@graphland/flame-mcp

Connect Flame page setup tools to Cursor and other MCP IDEs with one command.

Quick start

1. In the Flame console, open MCP and create a server. Copy the install command. The secret already names the channels that server may manage.
2. Run it:

npx @graphland/flame-mcp init \
  --name flame-store \
  --secret flm_YOUR_SECRET \
  --api-url https://api.flame.bd

3. Reload MCP in Cursor → Settings → MCP.

Cursor runs npx @graphland/flame-mcp in the background and exposes the page-setup tools — for example list_channels, update_agent_config, list_knowledge_documents, list_catalog_items, create_social_post.

npm still serves 0.1.1, which rejects this command and asks for --org and --page. Until 0.2.0 is published, run the copy in this repo instead:

bun packages/flame-mcp/src/index.ts init \
  --name flame-store \
  --secret flm_YOUR_SECRET \
  --api-url https://api.flame.bd

Options

| Flag | Env var | Description | | ----------- | ----------------------- | ---------------------------------------------------- | | --secret | FLAME_MCP_SECRET | MCP server secret from the Flame console | | --api-url | FLAME_API_URL | API base URL (default http://localhost:8000) | | --name | FLAME_MCP_SERVER_NAME | Name in Cursor MCP list (default flame) | | --project | — | Write .cursor/mcp.json in the current directory | | --dev | — | Point Cursor at the local monorepo package | | --config | — | Custom mcp.json path |

Test with MCP Inspector

MCP Inspector needs Node 22.19 or newer. The Flame API must be running. Use the secret from the console MCP page (flm_…); that key already names the channels the server may manage.

The HTTP server is http://localhost:8000/mcp. This package is only the stdio bridge Cursor runs in front of that URL.

Open the browser UI (the default; do not pass --cli). It prints a one-time URL and opens it:

npx @modelcontextprotocol/inspector \
  --server-url http://localhost:8000/mcp \
  --transport http \
  --header "Authorization: Bearer flm_YOUR_SECRET"

Connect, then use the Tools tab. Page tools need a channelId from list_channels when the key manages more than one channel. Omit it only when the server manages a single connected channel.

The CLI client prints JSON and exits. It does not open a browser.

npx @modelcontextprotocol/inspector --cli http://localhost:8000/mcp \
  --transport http \
  --header "Authorization: Bearer flm_YOUR_SECRET" \
  --method tools/list

List channels (id is the connection id):

npx @modelcontextprotocol/inspector --cli http://localhost:8000/mcp \
  --transport http \
  --header "Authorization: Bearer flm_YOUR_SECRET" \
  --method tools/call \
  --tool-name list_channels \
  --format json

Pass that id as channelId. Omit it only when the server manages a single connected channel.

npx @modelcontextprotocol/inspector --cli http://localhost:8000/mcp \
  --transport http \
  --header "Authorization: Bearer flm_YOUR_SECRET" \
  --method tools/call \
  --tool-name list_knowledge_documents \
  --tool-arg channelId=CONNECTION_ID \
  --format json

To exercise the stdio bridge itself, from the repo root:

npx @modelcontextprotocol/inspector --cli \
  -- bun packages/flame-mcp/src/index.ts \
  -e FLAME_API_URL=http://localhost:8000 \
  -e FLAME_MCP_SECRET=flm_YOUR_SECRET \
  --method tools/list

A missing or rejected token exits with code 3.

Manual Cursor config

If you prefer to edit ~/.cursor/mcp.json yourself:

{
  "mcpServers": {
    "flame": {
      "command": "npx",
      "args": ["-y", "@graphland/flame-mcp@latest"],
      "env": {
        "FLAME_API_URL": "https://api.flame.bd",
        "FLAME_MCP_SECRET": "flm_YOUR_SECRET"
      }
    }
  }
}