Twilio MCP Server: Tools, Setup and Security

Twilio's Alpha MCP server turns Twilio's public APIs into tools an AI assistant can call, such as sending an SMS or managing phone numbers. Twilio Labs publishes it as an open-source package that runs on your machine with your Twilio API key.

Checked against: Twilio's MCP monorepo README on 28 October 2026. eSEOspace did not install or test this server.

At a glance

What it can do

The monorepo holds two packages:

• mcp: an MCP server for all of Twilio's public API.
• openapi-mcp-server: a server that serves any OpenAPI spec you point it at with --apiPath.

Twilio does not publish a fixed tool list, because tools are generated from its OpenAPI specs. Which tools appear depends on the filters you set:

• --services: service names that match spec files in Twilio's OpenAPI repo, for example twilio_api_v2010.
• --tags: tags on individual endpoints, for example Api20100401IncomingPhoneNumber.

Twilio's launch post from 1 April 2025 uses sending an SMS as its example. It says filtering is needed because the full tool set would exceed most model context limits. The post also advises adding your Account SID and service SIDs to project instructions, because the model does not always set them correctly.

How to connect it

The README's quick start uses npx in a client config such as Claude Desktop's:

{
  "mcpServers": {
    "twilio": {
      "command": "npx",
      "args": [
        "-y",
        "@twilio-alpha/mcp",
        "YOUR_ACCOUNT_SID/YOUR_API_KEY:YOUR_API_SECRET"
      ]
    }
  }
}

Add --services or --tags after the credentials to load only the APIs you need. Twilio's API keys docs explain how to create the key and secret. The launch post also describes building from source: clone the repo, run npm install and npm run build, then point node at the built index.js.

If authentication fails, Twilio says to check the credential format and the key's permissions.

Security notes

• Twilio's own warning. The README says Twilio's ETI team advises users "to avoid installing or running any community MCP servers alongside our official ones," to guard against injection attacks.
• Credentials on disk. The API key and secret sit in your client config as a command argument. Use a dedicated key you can revoke, and keep the file private.
• Real-world actions. Tools can send messages and change account resources, which reaches real people and can run up Twilio usage. Load only the services you need.
• Local only. The launch post says the server is limited to local execution with no user authentication support, and calls authentication the biggest blocker to running MCP servers in shared environments.
• Alpha status. Twilio brands this as Alpha and invited feedback at launch. Do not treat it as a production service.

A local server that holds an account-wide key is a valuable target. Read MCP secret leakage and the MCP Security Center. For local servers, see sandboxing local MCP servers.

Alternatives

• HighLevel MCP server: a hosted server with messaging and CRM operations under OAuth.
• Front MCP server: sends replies across shared inbox channels with a separate send scope.
• Intercom MCP server: support conversations with mostly read-only tools.

Next step

If you only need SMS, load a single service with --services and use a test account first. If you want Twilio actions inside a custom agent with proper auth and logging, talk to our MCP development team, or browse the MCP server directory.

Frequently asked questions