Koskamo

LexVibe MCP

An MCP server that provides one-step legal compliance for vibe-coded apps, including generating privacy policies, terms of service, cookie banners with script blocking, and EU AI Act risk classification checks.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

LexVibe MCP logo, by LexVibeCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by LexVibe
MCP endpoint (Streamable HTTP)
https://golexvibe.com/api/mcp
Vendor documentation

What its tools do

10 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Can change data (1)

10 of 10 have a description · 10 of 10 declare behavior hints · 10 of 10 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Generate privacy policies and terms of service
  • Install cookie banners with real script blocking
  • Check EU AI Act compliance and risk classification
  • Scan projects to infer missing compliance facts

Source and maintenance

Community listingRegistry 1.0.4
Maintenance checked

Protocol and capabilities

Server
lexvibe 0.1.9
MCP protocol negotiated in check
2025-11-25
Tools
10 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

LexVibe makes vibe-coded apps (Lovable, Bolt, v0, Next.js, plain HTML) legally compliant: GDPR privacy policy, terms of service, cookie consent banner with real script blocking, and EU AI Act risk classification. This is the REMOTE server (no filesystem access): use check_website or check_store to analyze a live site or store listing, generate_policies for localized document drafts, check_ai_act to classify EU AI Act risk, and get_install_snippet for the exact install steps. To create a REAL app in the user's account (real app id instead of YOUR_APP_ID, hosted + auto-updated policies), call claim_app — it returns a link the user opens to confirm — then poll get_claim_status. Legal documents describe the app as it was when they were generated: after adding any SDK, analytics, payments, auth or AI integration, run check_website again — for claimed apps it returns a drift section listing processing the hosted documents don't cover yet, with a recommendation to regenerate. For local-repo scanning and automatic snippet installation, use the stdio server instead: npx -y @lexvibe/mcp. For regulatory questions that need a citable answer rather than an action, use the read-only lookups: list_frameworks (55 privacy and AI laws across 46 jurisdictions, including 17 US state laws modelled individually), lookup_framework (full record for one law: applicability threshold, required documents, rights granted, cookie regime, key articles and a link to its OFFICIAL text) and applicable_frameworks (given the markets a product serves, everything that applies plus the strictest cookie regime). The same data is downloadable as an open dataset at /api/dataset (CC BY 4.0).

Tools

10 advertised

