Get started

MCP servers

ThunderPhone can connect to a remote Model Context Protocol server, discover the tools it exposes, and make those tools available to selected phone agents. This is useful when an organization already has an MCP-compatible service or wants one connection to expose a controlled group of business actions.

The server defines the capabilities. ThunderPhone does not add scheduling, CRM, ticketing, or automation behavior merely because an MCP connection exists. An agent can use only the tools the remote server advertises and that the organization attaches to the agent.

What MCP servers do on ThunderPhone

A remote server is added by name and URL under Connections → MCP. ThunderPhone connects over Streamable HTTP, synchronizes the server, and caches the discovered tool list. Static HTTP headers are supported for servers that require values such as an authorization header.

Streamable HTTP is the supported transport. A local server that works only through standard input and output cannot be connected directly. The endpoint must be reachable at an HTTP URL from ThunderPhone.

After the server is saved, its connection can be enabled, disabled, edited, synchronized, or deleted. Disabling a server keeps the configuration without making it available. Synchronizing again is important after the remote server adds, removes, or changes a tool because agents see the tool list from the latest sync.

The connection remains inactive from the agent's perspective until it is attached in the agent builder. This separation lets one organization register a server once and choose which agents should receive its tools.

Typical call flows

Appointment workflow

An MCP server might expose tools for checking approved availability and creating a booking. During an appointment scheduling call, the agent collects the required details, invokes the relevant tool, and reports success only after the server confirms it. If the tool times out or returns ambiguous availability, the prompt should move to a fallback rather than inventing a result.

Lead or customer lookup

A server can expose a narrow lookup action for a business system. During lead qualification, the agent can request permitted context using the caller's confirmed details. A separate write tool could submit the result, but only if the server advertises it and the agent is instructed to use it.

Automation through an MCP endpoint

The ThunderPhone catalog includes a Zapier MCP connection. The available actions still come from the remote endpoint and its configuration. Connecting the endpoint is not blanket authorization to every downstream application; review the discovered tool list before attaching it to a production agent.

Setup outline

  1. Deploy or choose a remote MCP server with a Streamable HTTP endpoint.
  2. In Connections → MCP, add a clear name, the server URL, and any required static headers.
  3. Save and synchronize the connection, then inspect the discovered tools. If no tools appear, confirm that the server advertises them correctly.
  4. Attach the server to the agent that needs those tools.
  5. Update the agent prompt with when each tool may be called, required inputs, confirmation rules, and failure behavior.
  6. Test realistic success, rejection, timeout, and ambiguous-result cases before deploying the agent change.

Use narrow tool definitions and least-privilege credentials. The remote server must validate every request; a tool call from an agent should not bypass the business system's normal authorization or data rules.

Related workflows and terms