mcp-twilio-sms
Allows sending SMS messages and checking their delivery status via the Twilio API.
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., "@mcp-twilio-sms send an SMS to +1234567890 saying 'Hello from Claude!'"
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.
MCP Twilio SMS
MCP server that lets Claude send SMS text messages via Twilio. Single-file Python server (server.py) exposing two MCP tools: send_sms and get_sms_status.
How It Works
Claude → send_sms(to, body) → Twilio API → SMS delivered
Claude → get_sms_status(message_sid) → Twilio API → delivery statusThe server speaks MCP over stdio. Claude (Code or Desktop) launches it as a subprocess, Twilio credentials are supplied via environment variables, and the two tools wrap the official twilio Python SDK.
Related MCP server: twilio-mcp
Tools
send_sms
Send a text message. Parameters:
to— Recipient phone number in E.164 format (e.g.+33612345678)body— Message text (max 1600 characters)from_number— Optional sender override (default:TWILIO_PHONE_NUMBERenv var)
Returns message_sid, status, to, from, and segments.
get_sms_status
Check delivery status of a sent message by its message_sid. Returns one of: queued, sending, sent, delivered, failed, or undelivered (plus error_code/error_message on failure).
Setup
1. Prerequisites
uv — install with
curl -LsSf https://astral.sh/uv/install.sh | shPython ≥ 3.11 (uv will fetch it if missing)
A Twilio account
2. Get Twilio credentials
From the Twilio Console:
Copy your Account SID and Auth Token from the dashboard.
Get an SMS-capable phone number (Console → Phone Numbers → Buy a number, or use the trial number). It must be in E.164 format, e.g.
+1234567890.
Trial accounts can only send SMS to phone numbers you have verified in the Console (Verified Caller IDs), and messages are prefixed with a trial notice. Upgrade the account to remove both limits.
3. Install dependencies
git clone git@github.com:sebastienfi/mcp-twilio-sms.git
cd mcp-twilio-sms
uv sync4. Configure secrets
Create a secrets file (shared with other MCP servers) and lock it down:
mkdir -p ~/.config/mcp
cat > ~/.config/mcp/secrets.env <<'EOF'
TWILIO_ACCOUNT_SID=ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
TWILIO_AUTH_TOKEN=your-auth-token
TWILIO_PHONE_NUMBER=+1234567890
EOF
chmod 600 ~/.config/mcp/secrets.envSee .env.example for the full list of variables.
5. Verify it runs
# Load secrets and start the server (Ctrl-C to stop — it waits for a client on stdio)
set -a; source ~/.config/mcp/secrets.env; set +a
uv run python server.pyThe server has no console UI; it waits for an MCP client on stdio. Register it with Claude (below) to actually use it.
6. Register with Claude Code
Add to ~/.claude.json under mcpServers (use absolute paths):
{
"twilio-sms": {
"command": "/bin/bash",
"args": [
"-c",
"set -a; source /Users/you/.config/mcp/secrets.env; set +a; exec /opt/homebrew/bin/uv run --directory /path/to/mcp-twilio-sms python server.py"
]
}
}Or with the CLI:
claude mcp add twilio-sms -- /bin/bash -c \
"set -a; source ~/.config/mcp/secrets.env; set +a; exec uv run --directory $(pwd) python server.py"Restart Claude Code, then confirm with /mcp that twilio-sms is connected.
7. Register with Claude Desktop
Add the same block to claude_desktop_config.json:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Use absolute paths for both uv and the project directory, then restart Claude Desktop.
Running directly
server.py carries PEP 723 inline metadata, so it runs standalone without uv sync:
uv run --script server.pyDevelopment
uv sync # Install dependencies
uv run python server.py # Run the MCP server (stdio transport)No test suite or linter is configured.
License
Available Tools
2 toolsget_sms_statusA
Check the delivery status of a sent SMS.
USAGE:
Call after send_sms() to verify delivery
Delivery confirmation may take a few seconds
STATUS VALUES:
queued: Message is queued for sending
sending: Message is being sent
sent: Message was sent to carrier
delivered: Carrier confirmed delivery to recipient
failed: Message could not be sent
undelivered: Carrier could not deliver the message
Args: message_sid: The message SID returned by send_sms (e.g. "SMxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx")
Inputs: message_sid (required). Returns: result
send_smsA
Send an SMS text message via Twilio.
WORKFLOW:
Call send_sms(to="+33612345678", body="Your message here")
Get back a message_sid and status
Optionally call get_sms_status(message_sid=...) later to confirm delivery
PARAMETERS:
to: Recipient phone number in E.164 format ("+33612345678" for France, "+15551234567" for US). Must include country code with + prefix.
body: The text message content. Max 1600 characters (messages over 160 characters are split into segments and billed per segment).
from_number: Override the sender phone number. Default: TWILIO_PHONE_NUMBER env var. Must be a Twilio number you own.
RETURNS:
message_sid: Unique identifier for tracking this message
status: Initial status (typically "queued")
to/from: The phone numbers used
segments: Number of message segments (billing units)
TIPS:
Keep messages under 160 characters for 1 segment (cheapest)
Unicode characters (accents, emojis) reduce the limit to 70 chars/segment
Use get_sms_status() to verify delivery if needed
Args: to: Recipient phone number in E.164 format (e.g. "+33612345678") body: The text message content (max 1600 characters) from_number: Sender phone number override (default: TWILIO_PHONE_NUMBER env var)
Inputs: to (required), body (required), from_number. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: send_sms sends a message, get_sms_status checks delivery status. There is no overlap or ambiguity; the workflow explicitly links them.
Both tools use a consistent verb_noun snake_case pattern (send_sms, get_sms_status). The naming is predictable and easy to understand.
Two tools cover the core send-and-verify workflow, which is focused and appropriate for a minimal SMS server. It is slightly under the typical 3-15 range but each tool earns its place without redundancy.
The surface covers sending an SMS and checking its status, which are the essential operations. Minor gaps exist (e.g., listing sent messages or retrieving full message details), but agents can work around them for the stated purpose.
Maintenance
Related MCP Connectors
Twilio MCP Pack — send SMS, list messages, make calls via Twilio REST API.
MCP server for customer-io
The Mobile Text Alerts SMS MCP server enables your AI to send SMS messages & manage contacts
MCP server for SuperPhone — contacts, conversations, tags and consent-based text messages.
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.3 npm5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Twilio communications, enabling SMS/MMS sending, message listing, outbound calls, and phone number lookup.MIT
- AlicenseAqualityDmaintenanceMCP server for sending SMS messages via SmsManager.cz HTTP API, supporting high, economy, and low delivery gateways.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides SMS sending, CSV bulk SMS, and voice calling capabilities via the Vonage API.Apache 2.0