check_website — Check website compliance
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Free legal-compliance check of a public website (no signup). Fetches the URL server-side and detects data processing relevant to compliance — analytics, marketing pixels, payments, generative AI, email collection, third-party sharing — then returns the legal documents and cookie-consent setup the site needs, whether the EU AI Act applies, and suggestedAnswers you can pass straight to generate_policies. Result contract: `fetched` is true only when the page HTML was actually read; when false, `fetchError` says why ("unreachable": the URL could not be resolved or connected; "blocked": the server answered with an error status) and the detected signals are NOT meaningful — report the check as inconclusive, not as clean. Run it again after adding any SDK, analytics, payment, auth or AI integration: when an appId is passed (or read from the installed LexVibe snippet) the result ALWAYS includes a `drift` key — status "in_sync", "outdated" (listing processing the hosted legal documents don't cover yet) or "unavailable" with a bounded `reason` (no-database, app-not-found, no-baseline, domain-mismatch, page-not-fetched) when the comparison could not be made; treat "unavailable" as unknown, never as in sync. Read-only.

check_website input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 300,
      "minLength": 3,
      "description": "Website URL or bare domain, e.g. https://myapp.com or myapp.com."
    },
    "appId": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,80}$",
      "description": "Optional LexVibe app id of a claimed app. When provided (or when the page already carries the installed LexVibe snippet), the result includes a drift report comparing the current site against the baseline its legal documents were generated from."
    }
  },
  "additionalProperties": false
}
check_website annotations
{
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
check_store — Check app-store listing compliance
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Free legal-compliance check of a mobile app from its PUBLIC App Store (apps.apple.com) or Google Play (play.google.com) listing URL — no repo or developer-account access needed. Follows the privacy-policy link the developer declared on the listing, analyzes that page, and returns detected data processing, compliance recommendations, whether the EU AI Act applies, and suggestedAnswers for generate_policies. Read-only.

check_store input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 500,
      "minLength": 10,
      "description": "App Store or Google Play listing URL, e.g. https://apps.apple.com/app/id123456789 or https://play.google.com/store/apps/details?id=com.example.app."
    }
  },
  "additionalProperties": false
}
check_store annotations
{
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
generate_policies — Generate legal documents
Advertised by the server during the last successful anonymous check.
Advertised read-only

Generate the legal documents (privacy policy, terms of service and, if applicable, an AI disclosure) localized and tailored to the target markets (GDPR, UK GDPR, CCPA…). Returns Markdown drafts. Pass check_website's or check_store's suggestedAnswers as `answers` so the documents disclose the right processing. Anonymous remote generation is template-based and capped at 3 locales; AI-tailored, hosted and auto-updated documents require a LexVibe account (https://golexvibe.com).

generate_policies input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appName",
    "markets"
  ],
  "properties": {
    "entity": {
      "type": "string",
      "maxLength": 300,
      "description": "Data controller / legal entity responsible for the app."
    },
    "answers": {
      "type": "object",
      "default": {},
      "description": "Compliance flags; pass check_website's suggestedAnswers. Recognized keys: usesAnalytics, processesPayments, usesGenerativeAI, collectsEmails, sharesWithThirdParties, platformType.",
      "additionalProperties": {
        "anyOf": [
          {
            "type": "string",
            "maxLength": 2000
          },
          {
            "type": "boolean"
          },
          {
            "type": "array",
            "items": {
              "type": "string",
              "maxLength": 200
            }
          }
        ]
      }
    },
    "appName": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Public / commercial name of the product."
    },
    "locales": {
      "type": "array",
      "items": {
        "enum": [
          "es",
          "en",
          "fr",
          "de",
          "it",
          "pt",
          "nl",
          "ja",
          "zh",
          "ko",
          "hi",
          "ar"
        ],
        "type": "string"
      },
      "maxItems": 3,
      "minItems": 1,
      "description": "Document languages (max 3 for anonymous callers). Defaults to the languages suggested by the chosen markets."
    },
    "markets": {
      "type": "array",
      "items": {
        "enum": [
          "eu",
          "uk",
          "ch",
          "us",
          "ca",
          "latam",
          "apac",
          "india",
          "china",
          "mena",
          "africa",
          "global"
        ],
        "type": "string"
      },
      "maxItems": 12,
      "minItems": 1,
      "description": "Regions where the app has users; determines the legal frameworks covered."
    },
    "contactEmail": {
      "type": "string",
      "maxLength": 200,
      "description": "Contact email for privacy requests and data-subject rights."
    }
  },
  "additionalProperties": false
}
generate_policies annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
check_ai_act — Classify EU AI Act risk
Advertised by the server during the last successful anonymous check.
Advertised read-only

Classify a product's risk level under the EU AI Act — minimal, limited, high or prohibited — and return the applicable obligations, each with its compliance deadline (limited-risk transparency duties apply from Aug 2, 2026; Annex III high risk from Dec 2, 2027). The boolean parameters fall into three groups, all optional and defaulting to the safest 'not applicable' value: (1) transparency triggers — usesAI, interactsWithPeople, generatesContent, automatedDecisions; (2) the eight prohibited practices of art. 5 — socialScoring, realtimeBiometricPublic + realtimeBiometricLawEnforcement, emotionRecognitionWorkEducation, biometricCategorisationSensitive, untargetedFaceScraping, manipulativeOrExploitative, individualPredictivePolicing; (3) high-risk triggers — embeddedInRegulatedProduct, annexIII domains. Answer the boolean questions about what the system does; leave unknowns at their defaults, which never over-report risk. Read-only and instant.

