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
• An operator or administrator with access to the agent's tenant

For Cloud Kinnekt, the operator can create the key in the dashboard. For other MCP servers, bring the server's public HTTPS URL and an agent-specific bearer token.

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

1. Open Admin → Agents and select the agent.
2. Find the independent MCP Server card below the main agent settings.
3. For Cloud Kinnekt, choose Create key. If you already use CK webhooks for this agent, enter one of its current bearer tokens first so CK can carry over that setup. The dashboard saves the new key and server URL automatically. If the tenant has a saved GHL Private Integration token and Location ID, CK receives them for its GHL tools. Review any warnings shown after creation. For another server, enter its URL and bearer token instead.
4. Choose Discover tools.
5. Review the names, descriptions, and expandable argument schemas returned by the server.
6. Tick only the tools this agent should be able to use.
7. 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. Creating a CK key does not enable any newly discovered tools by itself. Previously selected tools remain selected only when the new CK key still offers them. CK booking and email actions also need calendar and conversation permissions on the GHL Private Integration token. You can create a CK key without GHL; adding GHL later currently requires an operator to coordinate an update with CK.

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.
• For a manually entered connection, use Replace token after the MCP provider reissues the credential. Discover and save again. For a dashboard-created CK key, remove the server to revoke it, then create a new key and review the tool selection.
• Use Remove server to clear the URL, credential, and all selected remote tools from the agent. For a dashboard-created CK key, this also revokes the key at CK.

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

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.