Connect an MCP server to an agent
Discover tools from a public MCP server and choose which tools a voice agent may use.
Connect an MCP server to an agent
An operator can connect one public HTTPS MCP server to an existing voice agent. The server decides which tools are available for that agent's bearer token; MakeAutomation does not keep a fixed tool catalog.
Cloud Kinnekt is available as a preset. Other servers work when they support the
same bearer-authenticated, stateless JSON-over-POST tools/list and tools/call
contract. OAuth, sessions, SSE-only responses, and servers that require an
initialization handshake are not supported in this release.
What you need
- An existing voice agent
- The MCP server's public HTTPS URL
- A bearer token issued specifically for that agent
- An operator or administrator with access to the agent's tenant
Treat the token like a password. The dashboard accepts it as a write-only value and never displays it again.
During a voice call, the connected MCP server also receives the MakeAutomation call ID and, when available, the caller's phone number in each tool call's metadata. Connect only a provider approved to process caller data. These values are not added to the tool arguments chosen by the voice agent.
Connect and choose tools
- Open Admin → Agents and select the agent.
- Find the independent MCP Server card below the main agent settings.
- Confirm or replace the server URL. Cloud Kinnekt's preset
is
https://mcp.cloudkinnekt.au/mcp. - Paste the agent's bearer token and choose Discover tools.
- Review the names, descriptions, and expandable argument schemas returned by the server.
- Tick only the tools this agent should be able to use.
- Choose Save MCP tools.
Saving checks the server again before changing the agent. New server tools remain unticked. If a previously selected tool is no longer returned, the dashboard marks it unavailable and removes it on the next successful save.
Refresh, replace, or remove
- Use Refresh tools whenever the server's catalog or token permissions may have changed. Refreshing alone does not change the tools used at runtime.
- Use Replace token after the MCP provider rotates or reissues the agent's credential. Discover and save again with the replacement.
- Use Remove server to clear the URL, credential, and all selected remote tools from the agent.
Custom tools and the knowledge-base search tool cannot have the same name as an enabled MCP tool. Rename or disable the conflicting tool, then save again.
Troubleshooting
| Message or state | What to check |
|---|---|
| Token rejected | Confirm the token belongs to this agent and has not been rotated or disabled. |
| Server must be public HTTPS | Use the provider's public https:// endpoint; private, local, redirected, or reserved addresses are blocked. |
| No tools returned | Confirm the token has tools enabled at the MCP provider, then refresh. |
| Tool unavailable | The latest server response omitted a previously selected tool. Ask the provider to enable it or save to remove it. |
| Tool-name conflict | A Custom Tool or active knowledge-base tool uses the same name. Remove the collision; names are not silently rewritten. |
| Regional sync warning | The primary save succeeded, but the regional voice engine may remain stale until an operator repairs the data-plane sync. |
Connection setup does not prove a call can complete the provider action. After deployment, test the exact selected tools in a browser voice call and every production telephony path used by the agent.