Skip to content

Cline lexvibe list_frameworks

How to: Cline lexvibe list_frameworks

client:Cline transport:streamable-http tool:list_frameworks

Add lexvibe to Cline

  1. 01

    Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.

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

    Save the file and restart Cline.

  2. 03

    Ask for something list_frameworks does. Cline lists the server's tools on connect and calls list_frameworks itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that lexvibe's identifier in your config matches the one above exactly.

Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs

Set these first

lexvibe will not start until these are set, so list_frameworks never becomes available.

  • LEXVIBE_APP_ID
  • LEXVIBE_API_URL
  • LEXVIBE_CDN_URL
  • LEXVIBE_EVENTS_URL
  • LEXVIBE_TELEMETRY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.