Who it is for
Developers writing code against Twilio APIs.
Search Twilio API specs and docs without loading them wholesale
Overview
Twilio's connector does not operate an account. It searches Twilio's documentation and API surface, stated at more than 1,800 endpoints, across voice, email, SMS and RCS, identity, customer data, contact centre and conversational AI, and returns the specific specs and code patterns a task needs. The point is context economy: fetching the exact parameter schema for one operation rather than pulling whole reference pages into a session. The endpoint answered an unauthenticated tools/list and returned exactly the two tools published. Twilio is the author and the connector carries the partner tier, with documentation available.
Developers writing code against Twilio APIs.
The two tools are `twilio__search` and `twilio__retrieve`, a find-then-expand pair over documentation and API operations. Neither touches a Twilio account, so this is a reference surface rather than an operational one.
Availability
Twilio is listed in the Claude connectors directory only. Twilio has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.
The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.
Claude listing
Twilio publishes 2 tools to Claude, a deliberately narrow surface; only 5.3% of the 1,253 Claude-listed connectors expose fewer.
The median Claude-listed connector filed under Communication publishes 11, so this one sits 9 tools below its bucket's median, 27th of 29.
It falls in the 1-3 tools band, which holds 16.4% of the Claude directory.
A direct call to the endpoint returned 2 tools, matching the 2 the listing publishes. Probed 2026-08-07.
twilio__retrievetwilio__searchTwilio publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally.
Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.
https://mcp.twilio.com/docs Twilio carries partner verification in the Claude directory, which 474 of 1,253 listings do (37.8%). That is a review step past self-publishing, not an Anthropic-built server.
In the publisher's words
Search Twilio’s APIs and build customer engagement experiences directly from Claude. Across more than 1,800 endpoints, Twilio MCP surfaces the exact specs and code patterns you need for channels like voice, email, and SMS/RCS, as well as user identity, customer data, contact center, and conversational AI. Get straight to the right API details and implementation guidance without loading full API docs into context or leaving your IDE.
Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.
Same company
Twilio API selection and implementation guidance
ChatGPT
Nearby
Messaging, segment, and analytics access for OneSignal
Claude · ChatGPT
Look up support tickets and contact history from chat
ChatGPT
Intercom conversations, contacts, and tickets in chat
Claude · ChatGPT
Search saved links, notes, and clips from chat
ChatGPT
Read, summarize, and update Klaxoon whiteboards
ChatGPT
Build and operate AI phone agents
Claude · ChatGPT
This is an independent catalogue entry compiled by Node8 from Twilio's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Twilio, and inclusion here is not an endorsement.
Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.