check_ai_act input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "usesAI": {
      "type": "boolean",
      "default": true,
      "description": "Does the product use AI at all (LLM calls, recommendations, computer vision…)? false ⇒ minimal risk, the AI Act does not apply."
    },
    "annexIII": {
      "type": "array",
      "items": {
        "enum": [
          "biometrics",
          "critical",
          "education",
          "employment",
          "essential",
          "law",
          "migration",
          "justice"
        ],
        "type": "string"
      },
      "default": [],
      "description": "Annex III high-risk domains that apply. Only these exact values count; anything else is not Annex III and must be left out."
    },
    "socialScoring": {
      "type": "boolean",
      "default": false,
      "description": "Does it score people's social behavior or traits causing detrimental treatment in unrelated contexts, or disproportionate to the behavior (art. 5.1.c)? Prohibited. A seller rating or fitness points app is NOT this."
    },
    "generatesContent": {
      "type": "boolean",
      "default": false,
      "description": "Does it generate text, images, audio or video shown to users? Triggers the art. 50 duty to label AI-generated content."
    },
    "automatedDecisions": {
      "type": "boolean",
      "default": false,
      "description": "Does it make automated decisions with legal or similarly significant effects on people (credit, hiring, admissions…)? Adds GDPR art. 22 duties; high risk only if an Annex III domain applies."
    },
    "interactsWithPeople": {
      "type": "boolean",
      "default": false,
      "description": "Do people interact directly with the AI (chatbot, voice assistant…)? Triggers the art. 50 duty to disclose they are talking to an AI."
    },
    "untargetedFaceScraping": {
      "type": "boolean",
      "default": false,
      "description": "Does it untargetedly scrape facial images from the internet or CCTV footage to build or expand a face-recognition database (art. 5.1.e)? Prohibited. Matching a user's own consented selfie against their own ID photo is NOT this."
    },
    "realtimeBiometricPublic": {
      "type": "boolean",
      "default": false,
      "description": "Real-time remote biometric identification in publicly accessible spaces (e.g. live face recognition)? High risk (Annex III biometrics) — prohibited only when combined with realtimeBiometricLawEnforcement."
    },
    "embeddedInRegulatedProduct": {
      "type": "boolean",
      "default": false,
      "description": "Is the AI a safety component embedded in an Annex I regulated product (toys, machinery, medical devices…)? High risk via art. 6.1, deadline Aug 2, 2028."
    },
    "manipulativeOrExploitative": {
      "type": "boolean",
      "default": false,
      "description": "Does it use subliminal techniques beyond a person's consciousness, or exploit a known vulnerability (age, disability, specific social or economic situation) to materially distort behavior and cause harm — e.g. dark patterns targeting a diagnosed gambling addiction (art. 5.1.a-b)? Prohibited. Ordinary persuasive marketing or UX nudges aimed at the general population are NOT this."
    },
    "individualPredictivePolicing": {
      "type": "boolean",
      "default": false,
      "description": "Predicting an individual's criminal risk based solely on profiling or personality traits (art. 5.1.d)? Prohibited."
    },
    "emotionRecognitionWorkEducation": {
      "type": "boolean",
      "default": false,
      "description": "Does it infer emotions (frustration, attention, mood…) from employees at work or students in education, e.g. to flag disengaged staff or bored students (art. 5.1.f)? Prohibited. Emotion inference on end users of a public consumer product (not their employees/students) is NOT this."
    },
    "realtimeBiometricLawEnforcement": {
      "type": "boolean",
      "default": false,
      "description": "Only if realtimeBiometricPublic: is it used FOR LAW ENFORCEMENT purposes? That combination is prohibited under art. 5.1.h and already in force; any other use of public real-time biometric ID is high risk instead. Without this the prohibition can never be reached."
    },
    "biometricCategorisationSensitive": {
      "type": "boolean",
      "default": false,
      "description": "Does it use biometric data (face, voice, gait…) to infer sensitive attributes — race, political opinion, religion, trade-union membership, sexual orientation (art. 5.1.g)? Prohibited. Ordinary face-unlock or liveness checks that don't infer these attributes are NOT this."
    }
  },
  "additionalProperties": false
}
check_ai_act annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
get_install_snippet — Get install snippet
Advertised by the server during the last successful anonymous check.
Advertised read-only

Return what to install for a LexVibe app id. For web: the one-line <script> snippet (cookie banner with real script blocking + hosted policy links) to paste before </head>, plus a JSX variant for React/Next.js layouts. For iOS/Android: the hosted privacy-policy URL and the exact App Store Connect / Google Play Console fields to paste it into. No app id yet? Call claim_app to create one in the user's account.

get_install_snippet input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{1,80}$",
      "description": "LexVibe app id from the dashboard."
    },
    "accent": {
      "type": "string",
      "pattern": "^#[0-9a-fA-F]{3,8}$",
      "description": "Optional brand color for the banner, as a hex value like #4f46e5."
    },
    "platform": {
      "enum": [
        "web",
        "ios",
        "android"
      ],
      "type": "string",
      "default": "web",
      "description": "Target platform. Defaults to web."
    }
  },
  "additionalProperties": false
}
get_install_snippet annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
claim_app — Claim a real LexVibe app
Advertised by the server during the last successful anonymous check.

Create a REAL LexVibe app in the user's account (replaces any YOUR_APP_ID placeholder). Returns a claim link: show it to the user so they can sign in and confirm — the link stays valid for 7 days, so the user can open it later. On confirmation LexVibe creates the app, scans the URL (if given), generates and hosts the legal documents. After the user confirms, call get_claim_status with the returned code to retrieve the real app id and install snippet. Provide at least `url` or `appName`.

claim_app input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 500,
      "minLength": 3,
      "description": "Public URL of the app: a website URL, or an App Store / Google Play listing URL for a mobile-only product. LexVibe scans whichever kind is provided on confirmation. If you don't have a listing URL yet, set `platform` explicitly instead."
    },
    "aiAct": {
      "type": "object",
      "description": "If you already ran check_ai_act for this product, pass the SAME answers object here. The EU AI Act classification is then saved against the app on confirmation and shown in the user's dashboard, instead of being lost when this conversation ends.",
      "additionalProperties": {
        "anyOf": [
          {
            "type": "boolean"
          },
          {
            "type": "array",
            "items": {
              "type": "string",
              "maxLength": 60
            },
            "maxItems": 8
          }
        ]
      }
    },
    "answers": {
      "type": "object",
      "description": "Compliance flags you already know (pass check_website's suggestedAnswers): usesAnalytics, processesPayments, usesGenerativeAI, collectsEmails, sharesWithThirdParties, platformType, companyEntity, contactEmail…",
      "additionalProperties": {
        "anyOf": [
          {
            "type": "string",
            "maxLength": 2000
          },
          {
            "type": "boolean"
          },
          {
            "type": "array",
            "items": {
              "type": "string",
              "maxLength": 200
            },
            "maxItems": 30
          }
        ]
      }
    },
    "appName": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "App / business name (required if no url is provided)."
    },
    "markets": {
      "type": "array",
      "items": {
        "enum": [
          "eu",
          "uk",
          "ch",
          "us",
          "ca",
          "latam",
          "apac",
          "india",
          "china",
          "mena",
          "africa",
          "global"
        ],
        "type": "string"
      },
      "maxItems": 12,
      "description": "Regions where the app has users; each market pack cites its own frameworks: eu → GDPR/ePrivacy, uk → UK GDPR/PECR, us → CCPA/CPRA, ca → PIPEDA, latam → LGPD…; 'global' is NOT a union of the others — it only cites generic OECD international privacy best practices, for users outside every listed market. To cover several specific frameworks, list each market explicitly, e.g. ['eu', 'us', 'latam']. Defaults to [eu]."
    },
    "platform": {
      "enum": [
        "web",
        "ios",
        "android"
      ],
      "type": "string",
      "description": "Target platform when there is no url to infer it from."
    }
  },
  "additionalProperties": false
}
claim_app annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "destructiveHint": false
}
get_claim_status — Get claim status
Advertised by the server during the last successful anonymous check.
Advertised read-only

Check whether the user has confirmed a claim created with claim_app. While the user hasn't confirmed yet it returns {status: 'pending'} — wait a few seconds and call again (the link stays valid for 7 days). Once claimed it returns the REAL app id, the install snippet and the hosted privacy-policy URL: replace any placeholder (YOUR_APP_ID) snippet with the real one.

get_claim_status input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]{16,64}$",
      "description": "The claim code returned by claim_app."
    }
  },
  "additionalProperties": false
}
get_claim_status annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
lookup_framework — Look up a privacy or AI framework
Advertised by the server during the last successful anonymous check.
Advertised read-only

