Server

One MCP tool contract for telephony — any call provider, hosted, local, or BYOK.

CallMCP Server is an MCP server published by ai.callmcp that exposes a unified tool contract for telephony operations. Its stated purpose is to abstract away provider-specific differences so that an AI agent can work with any call provider — whether that provider is hosted externally, run locally, or supplied by the user under a bring-your-own-key arrangement. The server communicates over the stdio transport and is distributed as the npm package @callmcp/server at version 0.1.2. Runtime behaviour is controlled through two environment variables: CALLMCP_CONFIG, which points to the configuration the server should load, and CALLMCP_DEFAULT_DRIVER, which selects which telephony backend the server will use by default. Because the facts do not include a populated tool list, the exact MCP tools exposed at runtime are not documented here; consult the repository at https://github.com/CallMCP/callmcp for tool-level detail. The server is the right choice when you want a single, consistent MCP interface for telephony that is not locked to one provider, and when your agent runtime supports the stdio transport. It is unlikely to be the right choice if you need a well-documented tool schema before integrating, if your agent runtime requires HTTP or SSE transport, or if you are not working with telephony or call-provider workflows at all.

Use cases

  • Integrate telephony into an AI agent without writing provider-specific adapter code
  • Switch between hosted and local call providers by changing CALLMCP_DEFAULT_DRIVER without modifying agent logic
  • Use a bring-your-own-key call provider through a standard MCP interface
  • Wire up telephony capabilities in an agent pipeline that consumes MCP servers over stdio

When to use it

  • The agent needs to interact with a telephony or call provider
  • The project requires provider-agnostic telephony so the backend can be swapped later
  • The runtime supports stdio transport for MCP servers
  • A BYOK telephony arrangement needs a standard MCP wrapper

When not to use it

  • The agent runtime requires HTTP or SSE transport rather than stdio
  • Detailed, stable tool schemas are needed before integration — the tool list is not yet documented in the published facts
  • The use case has nothing to do with telephony or call providers
  • A production-grade, versioned API is required — the package is at version 0.1.2