Model Context Protocol (MCP)

​

What is MCP?

​

Key Benefits

• Third-Party Platform Access — Connect your agent to MCP servers provided by CRMs, ERPs, scheduling platforms, and other business tools to access their data and functionality during live calls.
• Real-Time Data — Your agent can fetch live data from connected platforms to provide accurate, up-to-date answers to callers (e.g., look up order status, check inventory, pull customer records).
• Growing Ecosystem — As more platforms adopt the MCP standard, new integrations become available without requiring custom development on your end.

​

How to Enable MCP Integration

​

Via the Dashboard

1. In the Telzino Dashboard, navigate to Customers → your Organization → your Agent → Integrations.
2. Find Model Context Protocol (MCP) and click to configure.
3. Enter the MCP server URL from your vendor — SSE endpoint for SSE transport, or the streamable HTTP MCP URL for HTTP transport (same field; it must match the transport you choose next).
4. Choose Transport Type: sse or http.
5. Click Test Connection to verify the endpoint and discover available tools.
6. Click Save Connection. Your agent can now call the tools exposed by that MCP server during live conversations.

​

Choose which tools the agent uses

1. Open the MCP connection and click Test Connection (or open an already tested connection and click Edit).
2. Under Tools, turn off Automatically turn on new tools from this server, then untick the tools the agent should not use. Use Select all / Select none, and the search box on servers with more than 10 tools.
3. Click Save Connection / Update Connection (Dashboard), or Connect / Update / Connect Server / Update Server (Connect).

• Switch on (the default, and how every existing connection starts) means no limit — the agent gets every tool, including any the server adds later.
• Switch off means only the ticked tools, even if you tick all of them. Tools the server adds later stay off until you tick them.
• Tools the server removes drop off the list automatically the next time you test and save.
• Changing the endpoint URL, transport type or headers makes Save re-test the server first. With the switch off, if that test finds tools the server added since you last looked, Save stops and shows them (unticked) so you can review them — click Save again to finish.
• At least one tool must stay ticked; to stop using the server entirely, disconnect it.
• OpenTable reservation agents: only the 8 OpenTable tools are listed, and the availability, availability-slots and menu tools are always on because the reservation flow depends on them.

​

Look things up while the phone rings

​

Via the API

1. Open the agent in the Dashboard → Integrations → Model Context Protocol (MCP).
2. Click the connection with the Not tested badge — it opens directly in edit mode.
3. Click Test Connection to verify the endpoint and populate the tools list.
4. Click Update Connection to save the test result (this clears the badge).

​

SSE vs HTTP transport

• transport_type — Must be the lowercase string "sse" or "http" as persisted. Do not use "SSE", "HTTP", or other casing; the server reads the flag exactly as stored.
• mcp_endpoint_url — Same field name for both transports. For http, set it to your MCP server’s streamable HTTP endpoint. For sse, set it to your server’s SSE endpoint URL. Only transport_type distinguishes how the URL is interpreted.
• Test connection (server-side) — The test runner picks the transport from that flag: http → streamable HTTP client transport; sse (or non-http) → SSE client transport (with EventSource-style header behavior for SSE).

​

API Usage

• GET /v1/agents/{agentId} returns the agent row unchanged from storage. Whatever is under extensions.mcp_servers is the persisted list. Field reference: Get Agent — stored MCP shape.
• POST / PATCH (Create / Update agent) validate extensions on write. Each MCP entry uses a different request shape (name and url are both required) — the platform transforms this to the stored shape on write. See Create Agent — MCP request body. Do not paste a GET mcp_servers array directly into a POST/PATCH body without converting connection_name → name and mcp_endpoint_url → url.

{
  "extensions": {
    "mcp_servers": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "connection_name": "My Company MCP Server",
        "mcp_endpoint_url": "https://mcp.example.com/mcp",
        "transport_type": "http",
        "auth_headers": { "Authorization": "Bearer YOUR_TOKEN" },
        "initialization_options": {},
        "fingerprint": "sha256:abc123…",
        "tools": [
          { "name": "lookup_customer", "description": "Find customer by phone number" }
        ]
      }
    ]
  }
}

{
  "extensions": {
    "mcp_servers": [
      {
        "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
        "connection_name": "CRM MCP Server",
        "mcp_endpoint_url": "https://mcp.mycrm.com/sse",
        "transport_type": "sse",
        "auth_headers": {},
        "initialization_options": {},
        "tools": []
      }
    ]
  }
}

​

Example Use Cases

• CRM Integration — Connect to your CRM’s MCP server so your agent can pull up customer records and personalize conversations in real time.
• ERP & Order Management — Let your agent look up order status, check inventory, or retrieve account details from your ERP platform during a call.
• Scheduling Platforms — Connect to third-party scheduling systems that offer MCP servers to enable appointment booking and availability checking.
• Healthcare & Practice Management — Integrate with EHR and practice management systems that expose MCP endpoints for patient scheduling and record lookup.