Skip to main content

​
Overview

When you create or update a Retell or VAPI voice agent and assign it to a customer, Knotie AI Pro automatically wires in a live MCP (Model Context Protocol) server for that customer’s connected apps. This means:
  • Any app the customer connects in their portal (Gmail, Slack, HubSpot, Google Calendar, etc.) becomes available to the voice agent immediately — even apps connected after the agent was built.
  • You do not need to rebuild or re-import the agent when the customer connects a new app.
  • Tool availability is resolved dynamically at call time.
Retell agent edit modal — Customer & Knowledge tab showing Current Customer Assignment and Knowledge Bases section

​
Prerequisites

​
How it works

When an agent is created or updated with a customer assigned:
  1. Knotie AI Pro mints an MCP token for that customer and attaches it to the agent automatically — for both Retell and VAPI, with no manual wiring on your part.
  2. At call time, the agent looks up whichever apps the customer has currently connected. New apps appear automatically — no token regeneration needed when the customer’s apps change.

​
What tools are served via MCP vs. static webhooks

Not all tool types switch to MCP. The table below explains the routing:

​
Supported voice providers

​
Token management

  • Each agent create/update operation mints a fresh MCP token with a 1-year lifetime.
  • When an agent is updated, the prior MCP token for that agent is deactivated automatically — stale tokens do not accumulate.
  • Tokens are stored as a secure hash only — the plaintext token is never stored.
  • You can view and revoke active MCP tokens under Settings → API Keys → MCP Tokens.
MCP Token Management page showing the Active Tokens section and Create New Token button

​
Troubleshooting

The voice agent can’t use my customer’s connected apps
  1. Confirm the integration gateway is configured. Check with support if unsure.
  2. Confirm the agent is assigned to the correct customer.
  3. Rebuild the agent (trigger an update) — this re-mints the MCP token and re-attaches the MCP server.
  4. Confirm the customer has connected the relevant app in their portal under Integrations.
I see old per-tool webhooks alongside MCP Custom API integrations and tools with pre-filled parameters intentionally keep static webhooks. MCP and static webhooks coexist — there is no conflict. VAPI agent update shows a warning about stale MCP tools On agent update, Knotie AI Pro removes prior MCP tools before attaching the new one. If a prior tool couldn’t be classified (e.g., the VAPI API was temporarily unreachable), the system logs a warning but continues — the new MCP tool is still attached. A subsequent update will clean up any lingering stale tools.