Twilio MCP Server

Created By
YiyangLia year ago
A Model Context Protocol (MCP) server that enables Claude and other AI assistants to send SMS messages using Twilio.
Overview

what is Twilio MCP Server?

Twilio MCP Server is a Model Context Protocol (MCP) server that allows AI assistants like Claude to send SMS and MMS messages using Twilio's services.

how to use Twilio MCP Server?

To use the Twilio MCP Server, you need to configure it with your Twilio credentials and set it up in your Claude Desktop configuration. After setup, you can send messages through natural language commands.

key features of Twilio MCP Server?

  • Send SMS messages 📱
  • Pre-built prompts for common messaging scenarios 📝
  • Secure handling of Twilio credentials 🔒

use cases of Twilio MCP Server?

  1. Sending reminders via SMS.
  2. Sending creative messages like poems or notifications.
  3. Integrating SMS functionality into AI applications.

FAQ from Twilio MCP Server?

  • What format should phone numbers be in?

All phone numbers must be in E.164 format (e.g., +11234567890).

  • How do I secure my Twilio credentials?

Keep your Twilio credentials secure and never commit them to version control.

  • What should I do if I encounter an "Invalid credentials" error?

Double-check your ACCOUNT_SID and AUTH_TOKEN, and ensure they are correctly copied from the Twilio Console.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
YiyangLi
Star
2
Language
JavaScript
License
MIT license
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago