Lexvibe MCP Server

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

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

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

[mcp_servers.lexvibe]
url = "https://golexvibe.com/api/mcp"

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

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

This one needs environment variables set before it will start: LEXVIBE_APP_ID (Your LexVibe app id (used in the installed snippet and API calls). Optional: if unset, tools ask for the id explicitly and warn about the placeholder.), LEXVIBE_API_URL (Base URL of the LexVibe API. Only needed for self-hosting / development.), LEXVIBE_CDN_URL (Base URL the widget script is served from. Only needed for self-hosting / development (defaults to the LexVibe CDN, or to LEXVIBE_API_URL when that is set).), LEXVIBE_EVENTS_URL (Endpoint that receives anonymous tool-usage events (mcp_tool_call) for the Platform analytics. Defaults to the LexVibe events endpoint (or LEXVIBE_API_URL + /api/events when LEXVIBE_API_URL is set). Only needed for self-hosting.), LEXVIBE_TELEMETRY (Set to 0/false/off to disable anonymous usage telemetry. DO_NOT_TRACK=1 is also honored.). The author declared them in the registry entry; get the values from the project itself.

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints