Claude + Twilio: What the Integration Can (and Can't) Do in 2026
Yes — there’s an official Claude Twilio connector, but read the fine print: it searches Twilio’s docs, it does not send SMS. Twilio shipped a Claude connector and a Claude Code plugin on May 7, 2026, backed by its hosted MCP server at https://mcp.twilio.com/docs. That server needs no auth and touches no account — it indexes Twilio’s public API specs (1,800+ endpoints across 30+ products, plus SendGrid and Segment) so Claude can help you write correct Twilio code. It won’t fire a text message, buy a number, or place a call. Actually executing Twilio calls means running a separate, self-hosted alpha server with your own keys — and even then, everything happens inside a conversation you start, with no triggers watching for anything.
Here’s exactly what each piece does, how to set it up, where the limits bite, and what to use if you want Twilio work that runs on its own.
The official connector searches docs — it doesn’t execute
This is the trap worth internalizing. Twilio’s official connector is backed by the hosted Twilio MCP server (https://mcp.twilio.com/docs, public beta since May 7, 2026). It exposes two tools:
twilio__search— natural-language search across Twilio’s API and product documentation.twilio__retrieve— pulls full parameter and response schemas for a given endpoint.
That’s it. No auth, no account link, no execution. Ask Claude “how do I send an MMS with a media URL” and it retrieves the exact API shape and writes the code — but it will not call the API. So “connect Claude to Twilio and text a customer from chat” is not what the connector does.
To actually send messages, there’s a second, older, separate track: the Twilio Alpha MCP (@twilio-alpha/mcp on npm). It’s a self-hosted local server generated from Twilio’s OpenAPI specs that does execute API calls — send SMS, manage numbers, and so on — using your Account SID + API key. It’s alpha/experimental from Twilio’s Emerging Tech team, not covered by Twilio support or an SLA, and Twilio warns against running community Twilio MCPs alongside it.
How to set up each one
Docs search (official connector, no execution):
- In Claude, add the Twilio connector from the directory, or install the twilio-developer-kit plugin via Claude Code’s
/plugins. - Ask Claude to look up any Twilio endpoint or write code against it. No Twilio account needed — it’s reading public specs.
Actual execution (local alpha, your keys):
- Get your Account SID + API key from the Twilio console.
- Install and run
@twilio-alpha/mcpas a local MCP server in Claude Desktop or Claude Code (custom MCP connectors require a paid Claude plan). - Ask Claude to send a message or manage a number — it hits Twilio’s REST API with your credentials. Expect alpha rough edges, and remember US SMS needs A2P 10DLC registration first.
The limits that actually matter
Even with the alpha server executing calls, the shape is “an assistant you operate,” not “an agent that runs.” Three limits define it:
- The official connector can’t act at all. It searches docs. Sending anything requires the unsupported local alpha server plus your own keys.
- No triggers, no monitoring. MCP tools only run inside a conversation you start. There’s no “when a customer replies to an SMS, route it and log it” or “text everyone whose appointment is tomorrow.” Nothing fires on an inbound message or a webhook — you have to be there, prompting.
- Laptop-bound for anything scheduled. The nearest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on, event-driven messaging agent.
So Claude is great for “write and test this Twilio flow with me” and not built for “send and answer messages the moment things happen.”
If you want Twilio work that runs on its own: Carly
The moment you want something to happen over Twilio without you in the chat — text a reminder the day before an appointment, reply to an inbound SMS, send a verification code, notify a team when a call comes in — you’ve crossed past what Claude’s connector (or the alpha server) is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events, 24/7, in the cloud — driven by Twilio’s inbound-message and status webhooks, Carly acts when something happens; your laptop doesn’t need to be awake.
- Sends and receives on a schedule — appointment reminders, follow-ups, and confirmations go out on time without you in the loop.
- Ties messaging to the rest of your stack — connect an SMS to your calendar, CRM, email, and tasks in a single workflow.
- Builds the workflow for you — tell it “I’d like a system that texts a reminder the day before every booking and logs the reply” in plain English; it interviews you, then builds it with you. No prompt engineering.
Twilio is fully self-serve — sign up, get an Account SID + API keys, pay as you go — so Twilio connects to Carly via your own API key. Paste it on carlyassistant.com/integrations and Carly can do whatever the API allows: SMS, MMS, WhatsApp, Voice, Verify, and more.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations.
Claude vs Carly
| Claude (Twilio connector) | Claude (alpha local MCP) | Carly | |
|---|---|---|---|
| Search Twilio docs / write code | Yes | Yes | n/a |
| Send SMS / place calls | No | Yes (your keys, alpha) | Yes |
| Acts on triggers / events | No | No | Yes |
| Replies to inbound messages on its own | No | No | Yes |
| Works while laptop is closed | No | No (local server) | Yes (cloud) |
| Sends email as part of the flow | No | No | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | Pro $20 / Max $100–$200 | AI agents from $35/mo |
The official connector is a strong Twilio documentation and code helper. Carly is a teammate that sends and answers messages as events land.
Frequently Asked Questions
Does Claude work with Twilio?
Yes, with a big caveat. Twilio ships an official Claude connector and Claude Code plugin backed by its hosted MCP server — but that server only searches Twilio’s documentation and returns API schemas. It needs no account and cannot send messages or place calls. To actually execute Twilio calls, you run Twilio’s separate self-hosted alpha MCP server with your own API keys, which is experimental and unsupported.
Can Claude send an SMS from a chat?
Not with the official connector — that one is docs-search only. You can send SMS by running the local @twilio-alpha/mcp server with your Account SID and API key, but it’s alpha software with no SLA, and it still only acts inside a conversation you start (no triggers). For reliable, automated messaging, use an agent platform like Carly.
How do I connect Claude to Twilio?
For docs and code help, add the Twilio connector or install the twilio-developer-kit plugin in Claude Code — no account needed. For sending, install @twilio-alpha/mcp locally, add your Account SID + API key, and run it as a local MCP server in Claude Desktop or Claude Code (paid Claude plan required). US SMS requires A2P 10DLC registration.
Can Claude reply to incoming texts automatically?
No. MCP tools respond inside a chat you start — there are no inbound-message triggers, so Claude won’t answer a text or fire a reminder on its own. Carly runs on Twilio’s webhooks 24/7 in the cloud and can reply, send scheduled reminders, log messages to your CRM, and more. AI agents start at $35/month.
More: Claude connectors · Claude + SendGrid · Claude + Slack · Can Claude send emails · Claude vs Carly · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
