API keys, MCP, and the partner data API

What it is

Three ways to read the same measured data outside the dashboard. An organization API key authenticates all of them. The MCP server speaks JSON-RPC over HTTP and exposes five read-only tools. The partner data API returns each asset’s latest measured summary as JSON. Neither surface has a write path.

When to use it

When you want your measurements inside an AI assistant, a BI tool, or your own client dashboard, without a manual export or yet another login.

Step by step

1. 1Open Settings and then API & MCP. Creating a key needs owner or admin rights, and a key’s plaintext is shown exactly once.
2. 2Copy the client configuration block into any client that speaks MCP over HTTP, including Claude Code and Claude Desktop, or use the curl example to call the endpoint directly.
3. 3For a client that connects on your behalf instead of taking a pasted key, use OAuth: it registers itself, sends you here to approve read-only access for one organization, and receives a short-lived token it can refresh.
4. 4Pull JSON for your own dashboards from the partner API: GET /api/partner/v1 for every asset, or add ?asset= plus an asset id for one, with the same key as a bearer token.
5. 5Revoke a connected app at any time under Connected apps. Revoking takes effect immediately.

What you will see

Your active keys with their prefixes and last-used dates, the MCP configuration and curl snippets, the connected apps you approved through OAuth with a revoke button on each, and the five readable tools: list_assets, get_visibility_score, list_findings, list_recommendations, and get_answer_share.