Is this an official Twilio MCP server?

No. It is Memtro's MCP server with Memtro's Twilio connector behind it: the connector reads Twilio through its API with the credentials you connect on Dashboard → Connections, and Twilio publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Twilio?

Not yet. Today every Twilio tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

Twilio MCP server

Twilio in any MCP client, through Memtro: Twilio does not publish this server. Memtro's Twilio connector reads Twilio through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only view of a Twilio account: SMS/WhatsApp messages and voice calls by date, number or status, delivery failures by error code, usage and spend by category, and the phone numbers you own.

Reads

twilio_messagesList SMS / MMS / WhatsApp messages from Twilio, newest first: when, direction, status (queued, sent, delivered, undelivered, failed, received…)…
twilio_messageOne message by SID (SM…/MM…): full body, status, direction, from/to, segments, media count…
twilio_callsVoice calls from Twilio, newest first: start/end time, direction, status (completed, busy, no-answer, failed, canceled, in-progress…)…
twilio_usageUsage and spend for a period from Twilio's usage records: count, usage and price per category (sms, sms-inbound, sms-outbound, mms, calls…
twilio_phone_numbersPhone numbers owned by the account: number, friendly name, capabilities (voice, SMS, MMS, fax)…
twilio_delivery_errorsDelivery health for a period: counts of messages by status, delivery rate for outbound messages…

Connect it

First connect Twilio on Dashboard → Connections, then add Memtro to your client once. The Twilio tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Twilio connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Which SMS to +44 7700 900123 failed last week and why?
› How many messages did we send in September and what did they cost?
› Show me the calls over 10 minutes yesterday
› What share of outbound messages were undelivered this month, by error code?
› Which of our numbers can receive MMS?

Questions

Is this an official Twilio MCP server?: No. It is Memtro's MCP server with Memtro's Twilio connector behind it: the connector reads Twilio through its API with the credentials you connect on Dashboard → Connections, and Twilio publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Twilio?: Not yet. Today every Twilio tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.