Sign up

MCP

Connect AI assistants with MCP

On this page

MetricRaven runs a hosted MCP server, so an AI assistant can read your analytics and answer questions like “which channels brought paying customers last month?”. There is nothing to install.

Server URL
https://metricraven.com/api/mcp

It uses the Streamable HTTP transport and an access token sent as Authorization: Bearer.

Create a token

  1. Open Settings → API & MCP

    Go to metricraven.com/app/api and create a token, for example “Claude Code”.

  2. Choose its access

    Reports only is enough for most questions. Add Visitor details only if the assistant should see names, emails and journeys, and Write only if it should add websites or chart notes.

  3. Copy the token

    Keep it in an environment variable, for example export METRICRAVEN_TOKEN=mr_… in your shell profile.

Add the server to your client

Claude Code

terminal
claude mcp add --transport http metricraven https://metricraven.com/api/mcp \
  --header "Authorization: Bearer $METRICRAVEN_TOKEN"

Run /mcp in Claude Code to check that metricraven is connected. Add --scope user to use it in every project.

Codex

~/.codex/config.toml
[mcp_servers.metricraven]
url = "https://metricraven.com/api/mcp"
bearer_token_env_var = "METRICRAVEN_TOKEN"

Cursor

~/.cursor/mcp.json
{
  "mcpServers": {
    "metricraven": {
      "url": "https://metricraven.com/api/mcp",
      "headers": { "Authorization": "Bearer mr_YOUR_TOKEN" }
    }
  }
}

VS Code

.vscode/mcp.json
{
  "inputs": [
    { "type": "promptString", "id": "metricraven-token", "description": "MetricRaven access token", "password": true }
  ],
  "servers": {
    "metricraven": {
      "type": "http",
      "url": "https://metricraven.com/api/mcp",
      "headers": { "Authorization": "Bearer ${input:metricraven-token}" }
    }
  }
}

Claude Desktop and other clients

Any client that accepts a remote server URL and a header works directly. Clients that only start local servers can use the mcp-remote bridge:

claude_desktop_config.json
{
  "mcpServers": {
    "metricraven": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://metricraven.com/api/mcp", "--header", "Authorization: Bearer ${METRICRAVEN_TOKEN}"],
      "env": { "METRICRAVEN_TOKEN": "mr_YOUR_TOKEN" }
    }
  }
}

Try it

  • “How did traffic and revenue change this month compared with last month?”
  • “Which referrers brought paying customers in the last 90 days?”
  • “Where do visitors drop off in my signup funnel?”
  • “Which AI crawlers read my docs this week?”
  • “Add a chart note for today: launched the new pricing page.”

See every tool and its inputs in the tool reference.

Assistants only see what the token allows. Without the visitors scope, reports never include names, emails or visitor IDs.

Details

  • A site secret key also works, limited to its own website. Prefer an access token, which you can limit and delete.
  • The MCP server can't delete websites or people's data, or change billing.
  • Limit: 240 requests a minute per token.
  • Sign-in with OAuth, so you don't have to paste a token, is coming.