PolyAI Builder MCP
MCP server for building, testing and deploying PolyAI voice agents from an IDE
PolyAI Builder MCP is an MCP server for agent tooling. It runs as a hosted remote server, so there is nothing to install locally.
- Platforms
- CLI, API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
Similar MCP servers
About PolyAI Builder MCP
The Builder MCP lets an MCP-compatible IDE or AI coding assistant act as the client for PolyAI's platform. Instead of writing raw API calls, you describe changes in conversation and the client calls the server's tools to create branches, edit greetings, run tests and move versions between environments.
The server is reached over streamable HTTP at a region-specific endpoint and authenticates with a single account API key. The docs say the client reads each tool and its schema from the server, so no hosts or headers need to be hand-written. Variants, environments and deployments are exposed as tools as well.
The docs position it for developers and teams who build PolyAI voice agents and want to manage their lifecycle from their coding environment. It is distinct from PolyAI's Agent Studio MCP integrations, which go the other way and give a live agent extra tools during a call.
What it does
- Conversational agent editing
- Ask an assistant to create a Branch or update a greeting and it runs the required tool calls in order.
- Test and publish workflow
- Tools cover testing an agent and moving it to Staging and beyond.
- Environment and deployment tools
- Variants, environments and deployments are available as callable tools.
- Single API key authentication
- One account API key authorises every tool exposed by the server.
- Schema-driven tool discovery
- The client reads each tool and its schema from the server, so requests are not hand-written.
Good for
- Build a new voice agent branch from an IDE chat prompt
- Update greetings and flows in a PolyAI agent without writing API calls
- Test an agent and promote it from one environment to another
- Manage variants and deployments as part of a developer workflow
PolyAI Builder MCP FAQ
What authentication does PolyAI Builder MCP need?
A single account API key authenticates every tool.
How does PolyAI Builder MCP differ from Agent Studio MCP integrations?
Builder MCP has an MCP client connect into PolyAI to build and publish agents, while Agent Studio MCP integrations have a live PolyAI agent connect out to a third-party server to gain tools during conversations.
Which transport does the server use?
The registry entry lists streamable HTTP at a region-specific endpoint on api.poly.ai.
What are the best alternatives to PolyAI Builder MCP?
The closest alternatives to PolyAI Builder MCP are Cognigy Ai MCP Management Server, Ateam MCP, Apiany MCP, Airtable MCP and APEX AI, LLM, PDF, QR, JSON & Media MCP.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.