PolyAI Builder MCP

ai.polyPublished by poly.aiOfficial publisherv1.0.0Updated Nov 19, 2026

Build, test and deploy PolyAI voice agents from your IDE or AI coding tool. Needs an API key.

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant build, test and deploy PolyAI voice agents from an IDE or AI coding tool.

What you can do
  • Build PolyAI voice agents from an IDE or AI coding tool
  • Test and deploy those agents through the same assistant connection
  • Work against a regional PolyAI API endpoint over streamable HTTP
  • No individual tools are listed in the supplied material, so exact operations are not documented here.
When to use it
Useful if you already work with PolyAI voice agents and want an AI coding assistant to help create, test and deploy them without leaving the IDE.
Requirements
A remote endpoint at the regional PolyAI API host, reached over streamable HTTP. A PolyAI account API key, created on the API Keys tab in Agent Studio, sent in the X-API-KEY header. Network access to the endpoint.
Before you install
The server requires a PolyAI account API key in the X-API-KEY header; treat it as a secret and avoid exposing it in shared configuration. It can deploy agents, so changes may affect live voice agents. No tool list is published, so review what actions it can take before connecting.

Installation

In SourceWeft

  1. Open PolyAI Builder MCP in the dashboard and add it to a workspace.
  2. Connect X-API-KEY credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 19, 2026

Score

39% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Poly integrations