TwilioManager MCP
The TwilioManager MCP server enables programmatic management of Twilio resources through a standardized Model Context Protocol interface, providing seamless integration with AI assistants and development tools.
Core Capabilities:
List Twilio Subaccounts: Retrieve all subaccounts or filter by friendly name
Get Phone Numbers by Account: Fetch all phone numbers associated with a specific subaccount using the account SID
Transfer Phone Numbers: Move phone numbers between subaccounts (requires phone number SID, source account SID, and target account SID)
Retrieve Regulatory Bundle Information: Get regulatory bundle SIDs for subaccounts to manage compliance requirements
Integration Options:
Direct integration via uv/uvx
Server-Sent Events (SSE) for flexible deployment
Docker deployment with automatic HTTPS through Traefik reverse proxy
Compatible with Claude Desktop, Cursor, and other MCP-compatible AI assistants
Used for managing Twilio credentials and environment variables required for authentication with the Twilio API.
Enables direct interaction with Twilio's API for subaccount management, phone number control, regulatory compliance handling, and address management for compliance requirements.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TwilioManager MCP list all phone numbers for subaccount AC123456789"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Twilio Manager MCP
A Model Context Protocol (MCP) implementation for managing Twilio resources. This package provides tools for managing Twilio subaccounts, phone numbers, and regulatory bundles through a standardized MCP interface.
Features
List Twilio subaccounts
Get phone numbers associated with subaccounts
Transfer phone numbers between subaccounts
Get regulatory bundle SIDs
Support for both direct and Server-Sent Events (SSE) communication
Integration with Claude Desktop, Cursor, and other MCP-compatible tools
Related MCP server: Twilio MCP Server
Installation
Prerequisites
Install uv
On macOS:
brew install uvOn Windows:
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"On Linux:
curl -LsSf https://astral.sh/uv/install.sh | shProject Setup
Clone the repository:
git clone https://github.com/yourusername/twilio_manager_mcp.git
cd twilio_manager_mcpInstall dependencies using uv:
uv syncConfiguration
Create a
.envfile in the root directory with your Twilio credentials:
TWILIO_ACCOUNT_SID=your_account_sid
TWILIO_AUTH_TOKEN=your_auth_tokenConfigure MCP for your tool (Cursor, Claude Desktop, etc.) by creating a
.cursor/mcp.jsonfile:
{
"mcpServers": {
"twilio_manager_mcp_abs": {
"command": "uv",
"args": ["--directory", "/path/to/twilio_manager_mcp", "run", "mcp", "run", "./twilio_manager_mcp.py"],
"env": {
"TWILIO_ACCOUNT_SID": "your_account_sid",
"TWILIO_AUTH_TOKEN": "your_auth_token"
}
},
"twilio_manager_mcp_uvx": {
"command": "uvx",
"args": [ "twilio-manager-mcp" ],
"env": {
"TWILIO_ACCOUNT_SID": "your_account_sid",
"TWILIO_AUTH_TOKEN": "your_auth_token"
}
},
"twilio_manager_mcp_sse": {
"url": "http://localhost:8000/sse"
}
}
}Docker
You can run Twilio Manager MCP using Docker for easier deployment and management.
Using Docker Compose
The project includes a Docker Compose configuration that sets up:
The Twilio Manager MCP service
A Traefik reverse proxy with automatic HTTPS
Configure environment variables in your
.envfile:
# Twilio credentials
TWILIO_ACCOUNT_SID=your_account_sid
TWILIO_AUTH_TOKEN=your_auth_token
# Domain configuration for Traefik
DOMAIN_NAME=yourdomain.com
ACME_EMAIL=user@yourdomain.com
# Address details (optional)
ADDRESS_CUSTOMER_NAME=
ADDRESS_FRIENDLY_NAME=
ADDRESS_STREET=
ADDRESS_CITY=
ADDRESS_REGION=
ADDRESS_POSTAL_CODE=
ADDRESS_ISO_COUNTRY=Start the services:
docker-compose up -dThe application will be available at your configured domain with HTTPS enabled.
Using Docker Without Docker Compose
If you prefer to run just the Twilio Manager MCP container without Traefik:
Build the Docker image:
docker build -t twilio-manager-mcp .Run the container:
docker run -p 8000:8000 \
-e TWILIO_ACCOUNT_SID=your_account_sid \
-e TWILIO_AUTH_TOKEN=your_auth_token \
twilio-manager-mcpThe SSE endpoint will be available at http://localhost:8000/sse.
Usage
With Cursor, Claude Desktop, or other MCP-compatible tools
You have three options to use this MCP:
Direct UVX Integration (Recommended):
Use the
twilio_manager_mcp_uvxconfigurationThis is the simplest method and works out of the box with uvx
Direct UV Integration:
Use the
twilio_manager_mcp_absconfigurationRequires specifying the full path to your installation
SSE Server:
Use the
twilio_manager_mcp_sseconfigurationStart the SSE server first:
uvicorn twilio_manager_mcp_sse:app --host 0.0.0.0 --port 8000
Available Tools
Tool Name | Description |
| List all Twilio subaccounts |
| Get phone numbers for a specific subaccount |
| Transfer phone numbers between subaccounts |
| Get regulatory bundle SID for a subaccount |
Example Usage in Cursor/Claude Desktop
Once configured, you can use the tools directly in your AI assistant conversations:
List all subaccounts:
# The AI will automatically use the MCP to list all subaccounts
# No need to write code - just ask "List all Twilio subaccounts"Get phone numbers for a subaccount:
# Simply ask: "Show me all phone numbers for subaccount AC..."Direct Python Usage
For direct programmatic usage:
from mcp import ClientSession
from clients.client import MCPClient
async with MCPClient("uvx", ["twilio-manager-mcp"], env={}) as session:
# List available tools
tools = (await session.list_tools()).tools
# List all subaccounts
subaccounts = await session.invoke("list_twilio_subaccounts")
# Get phone numbers for a subaccount
numbers = await session.invoke("get_account_phone_numbers", {"account_sid": "AC..."})Project Structure
twilio_manager_mcp/
├── api/
│ └── async_twilio_api.py # Async Twilio API implementation
├── clients/
│ ├── client.py # Direct MCP client implementation
│ └── client_sse.py # SSE client implementation
├── twilio_manager_mcp.py # Core MCP server implementation
├── twilio_manager_mcp_sse.py # SSE server wrapper
├── requirements.txt # Project dependencies
└── README.md # This fileDevelopment
For development, you can use uv's virtual environment management:
# Create a virtual environment
uv venv
# Activate the virtual environment
source .venv/bin/activate # On Unix
.venv\Scripts\activate # On Windows
# Install dependencies in development mode
uv pip install -e .Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License
Available Tools
4 toolsget_account_phone_numbersC
Get all phone numbers associated with a Twilio subaccount
Inputs: account_sid (required).
get_all_phone_numbersC
Get all phone numbers associated with a Twilio subaccount
Inputs: source_account_sid (required), phone_number_sid (required), target_account_sid (required).
get_regulatory_bundle_sidC
Get the regulatory bundle SID for a Twilio subaccount
Inputs: subaccount_sid (required).
list_twilio_subaccountsB
List all Twilio subaccounts or filter by friendly name. Provide an empty string for all subaccounts
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Two tools have nearly identical purposes: 'get_account_phone_numbers' and 'get_all_phone_numbers' both retrieve phone numbers for Twilio subaccounts, creating clear ambiguity. The other two tools target distinct resources (regulatory bundles and subaccounts), but the overlap between the first two tools is significant and likely to cause misselection.
All tools follow a consistent verb_noun pattern (e.g., get_account_phone_numbers, list_twilio_subaccounts) with clear, descriptive names. The naming style is uniform across the set, making it easy to parse and understand the actions and targets.
With only 4 tools, the count feels thin for a server named 'TwilioManager MCP', which suggests broader Twilio API management. This limited set may not cover essential operations like sending messages, managing calls, or updating resources, making it borderline for the implied scope.
The tool surface is severely incomplete for Twilio management, lacking core functionalities such as sending SMS, making calls, or updating subaccounts. It focuses narrowly on retrieval operations (get/list) without create, update, or delete capabilities, leading to significant gaps that will hinder agent workflows.
Maintenance
Related MCP Connectors
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
Hosted CallRail MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Lets Claude, Cursor or any MCP client build voice agents and place real phone calls.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP (Model Context Protocol) server that lets users send SMS messages through Twilio API directly from Claude Desktop via natural language commands.20 npm5MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude and other AI assistants to send SMS and MMS messages using Twilio.19 npm15MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to initiate and manage real-time voice calls using Twilio and OpenAI's voice models.64MIT
- AlicenseNot gradedqualityDmaintenanceAn implementation of the Model Context Protocol (MCP) server that exposes Twilio APIs to AI assistants and tools, allowing them to interact with Twilio services through the MCP protocol.114MIT