@graphland/flame-mcp

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

Quick start

1. Set MCP_API_SECRET on your Flame API.
2. Run:

npx @graphland/flame-mcp init \
  --org your-organization-id \
  --page your-facebook-page-id \
  --secret your-mcp-api-secret

3. Reload MCP in Cursor → Settings → MCP.

That's it. Cursor will run npx @graphland/flame-mcp in the background and expose tools like create_knowledge_document, list_catalog_items, update_agent_config, etc.

Options

| Flag | Env var | Description | |------|---------|-------------| | --org | FLAME_ORGANIZATION_ID | Active organization id | | --page | FLAME_PAGE_ID | Connected Facebook page id | | --secret | FLAME_MCP_SECRET | Same value as API MCP_API_SECRET | | --api-url | FLAME_API_URL | API base URL (default http://localhost:8000) | | --name | FLAME_MCP_SERVER_NAME | Name in Cursor MCP list | | --project | — | Write .cursor/mcp.json in current directory | | --dev | — | Point Cursor at the local monorepo package (before npm publish) |

Local development (monorepo)

Before @graphland/flame-mcp is published to npm:

npx ./packages/flame-mcp init --dev \
  --org your-org-id \
  --page your-page-id \
  --secret your-mcp-secret

Per-page setup

Run init once per page (use --name flame-my-page to distinguish them):

npx @graphland/flame-mcp init --name flame-waland --org abc --page 1073361822536312 --secret ...

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": "http://localhost:8000",
        "FLAME_MCP_SECRET": "your-secret",
        "FLAME_ORGANIZATION_ID": "your-org-id",
        "FLAME_PAGE_ID": "your-page-id"
      }
    }
  }
}