Docs · Integrations

Connect LexVibe to any AI coding tool

LexVibe ships a Model Context Protocol (MCP) server in two flavors: a local stdio server (npx -y @lexvibe/mcp) that can scan your repo and install the cookie-banner snippet into your files, and a remote server over Streamable HTTP at https://golexvibe.com/api/mcp for browser-based agents that cannot run local processes. Platforms without MCP support get the same result through a single prompt.

PlatformMethodSetup
Claude CodeMCP — stdio or remoteclaude mcp add
Claude Desktop / claude.aiMCP — remoteSettings → Connectors
CursorMCP — stdio.cursor/mcp.json or one-click
WindsurfMCP — stdiomcp_config.json
ClineMCP — stdiocline_mcp_settings.json
VS Code (agent mode)MCP — stdio.vscode/mcp.json
ZedMCP — stdio or remotesettings.json
Codex CLIMCP — stdio or remotecodex mcp add / config.toml
Gemini CLIMCP — stdio or remote~/.gemini/settings.json
ChatGPTMCP — remoteSettings → Connectors
Lovable / Bolt / v0 / Base44 / ReplitPrompthttps://golexvibe.com/prompt

Claude Code

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.

Claude Desktop & claude.ai

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.

Cursor

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 CLI

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.

Gemini CLI

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" }
  }
}

Windsurf & Cline

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" }
    }
  }
}

VS Code (agent mode)

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

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

Zed

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

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, Bolt, v0, Base44 & Replit

These builders don't support MCP yet, so LexVibe speaks their 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 — step-by-step instructions to discover your legal needs from the code, generate the documents and install the snippet. 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.

About the remote MCP server

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.

Platform integrations

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.

GitHub

Install the LexVibe GitHub App on your repo and it opens a Pull Request that adds the snippet — you just review and merge. After that, every push is scanned for legally relevant changes (new payment/analytics/AI SDKs) and your documents are flagged for review when your code drifts. Works for web and mobile repos.

Vercel

Connect your Vercel account to link a project to your app: LexVibe pulls the production domain automatically and re-scans your site after each deployment, so the banner verification and drift detection track what is actually live.

Netlify, Render, Railway, Cloudflare Pages — universal deploy hook

Every app gets a private deploy-hook URL (Dashboard → Integrations → Deploy hook). Paste it as an outgoing deploy notification in your platform (Netlify: Site configuration → Notifications; Render: Workspace → Webhooks; Railway: Project → Webhooks; Cloudflare: Notifications → Destinations) and LexVibe re-scans your site after every successful deploy — same effect as the native Vercel integration, on any host. Plain POST, no body required.

Outgoing webhooks (Zapier · Make · n8n · your server)

LexVibe can push compliance events to you: consent recorded, regulation applied, documents flagged for review, EU AI Act assessed, snippet status changes and drift detected. Every delivery is HMAC-SHA256 signed (x-lexvibe-signature) so you can verify origin. Configure per app in Dashboard → Webhooks — paste a Zapier/Make/n8n catch URL and pick your events.

Slack & Discord

Paste a Slack Incoming Webhook URL (or a Discord channel webhook URL) directly in Dashboard → Webhooks: LexVibe detects the destination and sends a readable chat message instead of the signed JSON payload. Pick the events you care about — for example drift.detected to get pinged when your app changes in a legally relevant way. No Zapier in between.

Google Tag Manager & Consent Mode v2

Add data-consent-mode="on" to the snippet and the banner drives Google Consent Mode v2 (default denied, update on accept). The banner also pushes a lexvibe_consent event to dataLayer with the accepted state in categories — create a Custom Event trigger in GTM and gate tags on Data Layer variables like categories.analytics or categories.marketing.

WordPress

Download a ready-made plugin from Dashboard → Integrations → WordPress: it is generated with your app's identifier, so you just upload it under Plugins → Add New → Upload Plugin, activate, and the snippet is injected on every page. Nothing to configure.

Shopify & site builders (Webflow · Framer · Wix · Squarespace)

Shopify: Online Store → Themes → Edit code → layout/theme.liquid, paste the snippet before </head>. Site builders all have a custom-code slot for the head (Webflow: Site settings → Custom code; Framer: Site Settings → Custom Code; Wix: Settings → Custom code; Squarespace: Settings → Advanced → Code Injection). Paste, publish, done.