Skip to main content
Data MCP exposes PolyAI’s conversation data as MCP tools. Your client discovers them automatically on connection — you don’t configure tools by hand. Each tool carries its own input schema, which the client reads directly from the server; the parameter tables below reproduce that schema so you can see what each tool takes without connecting first. Data MCP exposes 5 tools. Tool names appear exactly as your client sees them in tools/list.
To see exactly what your client discovered, ask it to list its tools or query the endpoint’s tools/list method. Parameters map to a PolyAI REST endpoint — they’re sent as path segments, query parameters, or a request body — but your client handles that wiring from the schema; the tables below just list what you can set.

Search & read conversations

Find conversations by their metrics, search across transcript text, and pull back the full turn-by-turn record.

search-conversations

Search conversations by metric filters, with sorting and pagination.

search-transcripts

Full-text search over transcript turns across conversations, returning matches with surrounding turns for context.

get-conversation

Fetch every turn of a single conversation.

Metrics & analytics

Discover which metrics you can filter and aggregate on, then roll one up over time into buckets you can chart.

get-metrics

List the filterable metrics for an account, optionally scoped to a project — built-in metrics plus any custom metrics the project defines. Use this first to discover what you can filter and aggregate on.

-experimental--aggregate-a-metric-over-a-time-interval

Aggregate a metric over a time window into buckets you can chart — with grouping, cohort filters, and post-aggregation thresholds.
This tool is experimental — its name (carrying the -experimental- prefix) and schema may change. Your client discovers the current name from tools/list.

Errors

Last modified on July 17, 2026