MCP

Query funnels, pages, goals, and traffic from your editor. Read-only.

Do not use tracker keys

Keys that start with ed_ live in the browser snippet and can only ingest events. MCP needs an account token (edt_) or an app read key (edr_). Never paste secrets into chat.

1. Create a token

Default: Settings → API / MCP. Restricted: one app, Settings on that app → MCP / read key.

Account tokens can list every app you allow. App read keys skip appId because they are bound to one project.

Endpoint: https://www.eventda.sh/api/mcp

2. Connect your client

Cursor, Claude Desktop, VS Code

json

{
  "mcpServers": {
    "eventdash": {
      "url": "https://www.eventda.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer edt_xxx"
      }
    }
  }
}

Claude Code

bash

claude mcp add --transport http eventdash https://www.eventda.sh/api/mcp \
  --header "Authorization: Bearer edt_xxx"

Codex

Store the token in EVENTDASH_TOKEN, then:

bash

codex mcp add eventdash \
  --url https://www.eventda.sh/api/mcp \
  --bearer-token-env-var EVENTDASH_TOKEN

stdio-only clients

json

{
  "mcpServers": {
    "eventdash": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.eventda.sh/api/mcp",
        "--header",
        "Authorization: Bearer edt_xxx"
      ]
    }
  }
}

What agents can ask

“What are the top pages this week?”

“Where does the signup funnel drop off?”

“Which UTM campaigns converted in the last 30 days?”

Tool reference For agents Open API / MCP settings