Skip to navigation

MCP server

Connect custom tool servers using the Model Context Protocol.

MCP (Model Context Protocol) lets you connect any compatible tool server to your receptionist. Reception.ai discovers the server’s tools automatically, and your receptionist can call them during conversations.

What is MCP?

MCP is an open protocol for connecting AI to external tools and data sources. If your service exposes an MCP interface, the receptionist can use its tools without custom integration code.

Setting up an MCP connection

Go to Integrations, select Add integration, and choose MCP Server.

FieldDescription
NameDisplay name for this integration
DescriptionOptional. What this server provides.
Server typeSSE (default) or Streamable HTTP
Server URLThe HTTPS URL of your MCP server endpoint
Secret TokenOptional. Sent to authenticate with your server. Can only be set when creating the integration.
HTTP HeadersOptional headers sent with every request

Select Enable. Reception.ai connects and lists the available tools.

Server types

TypeWhen to use
SSELong-lived connections and streaming responses
Streamable HTTPStandard request and response, easier to deploy

Managing tools

Open the Tools tab to see the tools your server provides. Assign each tool to the Client (receptionist), the Assistant, or both, or select Enable all. Unassigned tools are not used.

Select Refresh tools after adding tools to your server.

If your server changes a tool after you enabled it, the tool shows a Changed badge and Reception.ai stops using it. Review the tool and select Update to save the tool assignments again.

When you edit the server, Rotate Secret Token (optional) replaces the saved token. The saved token is stored securely and never shown again.

Changing the server URL

You can edit the Server URL after setup. Changing it removes the stored secret token, and any HTTP headers you don’t re-enter in the same save, so they are never sent to the new address. To use a secret token with the new server, disconnect and reconnect the integration.

Use cases

  • Custom booking logic: connect to your existing reservation system.
  • Inventory lookup: let the receptionist check stock in real time.
  • CRM queries: pull customer data from your internal systems during calls.
  • Custom workflows: trigger any backend process based on the conversation.

You can connect multiple MCP servers. All their tools appear in the same assignment interface.

MCP servers are available on every plan. Your server must be reachable from the internet over HTTPS.