Data MCP - PolyAI Platform

Data MCP is PolyAI’s authenticated MCP server for conversation data. Connect an MCP client — Claude Code, Cursor, Claude Desktop, or Codex — and you can search conversations, read transcripts, and aggregate metrics in plain language, without calling the REST API directly.

Data MCP vs Builder MCP

Both are PolyAI-hosted servers you connect in to. They cover different jobs and authenticate differently.

	Data MCP	Builder MCP
What it’s for	Query conversation data: transcripts, metrics, analytics	Build, test, and deploy agents
Authenticates	Account API key	Account API key
Endpoint path	`/data-mcp`	`/builder-mcp`
Docs	This page	Builder MCP

To connect a client out from a live agent to a third-party server instead, see Agent Studio MCP integrations.

What you can do

Conversation search

Find conversations by their metrics and scores — filter and sort on quality scores, duration, and outcomes over a date range.

Transcripts

Read the full, turn-by-turn record of a conversation, or search across many conversations for a word or phrase with surrounding context.

Metrics catalog

List the metrics available for an account or project — the built-in ones plus any custom metrics your projects define.

Analytics

Roll a metric up over time into buckets you can chart — grouped, filtered, and thresholded however you like.

Get started

1. Get an account API key

Every request carries an API key in the X-API-KEY header. Data MCP uses an account API key, created from your account page in Agent Studio — it’s scoped to the account and can query any project in it. See Authentication for details.

2. Set your key and endpoint

Keys are region-specific — a US key doesn’t work against the UK endpoint. Match the region to where your account lives. Self-serve (Studio) accounts are supported too.

Region	Endpoint
US	`https://api.us.poly.ai/data-mcp`
UK	`https://api.uk.poly.ai/data-mcp`
EU	`https://api.eu.poly.ai/data-mcp`
Studio	`https://api.studio.poly.ai/data-mcp`

export POLYAI_API_KEY="your_api_key_here"
export POLYAI_DATA_MCP_URL="https://api.us.poly.ai/data-mcp"   # use your region

3. Add the server to your client

Claude Code
Cursor
Claude Desktop
Codex

claude mcp add --transport http polyai-data "$POLYAI_DATA_MCP_URL" \
  --header "X-API-KEY: $POLYAI_API_KEY" \
  --header "Accept: application/json, text/event-stream"

Verify with claude mcp list, then ask Claude to list its PolyAI data tools.

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "polyai-data": {
      "url": "https://api.us.poly.ai/data-mcp",
      "headers": { "X-API-KEY": "your_api_key_here" }
    }
  }
}

Restart Cursor, then open the MCP settings to confirm the tools loaded.

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "polyai-data": {
      "url": "https://api.us.poly.ai/data-mcp",
      "headers": { "X-API-KEY": "your_api_key_here" }
    }
  }
}

Restart Claude Desktop. The tools appear in the tools menu.

Add to your Codex MCP config:

[mcp_servers.polyai-data]
url = "https://api.us.poly.ai/data-mcp"
headers = { "X-API-KEY" = "your_api_key_here" }

Working across regions? Add the server once per region under distinct names (e.g. polyai-data-us, polyai-data-uk, polyai-data-eu), each with that region’s key.

Capabilities

Data MCP exposes 5 tools — conversation search, transcript search, single-conversation fetch, a metrics catalog, and metric aggregation. See Capabilities for each tool and its parameters.

Browse the tools

Every Data MCP tool, grouped by what it does, with its parameters.

​Data MCP vs Builder MCP

​What you can do

Conversation search

Transcripts

Metrics catalog

Analytics

​Get started

​1. Get an account API key

​2. Set your key and endpoint

​3. Add the server to your client

​Capabilities

Browse the tools

Data MCP vs Builder MCP

What you can do

Get started

1. Get an account API key

2. Set your key and endpoint

3. Add the server to your client

Capabilities