Prerequisites
Get access to a PolyAI workspace
You build agents inside a PolyAI workspace, so you need access to one first.
- Enterprise customers — PolyAI provisions your workspace during onboarding; your PolyAI representative sets it up and grants you access. Enterprise workspaces are region-specific (US, UK, or EU).
- Getting started via the website — sign up at poly.ai to create a self-serve workspace, which lives in the Studio region.
Get an API key
Create a workspace-scoped API key from the API Keys tab on your workspace homepage in Agent Studio (see API keys). Copy the value when it’s shown — the full key only appears once.
Treat the key like a password. Don’t commit it or put it in client-side code.

Find your account ID
Open Agent Studio. Your account ID is the first path segment in the URL:For example,
https://studio.uk.poly.ai/acme-uk/acme-team-4/agent → account_id=acme-uk.“Account ID” and “Workspace ID” are the same thing. Agent Studio’s UI calls this the Workspace ID and shows it in a prefixed form (
ws-xxxxxxxx). The API parameter is named accountId (Agents and Data APIs) or account_id (Conversations, Chat, Webhooks, and most other APIs) — same value, different casing convention depending on which API family you’re calling. Both the slug form from the URL (acme-uk) and the prefixed form (ws-xxxxxxxx) work in API calls.1. Set your key and endpoint
| Region | Endpoint |
|---|---|
| US | https://api.us.poly.ai/builder-mcp |
| UK | https://api.uk.poly.ai/builder-mcp |
| EU | https://api.eu.poly.ai/builder-mcp |
| Studio | https://api.studio.poly.ai/builder-mcp |
2. Add the server to your client
- Cursor
- Claude Code
- Claude Desktop
- Codex
Add to Restart Cursor, then open the MCP settings to confirm the PolyAI tools loaded.
~/.cursor/mcp.json:3. Verify
Ask your client to list its available tools, or test the endpoint directly:Next steps
What Builder MCP can do
Browse the tools, grouped by agents, data, and alerts.
Build, test & deploy
Walk through the full lifecycle from branch to production.

