Twilio MCP Monorepo

What is Twilio MCP Monorepo about?

Twilio MCP Monorepo provides a Model Context Protocol server that can either generate MCP tools directly from any OpenAPI spec or serve all public Twilio APIs as MCP tools. It enables AI assistants and other services to interact with Twilio functionality through a standardized protocol.

How to use Twilio MCP Monorepo?

The quickest way is to run the server with npx:

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

Replace the credential placeholder with your Twilio Account SID, API Key, and API Secret. Additional configuration can be supplied via command‑line flags, e.g., --services or --tags to limit which APIs are exposed, or --apiPath when using the OpenAPI MCP Server.

Key features of Twilio MCP Monorepo

• Two packages: mcp (full Twilio API exposure) and openapi-mcp-server (any OpenAPI spec).
• Fine‑grained filtering using --services and --tags to stay within LLM context limits.
• Simple execution through npx without a global install.
• Built‑in testing and linting scripts (npm test, npm run lint).
• Security recommendation: run only official Twilio MCP servers to avoid credential leakage.

Use cases of Twilio MCP Monorepo

• AI‑driven assistants that need to send SMS, make voice calls, or manage chats via Twilio.
• Tooling platforms that want to expose Twilio capabilities through a protocol‑agnostic interface.
• Rapid prototyping of services that consume any OpenAPI spec as MCP tools.
• Enterprise integrations where consistent model context exchange is required across multiple AI modules.

FAQ from the Twilio MCP Monorepo

Q: Do I need to install anything globally? A: No. The recommended approach is to run the server with npx, which fetches the package on demand.

Q: How do I limit the APIs exposed to stay within LLM token limits? A: Use the --services or --tags flags to select specific Twilio services.

Q: Can I serve my own OpenAPI definition? A: Yes. Use the openapi-mcp-server package and provide the spec path with --apiPath.

Q: What if I encounter authentication errors? A: Verify that the credential string follows ACCOUNT_SID/API_KEY:API_SECRET and that the API Key has the required permissions.

Q: Is there any risk in running community MCP servers alongside the official one? A: The ETI team recommends running only official Twilio MCP servers to prevent untrusted code from accessing your Twilio data.

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:

• MCP Package Documentation
• OpenAPI MCP Server 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 --services and --tags to filter which APIs to expose
• OpenAPI MCP Server: Use --apiPath to 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 --services or --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.