Twilio MCP server
Twilio's official MCP server: drive SMS, voice, Verify, Lookup, and 1,400+ Twilio API endpoints as tools.
The Twilio MCP Server is Twilio's official integration from Twilio Labs that turns the entire Twilio platform into MCP tools an agent can call. Rather than ship a small hand-written tool set, it generates tools directly from Twilio's OpenAPI specifications, exposing well over 1,400 API endpoints across messaging, voice, Verify, Lookup, phone numbers, Studio, TaskRouter, Sync, Serverless, and more. Each endpoint becomes an MCP tool named after its OpenAPI operationId.
Because that surface is far larger than any model's context window can hold at once, the server is designed to be scoped down with the --services and --tags flags so you load only the APIs a given agent needs (for example just the core twilio_api_v2010 service, or only the IncomingPhoneNumber and Studio Flow tags). It runs locally over stdio via npx and authenticates with a Twilio Account SID plus an API Key and Secret passed as a single ACCOUNT_SID/API_KEY:API_SECRET argument, so an agent can send a text, place a call, verify a phone number, or look up carrier data without you writing any Twilio glue code.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Add to ~/.claude.json
{
"mcpServers": {
"twilio": {
"command": "npx",
"args": [
"-y",
"@twilio-alpha/mcp",
"YOUR_ACCOUNT_SID/YOUR_API_KEY:YOUR_API_SECRET",
"--services",
"twilio_api_v2010"
]
}
}
}claude mcp add twilio -- npx -y @twilio-alpha/mcp YOUR_ACCOUNT_SID/YOUR_API_KEY:YOUR_API_SECRET --services twilio_api_v2010Available tools
| Tool | Description |
|---|---|
| Messaging (twilio_api_v2010) | Send and manage SMS, MMS, and WhatsApp messages; list and inspect message records and media. |
| Voice (twilio_api_v2010) | Create and control outbound and inbound calls, recordings, and conferences. |
| Phone Numbers (twilio_api_v2010 IncomingPhoneNumber) | Search, buy, configure, and release Twilio phone numbers and their webhooks. |
| Verify (twilio_verify_v2) | Start and check phone, email, and TOTP verifications for one-time-passcode flows. |
| Lookup (twilio_lookups_v2) | Look up carrier, caller-name, line-type, and validation data for a phone number. |
| Studio (twilio_studio_v2) | Trigger and inspect Studio Flow executions for no-code communication workflows. |
| TaskRouter (twilio_taskrouter_v1) | Manage workspaces, workers, task queues, and routing of contact-center tasks. |
| Sync (twilio_sync_v1) | Read and write Sync documents, lists, maps, and streams for real-time state. |
| Serverless (twilio_serverless_v1) | Manage Twilio Functions services, environments, deployments, and builds. |
| Account Management (twilio_accounts_v1, twilio_api_v2010) | Manage subaccounts, balances, usage records, and account-level settings. |
What you can do with it
Send notifications from an agent
An agent drafts and sends an SMS or WhatsApp message through the messaging tools, then confirms delivery by reading the message status back.
Verify a phone number inline
Scope the server to the Verify and Lookup services so an agent can validate a number, check its line type, and start a one-time-passcode flow without custom code.
FAQ
- Is it free?
- The MCP server is free and open source under Twilio Labs, but the Twilio APIs it calls are billed per use against your Twilio account (messages, calls, lookups, and so on).
- Does it support remote/OAuth?
- Not yet. It runs locally over stdio via npx and authenticates with your Twilio Account SID plus an API Key and Secret; Twilio has noted that hosted, OAuth-style authentication is still being researched.
- How do I avoid overwhelming the model with thousands of tools?
- Use the --services and --tags flags to load only the APIs a given agent needs, for example a single service like twilio_api_v2010 or specific tags such as the IncomingPhoneNumber and Studio Flow endpoints.