Skip to main content
Glama
pipeworx-io

mcp-twilio

by pipeworx-io

mcp-twilio

Twilio MCP Pack — send SMS, list messages, make calls via Twilio REST API.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool

Description

twilio_send_sms

Send an SMS message via Twilio. Returns the message SID and status.

twilio_list_messages

List recent SMS/MMS messages from your Twilio account. Supports filtering by to/from number and pagination.

twilio_get_message

Get details of a specific Twilio message by its SID.

twilio_list_calls

List recent phone calls from your Twilio account. Returns call SID, status, duration, and direction.

twilio_make_call

Initiate a phone call via Twilio. Requires a TwiML URL or application SID to control call behavior.

Related MCP server: Twilio MCP Server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "twilio": {
      "url": "https://gateway.pipeworx.io/twilio/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/twilio/mcp returns the tools in the table above plus the shared Pipeworx meta-toolsask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Twilio data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables AI assistants to interact with all Twilio APIs through the Model Context Protocol. Supports SMS, voice, messaging, and other Twilio services with secure authentication and configurable API filtering.
    -
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables communication through Twilio's API including sending SMS/WhatsApp messages, making phone calls, and managing phone numbers and account settings. Provides comprehensive messaging and voice capabilities with proper authentication and rate limiting.
    -
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables interaction with Twilio API services including messaging, voice, and Studio flows through Docker deployment. Supports both API Key and Auth Token authentication for managing calls, messages, phone numbers, and automation workflows.
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI-powered SMS messaging through Twilio with automatic conversation threading, message status tracking, and webhook support for receiving inbound messages.
    45 npm
    1
    MIT