API/MCP Gateway

https://gateway.api.metricsensei.com

You're reading the docs for v14, an older version that is still live. The current version is v16: read its docs.

export MS_TOKEN=msat_...

# Admin API: the clients you manage
curl -s https://api.metricsensei.com/clients -H "Authorization: Bearer $MS_TOKEN"

# API/MCP Gateway: the tools you can run for the client acme
curl -s https://gateway.api.metricsensei.com/tools -H "Authorization: Bearer $MS_TOKEN" -H "Metric-Sensei-Client: acme"

Using the gateway

Every tool is available two ways: to AI apps at https://gateway.api.metricsensei.com/mcp, and as plain JSON for scripts.

curl -s https://gateway.api.metricsensei.com/tools/ga4_run_report \
  -H "Authorization: Bearer $MS_TOKEN" -H "Metric-Sensei-Client: acme" -H "content-type: application/json" \
  -d '{"metrics": ["sessions"], "dimensions": ["date"]}'

Which tools you see depends on the client's connections and your access to them. Tools that change something need a connection that allows changes and a token that isn't read-only.

Connect an AI app

Add https://gateway.api.metricsensei.com/mcp as a remote MCP server and sign in when the app asks. You sign in with your Metric Sensei account and pick the client; the app then sees only the tools you have access to there.

• Claude (claude.ai, Desktop and mobile): Settings → Connectors → Add custom connector, paste https://gateway.api.metricsensei.com/mcp, then Connect.
• Claude Code: claude mcp add --transport http metricsensei https://gateway.api.metricsensei.com/mcp, then run /mcp and choose Authenticate.
• ChatGPT, Cursor, VS Code and others: add a remote server with the Streamable HTTP transport and choose OAuth sign-in. No client ID is needed: apps find the sign-in through https://gateway.api.metricsensei.com/.well-known/oauth-protected-resource/mcp and register themselves.
• Apps that can only send a fixed header: send Authorization: Bearer with a gateway API key, or a personal token plus the Metric-Sensei-Client header.

Signed-in apps are listed in the admin page under Connect an AI app, where you can sign them out. To let an AI app manage Metric Sensei itself, connect it to the Admin API's /mcp the same way.

How versions work

Every deploy of the API/MCP Gateway is a new API version: v1, v2, v3 and so on. Older versions keep running unchanged until they're retired.

• Without a version you always get the latest: https://gateway.api.metricsensei.com/mcp, https://gateway.api.metricsensei.com/tools.
• To pin a version, put it before the path: https://gateway.api.metricsensei.com/v16/mcp.
• Or send a header: Metric-Sensei-Version: 16.
• Every response carries the version that answered it in the Metric-Sensei-Version header.
• A retired version answers 410 Gone, and an unknown one 404. Move to the latest or a live version.

Versions

As JSON: GET https://gateway.api.metricsensei.com/versions

Limits

Each client may make a set number of requests a minute, counted across all its API keys and signed-in apps. Above that the API answers 429 with a Retry-After header saying how many seconds to wait.

Examples

curl -H "Authorization: Bearer $API_KEY" https://gateway.api.metricsensei.com/tools
curl -H "Authorization: Bearer $API_KEY" https://gateway.api.metricsensei.com/v16/tools
curl -H "Authorization: Bearer $API_KEY" -H "Metric-Sensei-Version: 16" https://gateway.api.metricsensei.com/tools

For an AI app, use https://gateway.api.metricsensei.com/mcp to follow the latest version, or https://gateway.api.metricsensei.com/v16/mcp to stay on one. Sign-in works the same on every version.