LabscoMCP early access ↗
twilio-labsMCP SERVER · OFFICIAL PROJECT

Twilio

Twilio's public API as tools, with switches so you load only the parts of it you need.

by twilio-labs ↗Telephony, SMS & Voice Agents✓ Official

LABSCO SUMMARY

Filter first, or the context bill arrives immediately.

Exposing all of Twilio at once is the documented failure mode, not an edge case — the troubleshooting section leads with context size. Decide up front which services or tags the assistant needs, pass them on the launch command, and treat the API version you are targeting as part of that decision.

What it is

Twilio's own monorepo for an MCP server covering its public API, alongside a second server that turns any OpenAPI specification into MCP tools.

What you get

  • The Twilio public API surface through npx -y @twilio-alpha/mcp, with credentials passed as one argument in the form YOUR_ACCOUNT_SID/YOUR_API_KEY:YOUR_API_SECRET
  • --services and --tags to filter which APIs are exposed — the project's own answer to hitting model context limits
  • A companion openapi-mcp-server that serves a given OpenAPI spec, pointed at spec files with --apiPath
  • Per-package documentation for each half of the monorepo

Requirements

A Twilio Account SID plus an API Key and Secret — the docs on creating those are linked from the README. Run it with npx; the published package is @twilio-alpha/mcp, inside the @twilio-alpha/mcp-monorepo repository. ISC licence. Twilio's security guidance is explicit: do not run community MCP servers alongside this one, so that untrusted tools cannot reach your Twilio account.

Setup effort

One command plus a key — npx -y @twilio-alpha/mcp <YOUR_ACCOUNT_SID>/<YOUR_API_KEY>:<YOUR_API_KEY>, then supply credentials