Connect Claude, Cursor or Codex over MCP

Create a personal access token or a per-project key, add Flamio to your AI tool's MCP config, and ask about your Flamio data from there.

Connect an AI tool such as Claude Code, Cursor or Codex to Flamio over MCP. The tool can then read your Flamio data, ask Flami, and build charts — from your terminal or editor.

Before you begin

You need the Editor, Admin or Owner role to create tokens and keys.
You run the setup in the AI tool itself — a terminal command or its MCP config file — not in Flamio.
Decide which credential you need:

Credential	Reaches	Use it for
Personal access token	Every project in your account	Your own AI tool: ask Flami, count and chart, read every project.
Per-project key	Exactly one project	A tool that should see one project only. It cannot ask Flami or build charts.

Create a personal access token

Open API & MCP

Click Settings, then API & MCP in the Developer group.

Create the token

Click Create token, enter a Name you will recognize later — for example "Claude Code on my laptop" — and click Create.

Copy the token

In Your new token, click Copy, then Done. "Copy this now. You won't be able to see it again."

Treat the token like a password

A token gives full read access to your account's data, and the right to ask Flami and build charts with your role. Keep it in your tool's config or an environment variable, never in a repository or a chat. Tokens do not expire — revoke one the moment you stop using it.

Create a per-project key

Find the project

On API & MCP, scroll to Per-project keys. Every project is listed with a Key active or No key pill.

Generate the key

On a project with No key, click Generate key.

Copy the key

In Your project key, click Copy, then Done. Flamio shows it once.

The key is a dedicated MCP key, separate from the On-Live project key your site uses — that one is not accepted for MCP.

Add Flamio to your AI tool

On API & MCP, Connect a client shows the MCP URL (https://api.flamio.org/api/mcp) and a snippet for each tool — the same ones as below.

claude mcp add --transport http flamio https://api.flamio.org/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

{
  "mcpServers": {
    "flamio": {
      "url": "https://api.flamio.org/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

codex mcp add flamio --url https://api.flamio.org/api/mcp --bearer-token-env-var FLAMIO_TOKEN

Set FLAMIO_TOKEN=<YOUR_TOKEN> in your environment first.

<YOUR_TOKEN> — the personal access token or per-project key you copied.
Claude Code and Codex: run the command in your terminal. Cursor: paste the JSON into Cursor's MCP config.
Codex reads the token from FLAMIO_TOKEN, so set it in your environment first.

Authentication is always the header Authorization: Bearer followed by the token.

Result

Ask your AI tool a question about your Flamio data. With a personal access token it reaches the same Flami you use in Flamio, through the tool's ask call, and can count, chart and save charts to dashboards with your role's rights.

What your AI tool can do

Purpose	Personal access token	Per-project key
List the projects it can reach	Yes	Its one project
Ask Flami a question and continue the conversation	Yes	No
Count anything On-Live recorded, as a number or a chart	Yes	No
Find saved charts and funnels, and list the visits behind a number	Yes	No
Save a chart, create a dashboard, add or remove a chart, create a funnel	Yes, if your role can	No
On-Live overview figures and goal conversions	Through counting	Yes
On-Live issues, problem pages and page details	Yes	Yes
Recorded On-Live sessions	Yes	Yes
Vision test tasks, their recordings and AI reports	Yes	Tasks linked to the project

Manage tokens and keys

Revoke a token: click Revoke on its row under Tokens and confirm Revoke token?. It stops working immediately. Each row shows when the token was created and last used.
Rotate a project key: click Regenerate and confirm Regenerate key?. The current key stops working immediately.
Remove a project key: click Revoke and confirm Revoke key?.

Scoping is all-or-one: a token reaches every project in your account and a key reaches exactly one. There is no subset of projects, no per-tool limit and no expiry date. To rotate a token, revoke it and create a new one.

Connect Claude, Cursor or Codex over MCP

On this page