Connect Claude to Supermetrics

Query marketing and ads data from 150+ platforms - Google Ads, Meta, GA4, LinkedIn and more - through one API. Toolspoke puts 5 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 5
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Supermetrics
Open the marketplace in your workspace, add Supermetrics to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Supermetrics shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Supermetrics asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API keyRequired: Supermetrics Hub (hub.supermetrics.com) → your avatar → API keys → Create API key. Only team admins and owners can create one. The key queries every data source login your team has connected.

What Claude can do in Supermetrics

5 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 5Reads
Writes: 0Writes
Destructive: 0Destructive

Reads

Fetches data and changes nothing.

query_data
Run one query against a data source and return the rows as JSON. Name the source with ds_id (AW Google Ads, FA Meta Ads, GAWA Google Analytics 4, LIA LinkedIn Ads, …), the accounts with ds_accounts (from list_accounts), and the columns with fields (from list_fields, dimensions first). Check meta.status_code in the answer: SUCCESS means the rows are there; a still-running query returns a schedule_id for get_query_status.
list_accounts
The accounts available in one data source through the team's connected logins - the ids query_data takes as ds_accounts.
list_fields
The dimensions and metrics one data source offers, with the field ids query_data takes. An install tests itself with it against Google Analytics 4, because it needs the key to be valid and allowed to query but does not depend on which sources the team has connected.
get_query_status
The status of a query that returned a schedule_id - SCHEDULED, QUEUED, RUNNING, SUCCESS, FAILURE or STOPPED - with its rows once it has finished. Results expire an hour after the query stops.
get_query_results
Page through the rows of a finished query by schedule_id.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 5 actions above are the whole of it. A call to any other name is refused before it reaches Supermetrics rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It only reads: Every action here reads. Nothing this connector can do changes anything in Supermetrics.
It reaches no further than your credential: Toolspoke holds no access to Supermetrics of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Supermetrics: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Supermetrics. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Supermetrics's own rate limits. A call that Supermetrics refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Supermetrics?

5 named actions: 5 that only read. They include query_data, list_accounts and list_fields. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Supermetrics connector need?

API key. The connector asks for api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Supermetrics connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 5 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Supermetrics connector not do?

The 5 actions above are the whole of it. A call to any other name is refused before it reaches Supermetrics rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Every action here reads. Nothing this connector can do changes anything in Supermetrics. Toolspoke holds no access to Supermetrics of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Supermetrics. An agent has to ask. Toolspoke does not retry, queue or back off around Supermetrics's own rate limits. A call that Supermetrics refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Supermetrics's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Supermetrics?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More analytics connectors

Browse all of them