About Twilio MCP Monorepo
The Twilio MCP Monorepo exposes Twilio's public APIs as MCP tools for AI assistants and includes a generator that converts OpenAPI specs into MCP tools. It suits developers who want agents to operate a Twilio account.
Key features
- 01Exposes all Twilio public APIs as MCP tools
- 02OpenAPI-to-MCP tool generator
- 03Filtering APIs by services and tags
- 04Quick setup via npx configuration
Use cases
- 01Letting an AI assistant send messages or manage Twilio resources
- 02Loading only selected APIs to limit context size
- 03Generating MCP servers from other OpenAPI specifications
MCP support
The project is an MCP server that exposes Twilio API operations as MCP tools to compatible AI clients. Usage requires Twilio Account SID and API key credentials.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README

Twilio MCP Monorepo
This is a monorepo for the Model Context Protocol server that exposes all of Twilio APIs.
What is MCP?
The Model Context Protocol (MCP) is a protocol for exchanging model context information between AI tools and services. This implementation allows you to expose Twilio's APIs to AI assistants and other tools that support the MCP protocol.
Packages
This monorepo contains two main packages:
- mcp - MCP Server for all of Twilio's Public API
- openapi-mcp-server - An MCP server that serves the given OpenAPI spec
Each package has its own comprehensive README with detailed documentation:
Quick Start
The easiest way to get started is by using npx:
{
"mcpServers": {
"twilio": {
"command": "npx",
"args": [
"-y",
"@twilio-alpha/mcp",
"YOUR_ACCOUNT_SID/YOUR_API_KEY:YOUR_API_SECRET"
]
}
}
}
Visit Twilio API Keys docs for information on how to find/create your API Key and Secret.
Security Recommendations
To guard against injection attacks that may allow untrusted systems access to your Twilio data, the ETI team advises users of Twilio MCP servers to avoid installing or running any community MCP servers alongside our official ones. Doing so helps ensure that only trusted MCP servers have access to tools interacting with your Twilio account, reducing the risk of unauthorized data access.
Basic Configuration Options
Both packages accept configuration parameters. Here's a brief overview:
- MCP Server: Use
--servicesand--tagsto filter which APIs to expose - OpenAPI MCP Server: Use
--apiPathto specify OpenAPI spec files location
For complete configuration details, refer to the package-specific documentation linked above.
Development
# Run tests
npm test
# Run linting
npm run lint
# Fix linting issues
npm run lint:fix
Troubleshooting Common Issues
- Context Size Limitations: Due to LLM context limits, load specific APIs using
--servicesor--tags - Authentication Issues: Verify your Twilio API credentials format and permissions
- API Versioning: Check you're using the correct API version (v1, v2, v3) for your needs
For detailed troubleshooting guidance, see the package-specific documentation.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the ISC License - see the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.