Connect LexVibe to any AI coding tool

Local (recommended — the agent can scan the repo and install the snippet for you):

claude mcp add lexvibe -- npx -y @lexvibe/mcp

Or connect to the remote server (no local install):

claude mcp add --transport http lexvibe https://golexvibe.com/api/mcp

Then ask: “Make my app legally compliant for the EU.” The make_compliant tool does everything in one step.

Add LexVibe as a custom connector: open Settings → Connectors → Add custom connector and paste the remote server URL:

https://golexvibe.com/api/mcp

Claude can then check any website or app-store listing, draft localized policies, classify EU AI Act risk and hand you the exact install snippet — from the browser or the desktop app.

One-click install: Add LexVibe to Cursor (uses Cursor's cursor://anysphere.cursor-deeplink/mcp/install deeplink). Or create .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "lexvibe": {
      "command": "npx",
      "args": ["-y", "@lexvibe/mcp"],
      "env": { "LEXVIBE_APP_ID": "YOUR_APP_ID" }
    }
  }
}

Codex is the one client that does not use the mcpServers JSON above: its config is TOML in ~/.codex/config.toml (or .codex/config.toml for a single trusted project). The one-liner:

codex mcp add lexvibe -- npx -y @lexvibe/mcp

Or add the table by hand:

[mcp_servers.lexvibe]
command = "npx"
args = ["-y", "@lexvibe/mcp"]
env = { LEXVIBE_APP_ID = "YOUR_APP_ID" }

For the remote server, use codex mcp add lexvibe --url https://golexvibe.com/api/mcp — no account and no install, but it cannot read your local repo, so make_compliant is stdio-only.

Same mcpServers shape as Cursor, in ~/.gemini/settings.json (or .gemini/settings.json per project):

{
  "mcpServers": {
    "lexvibe": {
      "command": "npx",
      "args": ["-y", "@lexvibe/mcp"],
      "env": { "LEXVIBE_APP_ID": "YOUR_APP_ID" }
    }
  }
}

For the remote server use httpUrl, not url: in Gemini CLI url means SSE, and our endpoint speaks Streamable HTTP only.

{
  "mcpServers": {
    "lexvibe": { "httpUrl": "https://golexvibe.com/api/mcp" }
  }
}

Both use the standard mcpServers config. In Windsurf, add it to ~/.codeium/windsurf/mcp_config.json. In Cline, open MCP Servers → Configure MCP Servers (which edits cline_mcp_settings.json):

{
  "mcpServers": {
    "lexvibe": {
      "command": "npx",
      "args": ["-y", "@lexvibe/mcp"],
      "env": { "LEXVIBE_APP_ID": "YOUR_APP_ID" }
    }
  }
}

GitHub Copilot's agent mode reads MCP servers from .vscode/mcp.json:

{
  "servers": {
    "lexvibe": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@lexvibe/mcp"]
    }
  }
}

Add a context server to your settings.json:

{
  "context_servers": {
    "lexvibe": {
      "command": "npx",
      "args": ["-y", "@lexvibe/mcp"],
      "env": {}
    }
  }
}

Zed also supports remote servers directly — use { "url": "https://golexvibe.com/api/mcp" } instead of command.

ChatGPT connects to remote MCP servers via connectors (available on paid plans; custom connectors may require enabling developer mode). Open Settings → Connectors → Create and paste:

https://golexvibe.com/api/mcp

No authentication is required — the LexVibe remote server is anonymous.

Lovable connects to custom MCP servers as chat connectors, on every plan. Add a custom MCP server, choose no authentication and paste:

https://golexvibe.com/api/mcp

Then ask in the project chat: “Check my published site with LexVibe and add the privacy policy, terms and cookie banner it recommends.” The connection is personal and only used while building — it never becomes part of your published app. Prefer not to add a connector? The prompt below works too. A full walkthrough with questions and answers lives at LexVibe for Lovable.

No MCP setup needed: LexVibe also speaks your builder's language — a prompt. Paste this one-liner into your AI builder's chat:

Read https://golexvibe.com/prompt and follow it to make this app legally compliant (privacy policy, terms, cookie banner, EU AI Act).

The agent fetches https://golexvibe.com/prompt — instructions to scan your project, ask only for what the code cannot show (owner, contact email and target markets), send you to the free check to finish the setup, and then add the snippet with the app id from your own dashboard. Product context for AI assistants lives at https://golexvibe.com/llms.txt. Prefer zero setup? Paste your URL (website or App Store / Google Play listing) at https://golexvibe.com/check for an instant compliance report. Walkthroughs per builder: Bolt, v0, Base44 and Replit.

The remote endpoint (https://golexvibe.com/api/mcp, Streamable HTTP, no auth) exposes: check_website, check_store, generate_policies (template-based drafts, capped for anonymous callers), check_ai_act, get_install_snippet, and claim_app / get_claim_status — the agent hands you a link to sign in and confirm, which creates a real app in your account and gives the agent the real app id and snippet (no more YOUR_APP_ID placeholder). It cannot read or write your files — for repo scanning and automatic snippet installation use the stdio server (npx -y @lexvibe/mcp). Stdio-only clients can bridge to the remote server with npx -y mcp-remote https://golexvibe.com/api/mcp.

Beyond AI tools, LexVibe connects to where your app lives so compliance stays fresh without you doing anything. All of these are managed from Dashboard → Integrations.