Connect an agent over MCP

claude mcp add --transport http analytics https://app.stepmetrics.co/mcp \
  --header "Authorization: Bearer dak_..."

Twenty-eight read-only tools: twenty-three over your web analytics and dashboard, and five over agent telemetry. The key determines which organisation you are querying, so a site id belonging to someone else returns the same "not found" as a site that does not exist.

An edit key, which is what the dashboard's Connect agent screen gives your agent, is offered sixteen more. An admin key gets them too. One creates a site, and four add and remove a site's funnels and event checks. Two manage the ignore list: tell the agent to stop counting your own visits and it excludes the computer it is running on. Seven build your Dashboard page: the shared metrics and ratio metrics it tracks, and adding, changing, removing or clearing its charts. Two list and revoke your workspace's keys, so you can ask it to switch off a key you shared by mistake; it only ever sees your own workspace's keys, and it cannot revoke an admin key. An edit key cannot create keys or reach billing. A read key is never offered any of the sixteen; if your agent was connected with one, open Connect agent again for a new key. You can also revoke keys yourself under Account, Workspace, API keys.