Twilio Manager

Twilio Manager MCP provides a standardized Model Context Protocol interface to manage Twilio resources such as subaccounts, phone numbers, and regulatory bundles. It supports both direct local control via standard MCP clients and real-time updates through Server-Sent Events, making it easy to integrate Twilio operations into your automation workflows and AI assistants.

How to use

You interact with the MCP server through configured MCP clients or tools that understand MCP, such as Cursor or Claude Desktop. You can choose between three primary usage patterns: direct local control via a stdio-based command, a preconfigured UVX setup for seamless integration, or an SSE endpoint for live updates.

Available operations include listing Twilio subaccounts, retrieving numbers for a subaccount, transferring numbers between subaccounts, and obtaining regulatory bundle SIDs. Use these operations to automate common Twilio management tasks directly from your conversational assistant or automation workflow.

How to install

Prerequisites you need before installing:

• uv command-line tool installed (for managing MCP runs)
• Docker (optional, for containerized deployment with a reverse proxy)
• Git and a supported runtime environment for your chosen MCP client

Step-by-step setup

# Prerequisites
# Install uv (examples shown for common platforms)
brew install uv

# or install uv on Windows
# powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

# or install uv on Linux
# curl -LsSf https://astral.sh/uv/install.sh | sh

# Clone the MCP server project
git clone https://github.com/yourusername/twilio_manager_mcp.git
cd twilio_manager_mcp

# Install dependencies for development/usage
uv sync

Configuration steps include placing credentials and MCP wiring files in the project directory.

# Credentials for Twilio
TWILIO_ACCOUNT_SID=your_account_sid
TWILIO_AUTH_TOKEN=your_auth_token

# MCP wiring for Cursor/Claude Desktop
# Create a .cursor/mcp.json with the MCP server configurations shown below

Configuration and usage notes

The server can be configured to run in multiple modes. You can run it via a direct stdio configuration, use uvx for plug-and-play integration, or expose an SSE endpoint for live updates. The following configuration examples illustrate three labeled MCP connections and how to wire them into your tools.

Environment variables shown here are the credentials you must provide to enable Twilio access and to authenticate with MCP clients.

{
  "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 deployment and SSL

You can run Twilio Manager MCP with Docker for easier deployment and automatic HTTPS via a reverse proxy.

Prepare environment variables in a .env file and then start the services with Docker Compose.

# Example .env contents
TWILIO_ACCOUNT_SID=your_account_sid
TWILIO_AUTH_TOKEN=your_auth_token

# Traefik domain and contact for TLS
DOMAIN_NAME=yourdomain.com
ACME_EMAIL=user@yourdomain.com

# Optional address fields
ADDRESS_CUSTOMER_NAME=
ADDRESS_FRIENDLY_NAME=
ADDRESS_STREET=
ADDRESS_CITY=
ADDRESS_REGION=
ADDRESS_POSTAL_CODE=
ADDRESS_ISO_COUNTRY=

docker-compose up -d

Available tools

list_twilio_subaccounts

Lists all Twilio subaccounts available under your main account

get_account_phone_numbers

Retrieves phone numbers associated with a specific subaccount

get_all_phone_numbers

Transfers or copies phone numbers between subaccounts as needed

get_regulatory_bundle_sid

Fetches the regulatory bundle SID for a given subaccount