Twilio MCP Server

The Twilio Alpha MCP Server is Twilio's official Model Context Protocol server. It opens all of Twilio's public APIs — from SMS and voice calls to WhatsApp, email, and video — to MCP-capable AI clients such as Claude Desktop, Claude Code, Cursor, and Codex. The open-source repository at twilio-labs/mcp contains the source code, configuration examples, and the MIT license. According to the provider, the server is built on the Model Context Protocol (MCP), the open standard from Anthropic that standardizes how AI agents discover and invoke external services.

What is the Twilio Alpha MCP Server

Model Context Protocol decouples AI agents from manually integrating individual tools. Without MCP, a developer must manage SMS sending, voice call control, or message queries as individual, hardcoded integrations per agent. Scaling this across dozens of agents creates a maintenance burden. MCP solves this through a shared protocol standard: the agent asks the MCP server which tools are available, selects the right one, and calls it consistently. The Twilio Alpha MCP Server makes all public Twilio APIs accessible through this mechanism.

The server is structured as a monorepo at twilio-labs/mcp and contains two main packages: @twilio-alpha/mcp for full Twilio API access and openapi-mcp-server for generating custom MCP servers from OpenAPI specifications. The mcp package is the focus of this catalog entry.

Prerequisites

According to the provider, using the Twilio Alpha MCP Server requires an active Twilio account with an API key and API secret, plus an MCP-capable AI client. Twilio offers a free trial for getting started. A Twilio account with valid credentials is the only platform-side requirement; on the client side, a compatible MCP client is needed, such as Claude Desktop, Claude Code, Cursor, or Codex.

Features: All Twilio APIs as AI Tools

According to the provider, the server exposes all public Twilio APIs as MCP tools. In practice, this means an AI agent can send SMS messages, initiate and control voice calls, send WhatsApp messages, manage conversation threads, deliver Verify verification codes, query messaging services, and much more — all through a unified MCP tool call. The --services and --tags parameters allow selective restriction of the exposed APIs, conserving context window space and loading only the Twilio services actually needed.

This selectivity is especially useful in larger projects: a developer who only needs SMS functionality activates only the Messaging service. Someone automating voice calls loads the Voice service. This granularity reduces the number of tools in the AI client's context window and improves the agent's focus.

Setup and Configuration

According to the provider, the quickest setup method is using npx without a local installation. Client configuration is done through a JSON structure that tells the MCP client how to start the server:

{
  "mcpServers": {
    "twilio": {
      "command": "npx",
      "args": [
        "-y",
        "@twilio-alpha/mcp",
        "ACCOUNT_SID/API_KEY:API_SECRET"
      ]
    }
  }
}

Alternatively, the repository can be cloned and the server built locally. For production environments, the provider recommends using API keys rather than master credentials, since API keys can be scoped granularly and revoked at any time.

Security Recommendations per the Provider

Twilio explicitly recommends against running the Twilio Alpha MCP Server alongside community MCP servers, to minimize the risk of prompt injection attacks. Because a compromised community server could theoretically trigger tool calls against the Twilio server, the number of concurrently running MCP servers should be limited to trusted, official sources. This recommendation is especially relevant in environments where the Twilio account contains live customer data or executes billable actions such as SMS sending and voice calls.

Measurable Benefits per the Provider

According to the Twilio blog post, internal comparison measurements were made between an AI agent with and without MCP. Significant improvements in task completion time were observed, along with a reduction in required API calls and a decrease in human interventions. The success rate remained stable while developer complexity decreased. These measurements should be understood as an indication of potential value — they relate to specific test scenarios and are not independent third-party evaluations.

Scope and Differentiation

The Twilio Alpha MCP Server differs from community implementations in that it is maintained directly by Twilio's ETI team and draws on Twilio's public API specification. The second component of the monorepo, openapi-mcp-server, is a generic tool for creating custom MCP servers from arbitrary OpenAPI specifications. This catalog entry refers to the mcp package with full Twilio API access.

FAQ

Is the Twilio Alpha MCP Server free? The server itself is open source under the MIT license and free to use. Costs arise from the Twilio account and the Twilio services used: SMS sending, voice calls, Verify, and other services are billed by consumption. Current pricing is available at twilio.com/pricing. The GitHub API reported exactly 109 stars on 2026-09-08; this is a snapshot of repository popularity, not evidence of security, quality, or long-term maintenance.

Why "Alpha"? The "Alpha" qualifier signals that the server is still in an early stage of development. API calls and configuration formats may change. For production use, following the changelog in the repository is recommended.

Can I expose only specific Twilio APIs? Yes. The --services and --tags parameters allow targeted filtering of the exposed APIs. This is especially useful when only a subset of Twilio is needed and the AI client's context window should not be unnecessarily loaded.

Twilio account with API key and API secret, plus an MCP-capable AI client such as Claude Desktop, Claude Code, Cursor, or Codex.

In the MCP client configuration, set npx -y @twilio-alpha/mcp ACCOUNT_SID/API_KEY:API_SECRET as the command. Alternatively, clone the repository and build locally. Use --services and --tags to restrict the API scope.

npx -y @twilio-alpha/mcp ACCOUNT_SID/API_KEY:API_SECRET

Twilio API key and API secret (format: ACCOUNT_SID/API_KEY:API_SECRET). API keys are scoped granularly and revocable.

Depends on the permissions of the API key used. Per the provider: use dedicated API keys with minimal scope rather than master credentials.

The server forwards tool calls to Twilio APIs. Message content, phone numbers, and other user data are processed according to the Twilio privacy policy.

Per the provider, community MCP servers should not run alongside this server to minimize prompt injection risks. Billable actions such as SMS sending can be triggered unintentionally by faulty agent prompts.