Twilio
by Twilio
Twilio's MCP server searches Twilio's documentation and API specifications. Two read-only tools, no sign-in. It cannot send an SMS, place a call, or touch your account — verified live 2026-08-17.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Twilio via MCP
https://mcp.twilio.com/docsWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Twilio Tools & Capabilities (2)
Fetch full parameter schemas and response details for one or more Twilio API operations or documentation articles. Use this after twilio__search to get the complete request body fields, path/query parameters, response schema, and curator guidance needed to actually call the API. Pass the id values exactly as returned by twilio__search.
Search Twilio documentation and API operations by natural language query. Use source="docs" for conceptual guides and setup questions, source="api" for finding specific API endpoints and operations, or source="all" (default) when unsure. Returns ranked documentation snippets and/or API operation summaries. Use twilio__retrieve with an id from API results to get full parameter schemas.
Read from the server on 2026-08-17, including each tool's own safety annotations.
Limits
- It reads documentation; it does not run anything. Twilio's Limitations section states the server does not execute API calls on your behalf. No tool on the live surface sends a message, places a call, provisions a number, or reads an account.
- Public specs only. Twilio states the index covers publicly available API specifications, published in the
twilio/twilio-oairepository. An API absent from a public OpenAPI spec is absent from the index, and no private or account-scoped material is reachable. - Public Beta, with no SLA. Twilio's own notice states that Public Beta products are not covered by the Twilio Support Terms or the Twilio Service Level Agreement, and that features may change before general availability. Support runs through a feedback email address and GitHub issues rather than standard channels.
- Result quality depends on your model. Twilio names this as a limitation in its own words: search result quality and how well your agent uses the results depend on the AI model powering the coding agent.
- Version defaults can mislead. Search returns the latest version unless you pin one. Twilio's worked example is Programmable Messaging, where
v2010is legacy andv1current — an agent that does not pin getsv1and may write code against the wrong generation. - Ten IDs per retrieve, ten results per search.
twilio__retrievecapsidsat 10 items;twilio__searchcapslimitat 10 with a default of 5, andtopicsat 4 of the 8 corpora. There is no pagination cursor on either tool. - Retrieve cannot lead. Its IDs must come verbatim from a prior search. There is no way to look up an operation by name, path, or a guessed ID.
- No idempotency or open-world declaration. Neither tool carries
idempotentHintoropenWorldHint. Those axes are unstated by the server, not denied. - The endpoint count is inconsistent across Twilio's own pages. The MCP documentation and the directory entry both say more than 1,800 endpoints; Twilio's "Building with AI" overview page says 1,500+ twice. We report both figures rather than picking one, and neither is verifiable from the handshake.
- We did not call either tool. Our check was a read-only
tools/listhandshake. Every behavioural claim above comes from the server's own schemas and descriptions, or from Twilio's published documentation.
Frequently asked questions
Can the Twilio MCP server send an SMS or place a call?
No. The server exposes exactly two tools, twilio__search and twilio__retrieve, and we read both schemas live on 2026-08-17. Neither takes a phone number, a message body, or an account credential. Twilio's own documentation states the limitation directly under a Read-only heading: the server does not execute API calls on your behalf. It returns specifications, not messages.
Do you need a Twilio account to use the Twilio MCP server?
No. Twilio's documentation lists no authentication as a feature and states that no Twilio account or API keys are needed, because the server indexes public API specifications only. Our anonymous handshake on 2026-08-17 returned both tool definitions with no credential, and the server publishes no OAuth protected resource descriptor. The prerequisites are a supported agent and network access.
What is the difference between twilio__search and twilio__retrieve?
Search takes a natural-language question and returns ranked results with IDs. Retrieve takes those IDs and returns full parameter and response schemas. Twilio calls this a search-then-retrieve workflow and says the two-step design keeps context usage efficient by fetching full detail only for operations your agent actually needs. Retrieve cannot be called first, because its IDs come from search.
Why are the tools named with a double underscore?
Twilio namespaced them itself rather than relying on the client. Both tools use generic verbs, search and retrieve, which would collide with any other connector exposing the same words. Prefixing twilio__ into the tool name makes the routing unambiguous at the model's decision point regardless of whether your MCP client adds its own server prefix. It is a defensive naming choice.
Is the Twilio MCP server covered by Twilio's SLA?
No. Twilio labels both the MCP server and Twilio Skills as Public Beta products, and states that Public Beta products are not covered by the Twilio Support Terms or the Twilio Service Level Agreement. The same notice appears on the docs page and in the twilio/ai repository, and warns that features may change before general availability.
Which Twilio products does the MCP server cover?
Publicly documented ones. The live search schema enumerates 42 product values including messaging, voice, verify, video, flex, taskrouter, sendgrid and lookups. Twilio's documentation says the index covers all publicly available Twilio OpenAPI specs plus Twilio docs, support articles, SendGrid documentation and Segment documentation. Anything absent from a public OpenAPI spec is not indexed.
Will the Twilio MCP server ever be able to call Twilio APIs directly?
Twilio says that is planned, not shipped. Its documentation lists execute-ready, OAuth-authenticated MCP tools under What's next, alongside Twilio Skills and expanded documentation coverage. Treat the read-only boundary as the current scope of this connector rather than a permanent guarantee, and re-check the tool list after any Public Beta milestone.
Sources
- Twilio Docs, "Twilio MCP server" (retrieved 2026-08-17, HTTP 200; page metadata gives
dateModified2026-07-20). This is the exactdocumentationvalue in Anthropic's directory entry. Source for the two-tool table, the search-then-retrieve workflow, the no-authentication statement, the Limitations section, the Public Beta notice, the indexed corpora, the roadmap, and per-client setup. Fetched as clean Markdown by appending.mdto the page URL, an affordance Twilio'sdocs/llms.txtadvertises. · retrieved 2026-08-17 - Twilio Docs, "Twilio Skills for AI coding agents" (retrieved 2026-08-17, HTTP 200;
dateModified2026-07-09). The Skills-versus-MCP distinction and thetwilio-developer-kitplugin. · retrieved 2026-08-17 - Twilio Docs, "Building with AI" (retrieved 2026-08-17, HTTP 200). Source of the 1,500+ endpoint figure that disagrees with the MCP page's 1,800. · retrieved 2026-08-17
- Twilio documentation machine index (retrieved 2026-08-17, HTTP 200, 376KB of genuine text). Resolved the MCP page slug without guessing. · retrieved 2026-08-17
twilio/airepository README andmcp/README.md(raw files retrieved 2026-08-17, HTTP 200). Twilio's own repository independently confirms the endpoint, the streamable-HTTP transport, the no-authentication posture and the same two tool names — a second vendor source that corroborates the handshake. · retrieved 2026-08-17- Twilio Terms of Service (retrieved 2026-08-17, HTTP 200; page states last updated 16 July 2026). Consulted for beta and service terms. Twilio's separate beta-terms URL returned HTTP 403 to our client, so we make no claim about its contents. · retrieved 2026-08-17
- Twilio privacy pages — and (both retrieved 2026-08-17, HTTP 200). Neither carries a section on MCP or AI assistants. · retrieved 2026-08-17
- Live
tools/listhandshake againsthttps://mcp.twilio.com/docs— two tools with full descriptions, input schemas and safety annotations, returned anonymously (2026-08-17). Schema committed atdocs/marketing/data/tool-schemas/twilio.tools.json. · retrieved 2026-08-17 - Auth probe:
https://mcp.twilio.com/.well-known/oauth-protected-resourceand the same path under/docsboth returned HTTP 404 with a Twilio-formatted error body (2026-08-17). No RFC 9728 descriptor exists, which is consistent with the anonymous handshake and with Twilio's own no-authentication statement. · retrieved 2026-08-17 - Anthropic Connectors Directory entry — . Tier, categories, endpoint, transport, auth posture and both tool names, read from our committed directory snapshot dated 2026-08-16. · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Communication
- Developer
- Twilio
- Tools
- 2
- Domain
- mcp.twilio.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.