Twilio SMS Server
Provides tools for sending SMS messages via Twilio, including capabilities for sending plain text messages and pre-formatted greeting messages for special occasions.
Click on "Install 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., "@Twilio SMS ServerSend a text to +15550123456 saying 'I am running 5 minutes late.'"
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 SMS Server
A versatile SMS service that can run as both a Model Context Protocol (MCP) server for Claude Desktop and as a standalone REST API for cloud deployment.
๐ Two Deployment Modes
1. MCP Server Mode (Local with Claude Desktop)
Enables Claude and other AI assistants to send SMS messages through the Model Context Protocol.
2. Web API Mode (Cloud Deployment)
Standalone REST API that can be deployed to any cloud platform for web applications.
Related MCP server: Twilio MCP Server
โจ Features
๐ฑ Send SMS messages via Twilio
๐ REST API endpoints for web integration
๐จ MCP server for Claude Desktop integration
๐ Pre-built prompts for common messaging scenarios
๐ Secure handling of Twilio credentials
๐ณ Docker support for easy deployment
โ๏ธ Cloud deployment ready
๐ Requirements
Node.js >= 18
Twilio account with SMS capabilities
Environment variables for Twilio credentials
โ๏ธ Environment Setup
Create a .env file in the project root:
# Twilio Configuration (Required)
ACCOUNT_SID=your_twilio_account_sid_here
AUTH_TOKEN=your_twilio_auth_token_here
FROM_NUMBER=+1234567890
# Server Configuration (Optional, defaults to 3000)
PORT=3000๐ Installation & Usage
Local Development
```bash
Install dependencies
npm install
Build the project
npm run build
Run as MCP server (for Claude Desktop)
npm run start:mcp
Run as Web API server
npm run start:web
Development mode (rebuilds and starts web server)
npm run dev:web ```
๐ Web API Endpoints
When running in Web API mode, the following endpoints are available:
GET /
API documentation and usage examples
GET /health
Health check endpoint
POST /send-sms
Send an SMS message
Request Body:
{
"to": "+11234567890",
"message": "Your message here"
}Response:
{
"success": true,
"message": "Message sent successfully",
"messageSid": "SM...",
"to": "+11234567890",
"from": "+1234567890"
}POST /send-greeting
Send a greeting message for special occasions
Request Body:
{
"to": "+11234567890",
"occasion": "birthday",
"customMessage": "Optional custom message"
}๐ฅ๏ธ Claude Desktop Configuration (MCP Mode)
To use this server with Claude Desktop, add the following to your configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"twilio": {
"command": "npx",
"args": [
"-y",
"@yiyang.1i/sms-mcp-server"
],
"env": {
"ACCOUNT_SID": "your_account_sid",
"AUTH_TOKEN": "your_auth_token",
"FROM_NUMBER": "your_twilio_number"
}
}
}
}After updating the configuration, restart Claude Desktop. If connected successfully, you should see Twilio under the ๐จ menu.
โ๏ธ Cloud Deployment
Option 1: Railway
Connect your GitHub repository to Railway
Set environment variables in Railway dashboard
Deploy automatically
Option 2: Render
Connect your repo to Render
Create a new Web Service
Build command:
npm install && npm run buildStart command:
npm run start:webAdd environment variables
Option 3: Heroku
heroku create your-app-name
heroku config:set ACCOUNT_SID=your_sid
heroku config:set AUTH_TOKEN=your_token
heroku config:set FROM_NUMBER=your_number
git push heroku mainOption 4: Docker
# Build Docker image
docker build -t twilio-sms-server .
# Run container
docker run -p 3000:3000 \
-e ACCOUNT_SID=your_sid \
-e AUTH_TOKEN=your_token \
-e FROM_NUMBER=your_number \
twilio-sms-server๐งช Testing the API
Local Testing
# Start the server
npm run start:web
# Test health endpoint
curl http://localhost:3000/health
# Send a test SMS
curl -X POST http://localhost:3000/send-sms \
-H "Content-Type: application/json" \
-d '{"to": "+1234567890", "message": "Hello from the API!"}'
# Send a greeting
curl -X POST http://localhost:3000/send-greeting \
-H "Content-Type: application/json" \
-d '{"to": "+1234567890", "occasion": "birthday"}'๐ฌ Example Interactions with Claude (MCP Mode)
Here are some natural ways to interact with the server through Claude:
Simple SMS:
Send a text message to +11234567890 saying "Don't forget about dinner tonight!"Creative SMS:
Write a haiku about autumn and send it to my number +11234567890Greeting Messages:
Send a birthday greeting to +11234567890๐ Scripts Reference
npm run build- Build TypeScript to JavaScriptnpm run start:mcp- Start MCP server modenpm run start:web- Start web API server modenpm run dev:web- Development mode (rebuild + start web server)npm run watch- Watch TypeScript files for changes
โ ๏ธ Important Notes
Phone Number Format: All phone numbers must be in E.164 format (e.g., +11234567890)
Twilio Trial Accounts: Can only send messages to verified phone numbers
Rate Limits: Be aware of your Twilio account's rate limits and pricing
Security: Keep your Twilio credentials secure and never commit them to version control
Environment Variables: Use
.envfile for local development, set via platform for cloud deployment
๐ Troubleshooting
Common Errors and Solutions:
"Phone number must be in E.164 format"
Ensure phone number starts with "+" and includes country code
"Invalid credentials" / "accountSid must start with AC"
Verify your ACCOUNT_SID and AUTH_TOKEN from Twilio Console
Ensure environment variables are properly loaded
"Invalid 'To' Phone Number"
For trial accounts: Verify the destination number in Twilio Console
For paid accounts: Ensure the number format is correct
"Environment variable is required"
Check that
.envfile exists and contains all required variablesFor cloud deployment, ensure environment variables are set in platform settings
๐ค Contributing
Contributions are welcome! Please read our contributing guidelines before submitting pull requests.
๐ License
This project is licensed under the MIT License - see the LICENSE file for details.
๐ Security
Please do not include any sensitive information (like phone numbers or Twilio credentials) in GitHub issues or pull requests.
Available Tools
1 toolsend-messageC
Send an SMS message via Twilio
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Recipient phone number in E.164 format (e.g., +11234567890) | |
| message | Yes | Message content to send |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Send an SMS message via Twilio' implies a write operation, it doesn't disclose critical behavioral traits like authentication requirements, rate limits, cost implications, error conditions, or what happens on success/failure. This leaves significant gaps for an agent to understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with a single, clear sentence that states the tool's purpose without any wasted words. It's appropriately sized for a simple tool with two parameters and no complex context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool (sending messages) with no annotations and no output schema, the description is insufficiently complete. It doesn't address what the tool returns, error conditions, authentication needs, or operational constraints that would help an agent use it correctly. The high schema coverage doesn't compensate for these behavioral gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with both parameters ('to' and 'message') well-documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline of 3 for high schema coverage without adding value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Send') and resource ('SMS message via Twilio'), providing a specific verb+resource combination. However, with no sibling tools mentioned, there's no opportunity to distinguish from alternatives, which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v2025.2.24- First observed
send-message
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'send-message' has a clear and distinct purpose for sending SMS messages via Twilio.
The single tool name 'send-message' follows a clear verb_noun pattern (send + message). Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions.
One tool is too few for a server named 'Twilio SMS Server', which suggests a broader SMS functionality scope. Twilio's API typically supports operations like listing messages, checking delivery status, or managing phone numbers, making a single send tool feel incomplete and thin for the domain.
The tool surface is severely incomplete for an SMS server. While sending messages is a core function, there are obvious gaps such as retrieving sent messages, checking message status, or managing SMS-related resources, which are essential for typical SMS workflows and could cause agent failures.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
The Mobile Text Alerts SMS MCP server enables your AI to send SMS messages & manage contacts
Phone, SMS & email for AI agents โ one remote MCP endpoint, OAuth login, zero install.
Build and send email, SMS, and push straight from your AI agent.
Twilio MCP Pack โ send SMS, list messages, make calls via Twilio REST API.
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.205MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude and other AI assistants to send SMS and MMS messages using Twilio.2015MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with all Twilio APIs through the Model Context Protocol. Supports SMS, voice, messaging, and other Twilio services with secure authentication and configurable API filtering.-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered SMS messaging through Twilio with automatic conversation threading, message status tracking, and webhook support for receiving inbound messages.801MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mustafa-boorenie/twilio_sms_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server