AgentMail
Give an AI agent its own email inbox: create inboxes, read threads and send mail to anyone.
Searches Twilio's documentation and API specifications.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Twilio MCP server is a documentation search engine, not the Twilio API. It exposes two read-only tools that query Twilio's docs and OpenAPI specifications and return parameter schemas on demand. It cannot send a message, place a call, buy a number, or read your account. Its endpoint path is literally /docs, and no sign-in is required.
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.
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.
twilio/twilio-oai repository. An API absent from a public OpenAPI spec is absent from the index, and no private or account-scoped material is reachable.v2010 is legacy and v1 current — an agent that does not pin gets v1 and may write code against the wrong generation.twilio__retrieve caps ids at 10 items; twilio__search caps limit at 10 with a default of 5, and topics at 4 of the 8 corpora. There is no pagination cursor on either tool.idempotentHint or openWorldHint. Those axes are unstated by the server, not denied.tools/list handshake. Every behavioural claim above comes from the server's own schemas and descriptions, or from Twilio's published documentation.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.
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.
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.
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.
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.
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.
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.
dateModified 2026-07-20). This is the exact documentation value 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 .md to the page URL, an affordance Twilio's docs/llms.txt advertises. · retrieved 2026-08-17dateModified 2026-07-09). The Skills-versus-MCP distinction and the twilio-developer-kit plugin. · retrieved 2026-08-17twilio/ai repository README and mcp/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-17tools/list handshake against https://mcp.twilio.com/docs — two tools with full descriptions, input schemas and safety annotations, returned anonymously (2026-08-17). Schema committed at docs/marketing/data/tool-schemas/twilio.tools.json. · retrieved 2026-08-17https://mcp.twilio.com/.well-known/oauth-protected-resource and the same path under /docs both 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-17Connect Twilio once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.