Look up a privacy or AI law by id and get structured, primary-sourced facts: full name, jurisdiction, effective date, applicability threshold, the documents it requires, the rights it grants, its cookie-consent regime, whether it requires honouring Global Privacy Control, key articles, and a link to the OFFICIAL text (plus the supervisory authority). Use it to answer 'what does the TDPSA require?' or 'when does the EU AI Act apply?' with citations instead of guesses. Call list_frameworks first if you don't know the id. Read-only, instant, no signup.

lookup_framework input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 40,
      "minLength": 2,
      "description": "Framework id, e.g. \"gdpr\", \"eu-ai-act\", \"ccpa\", \"tdpsa\", \"lgpd\", \"pipl\", \"dpdp\", \"popia\". Get the full list from list_frameworks."
    }
  },
  "additionalProperties": false
}
lookup_framework annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
list_frameworks — List the frameworks LexVibe tracks
Advertised by the server during the last successful anonymous check.
Advertised read-only

List every privacy and AI framework LexVibe generates documents against — 55 laws across 46 jurisdictions, including GDPR, ePrivacy, the EU AI Act, UK GDPR and PECR, Swiss nFADP, 17 US state privacy laws modelled individually (CCPA/CPRA among them), PIPEDA and Quebec Law 25, LGPD and other LatAm regimes, APPI, PIPA, PDPA, Australia's Privacy Act, India's DPDP, China's PIPL, Saudi and UAE PDPL, POPIA and more. Each entry carries its id, jurisdiction, effective date and official-text URL. Optionally filter by market pack or by jurisdiction. Read-only, instant.

list_frameworks input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "market": {
      "enum": [
        "eu",
        "uk",
        "ch",
        "us",
        "ca",
        "latam",
        "apac",
        "india",
        "china",
        "mena",
        "africa",
        "global"
      ],
      "type": "string",
      "description": "Optional market pack to filter by (eu, uk, us, latam, apac…)."
    },
    "jurisdiction": {
      "type": "string",
      "maxLength": 20,
      "minLength": 2,
      "description": "Optional jurisdiction id to filter by, e.g. \"us-tx\", \"br\", \"eu\"."
    }
  },
  "additionalProperties": false
}
list_frameworks annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
applicable_frameworks — Which laws apply to my markets
Advertised by the server during the last successful anonymous check.
Advertised read-only

Given the markets a product serves, return every framework that applies, the documents it must publish, the strictest cookie-consent regime across those markets, and whether a universal opt-out signal (Global Privacy Control) has to be honoured. This is the read-only version of what generate_policies uses internally, so the answer matches the documents LexVibe would actually produce. Use it to answer 'I sell to the EU and Texas — what do I need?'. Read-only, instant.

applicable_frameworks input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "markets"
  ],
  "properties": {
    "markets": {
      "type": "array",
      "items": {
        "enum": [
          "eu",
          "uk",
          "ch",
          "us",
          "ca",
          "latam",
          "apac",
          "india",
          "china",
          "mena",
          "africa",
          "global"
        ],
        "type": "string"
      },
      "maxItems": 12,
      "minItems": 1,
      "description": "Markets the product serves, e.g. [\"eu\", \"us\"]."
    }
  },
  "additionalProperties": false
}
applicable_frameworks annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
626 ms
95th percentile latency
626 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 626 ms · metadata changed · 10 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http lexvibe-mcp-golexvibe https://golexvibe.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add lexvibe-mcp-golexvibe --url https://golexvibe.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable lexvibe-mcp-golexvibe in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "lexvibe-mcp-golexvibe": {
      "url": "https://golexvibe.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "lexvibe-mcp-golexvibe": {
      "type": "streamableHttp",
      "url": "https://golexvibe.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start lexvibe-mcp-golexvibe and inspect its tools.
VS Code configuration
{
  "servers": {
    "lexvibe-mcp-golexvibe": {
      "type": "http",
      "url": "https://golexvibe.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http lexvibe-mcp-golexvibe https://golexvibe.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://golexvibe.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "lexvibe-mcp-golexvibe": {
      "serverUrl": "https://golexvibe.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like LexVibe MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.