Skip to main content
mcpSource-backed

Twilio MCP Server for Claude

Connect Claude to Twilio's hosted MCP server for read-only search and retrieval across public Twilio API specifications, Twilio Docs, SendGrid Docs, Segment Docs, and support articles.

by Twilio · submitted by MkDev11·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://www.twilio.com/docs/ai/mcp, https://github.com/twilio-labs/mcp
Safety notes
Twilio describes the current hosted MCP server as a Public Beta. Treat tool behavior, indexed coverage, and connection instructions as changeable until Twilio declares general availability., The current hosted server is read-only and exposes search/retrieve tools for public API specifications and documentation. It does not execute Twilio API calls or send messages on your behalf., Do not confuse documentation retrieval with production readiness. Review generated Messaging, Voice, Verify, SendGrid, Segment, or other Twilio code against the canonical docs, product limits, regulatory requirements, and your normal approval process before running it., Future Twilio MCP releases may add OAuth-authenticated execute-ready tools. Re-review permissions, approval prompts, audit logging, and data handling before enabling any tool that can call live APIs., Keep MCP client approval settings enabled for prompts that might transform retrieved API schemas into runnable code, migration scripts, webhook handlers, message sends, or account-management actions.
Privacy notes
The hosted endpoint can receive your natural-language search queries, requested API IDs, product interests, integration plans, and troubleshooting topics through the MCP client., Returned documentation can enter the model conversation alongside your prompt, code, route names, environment names, webhook examples, or product decisions., Do not paste Twilio Account SIDs, Auth Tokens, API keys, SendGrid keys, Segment write keys, phone numbers, customer identifiers, message bodies, call recordings, transcripts, or production webhook payloads into prompts while using the public docs server., Use synthetic examples when asking Claude to draft Messaging, Voice, Verify, SendGrid, Segment, or support workflows from retrieved docs.
Author
Twilio
Submitted by
MkDev11
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

5 minutes

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup. Have accounts and credentials ready first.

0/4 ready
Account & credentials1Install & runtime1Network & hosting25 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.

4 areas
  • SafetyGeneralTwilio describes the current hosted MCP server as a Public Beta. Treat tool behavior, indexed coverage, and connection instructions as changeable until Twilio declares general availability.
  • SafetyNetwork accessThe current hosted server is read-only and exposes search/retrieve tools for public API specifications and documentation. It does not execute Twilio API calls or send messages on your behalf.
  • SafetyExecution & processesDo not confuse documentation retrieval with production readiness. Review generated Messaging, Voice, Verify, SendGrid, Segment, or other Twilio code against the canonical docs, product limits, regulatory requirements, and your normal approval process before running it.
  • SafetyCredentials & tokensFuture Twilio MCP releases may add OAuth-authenticated execute-ready tools. Re-review permissions, approval prompts, audit logging, and data handling before enabling any tool that can call live APIs.
  • SafetyNetwork accessKeep MCP client approval settings enabled for prompts that might transform retrieved API schemas into runnable code, migration scripts, webhook handlers, message sends, or account-management actions.
  • PrivacyNetwork accessThe hosted endpoint can receive your natural-language search queries, requested API IDs, product interests, integration plans, and troubleshooting topics through the MCP client.
  • PrivacyNetwork accessReturned documentation can enter the model conversation alongside your prompt, code, route names, environment names, webhook examples, or product decisions.
  • PrivacyCredentials & tokensDo not paste Twilio Account SIDs, Auth Tokens, API keys, SendGrid keys, Segment write keys, phone numbers, customer identifiers, message bodies, call recordings, transcripts, or production webhook payloads into prompts while using the public docs server.
  • PrivacyGeneralUse synthetic examples when asking Claude to draft Messaging, Voice, Verify, SendGrid, Segment, or support workflows from retrieved docs.

Safety notes

  • Twilio describes the current hosted MCP server as a Public Beta. Treat tool behavior, indexed coverage, and connection instructions as changeable until Twilio declares general availability.
  • The current hosted server is read-only and exposes search/retrieve tools for public API specifications and documentation. It does not execute Twilio API calls or send messages on your behalf.
  • Do not confuse documentation retrieval with production readiness. Review generated Messaging, Voice, Verify, SendGrid, Segment, or other Twilio code against the canonical docs, product limits, regulatory requirements, and your normal approval process before running it.
  • Future Twilio MCP releases may add OAuth-authenticated execute-ready tools. Re-review permissions, approval prompts, audit logging, and data handling before enabling any tool that can call live APIs.
  • Keep MCP client approval settings enabled for prompts that might transform retrieved API schemas into runnable code, migration scripts, webhook handlers, message sends, or account-management actions.

Privacy notes

  • The hosted endpoint can receive your natural-language search queries, requested API IDs, product interests, integration plans, and troubleshooting topics through the MCP client.
  • Returned documentation can enter the model conversation alongside your prompt, code, route names, environment names, webhook examples, or product decisions.
  • Do not paste Twilio Account SIDs, Auth Tokens, API keys, SendGrid keys, Segment write keys, phone numbers, customer identifiers, message bodies, call recordings, transcripts, or production webhook payloads into prompts while using the public docs server.
  • Use synthetic examples when asking Claude to draft Messaging, Voice, Verify, SendGrid, Segment, or support workflows from retrieved docs.

Prerequisites

  • MCP-capable client with remote HTTP transport support, such as Claude Code, Claude Desktop connector support, Cursor, OpenCode, Codex, or another compatible client
  • Network access to `https://mcp.twilio.com/docs`
  • Agreement that the current hosted Twilio MCP server should receive the Twilio, SendGrid, or Segment documentation questions your team asks through the MCP client
  • Separate Twilio, SendGrid, or Segment account credentials only when you later write or run application code outside this read-only MCP server

Schema details

Install type
cli
Troubleshooting
Yes
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Full copyable content
{
  "mcpServers": {
    "twilio-docs": {
      "transport": "http",
      "url": "https://mcp.twilio.com/docs"
    }
  }
}

About this resource

Content

Twilio MCP Server is Twilio's hosted Model Context Protocol server for API documentation discovery. It connects Claude and other MCP-capable clients to a read-only search and retrieval workflow over public Twilio OpenAPI specifications, Twilio Docs, Twilio Support articles, SendGrid Docs, SendGrid Support articles, and Segment Docs.

The safest way to think about this server is "current Twilio documentation in a tool." It helps Claude find the relevant API operation or article, then retrieve focused parameter and response schema details. It should not be treated as a live Twilio account operator because the documented hosted server does not execute API calls or require Twilio credentials.

Features

  • Hosted HTTP MCP endpoint at https://mcp.twilio.com/docs.
  • Official Twilio documentation page for setup, capabilities, limitations, and supported clients.
  • Public source repository in twilio-labs/mcp.
  • Read-only access to public Twilio API specifications, Twilio Docs, Twilio Support articles, SendGrid Docs, SendGrid Support articles, and Segment Docs.
  • Two-step workflow that searches first, then retrieves full details only for selected API or documentation results.
  • Claude Code CLI setup with remote HTTP transport.
  • Connector or marketplace setup paths documented for Claude, Cursor, OpenCode, Codex, and Figma Make.
  • No Twilio account, API key, or OAuth flow required for the current hosted docs endpoint.
  • Public Beta status disclosed by Twilio.

Tools

twilio__search

Use this first. It accepts a natural-language query and returns ranked matching API operations, documentation articles, and result IDs.

twilio__retrieve

Use this after search. It accepts one or more IDs from search results and returns focused parameter schemas, response schemas, and documentation details.

This search-then-retrieve flow helps keep model context smaller than pasting a large OpenAPI specification or documentation page into chat.

Installation

Claude Code

Add the hosted Twilio MCP endpoint:

claude mcp add --transport http twilio-docs https://mcp.twilio.com/docs

Then verify the server is configured:

claude mcp list

Ask a documentation question that should use the MCP server:

Use the Twilio MCP server to find the current API parameters for sending an SMS, then retrieve the endpoint schema before drafting code.

MCP Client Config

Use remote HTTP transport in clients that support it:

{
  "mcpServers": {
    "twilio-docs": {
      "transport": "http",
      "url": "https://mcp.twilio.com/docs"
    }
  }
}

Use Cases

  • Look up current Twilio Messaging, Voice, Verify, Conversations, Video, Flex, Serverless, Studio, Sync, TaskRouter, Events, Monitor, or Lookup API details.
  • Retrieve exact request parameters and response schemas before writing Twilio integration code.
  • Ask Claude to compare newer Twilio products or API versions that may not be well represented in model training data.
  • Search SendGrid or Segment documentation from the same MCP workflow when an integration crosses Twilio product boundaries.
  • Draft code or runbook notes from current docs while keeping API credentials out of the MCP server.
  • Review generated Twilio integration code against focused endpoint schemas instead of a broad documentation summary.

Safety Checklist

  • Confirm the MCP client points to https://mcp.twilio.com/docs.
  • Treat the server as read-only documentation retrieval, not live account access.
  • Keep Twilio, SendGrid, and Segment credentials out of prompts and MCP config.
  • Review generated code before running anything that sends messages, places calls, verifies users, modifies webhooks, or touches production contacts.
  • Check product-specific compliance, consent, sender registration, rate limits, and regional requirements before using generated Messaging or Voice code.
  • Revisit the setup if Twilio adds OAuth-authenticated execute tools in a future release.

Troubleshooting

The MCP server is not listed

Run claude mcp list and confirm that the twilio-docs server uses HTTP transport with https://mcp.twilio.com/docs.

Results are too broad

Start with a product name and action, such as "Twilio Verify create verification" or "SendGrid send email dynamic template", then retrieve only the specific result IDs you need.

The answer lacks endpoint details

Ask Claude to run twilio__retrieve on the best search result before drafting code. Search results are summaries; retrieve returns the focused details.

You need to call a live Twilio API

Use the retrieved docs to write or review code, then run that code through your normal local or CI workflow with approved credentials. Do not paste production credentials into the MCP conversation.

Duplicate And History Check

Checked current content/mcp/, collections, skills, commands, tools, hooks, open PRs, closed PRs, and issue history for Twilio, twilio-labs/mcp, mcp.twilio.com, SendGrid MCP, Segment MCP, and Twilio API docs. Existing content only mentions Twilio incidentally as a notification provider example. No dedicated Twilio MCP server entry, duplicate source URL, or prior rejected Twilio MCP PR was found.

Sources

Source citations

Add this badge to your README

Show that Twilio MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/twilio-mcp-server.svg)](https://heyclau.de/entry/mcp/twilio-mcp-server)

How it compares

Twilio MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

Connect Claude to Twilio's hosted MCP server for read-only search and retrieval across public Twilio API specifications, Twilio Docs, SendGrid Docs, Segment Docs, and support articles.

Open dossier

Explore OpenAPI and Swagger specifications from Claude through a hosted MCP server that returns API overviews and per-operation schema details.

Open dossier

Official AWS Labs MCP server that lets AI assistants read, search, and get recommendations across AWS documentation, returning pages as clean markdown with no AWS account or credentials required.

Open dossier

Official Brave Search MCP server for giving Claude web, local, place, image, video, news, LLM context, and summarizer search tools backed by the Brave Search API.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersMkDev11oktofeesh1jaso0n0818oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandAWS Labs logoAWS LabsBrave Search logoBrave Search
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorTwilioJan WilmakeAWS LabsBrave Software
Added2026-06-052026-06-032026-06-202026-06-06
Platforms
Harness
Source repo
Safety notesTwilio describes the current hosted MCP server as a Public Beta. Treat tool behavior, indexed coverage, and connection instructions as changeable until Twilio declares general availability. The current hosted server is read-only and exposes search/retrieve tools for public API specifications and documentation. It does not execute Twilio API calls or send messages on your behalf. Do not confuse documentation retrieval with production readiness. Review generated Messaging, Voice, Verify, SendGrid, Segment, or other Twilio code against the canonical docs, product limits, regulatory requirements, and your normal approval process before running it. Future Twilio MCP releases may add OAuth-authenticated execute-ready tools. Re-review permissions, approval prompts, audit logging, and data handling before enabling any tool that can call live APIs. Keep MCP client approval settings enabled for prompts that might transform retrieved API schemas into runnable code, migration scripts, webhook handlers, message sends, or account-management actions.The current server exposes OpenAPI exploration tools, not a general API execution tool. It returns overviews and operation details from specs rather than calling the target API endpoints. Treat OpenAPI specs as potentially sensitive. Internal paths, request schemas, server URLs, security schemes, operation names, and business domain language can reveal system design. Do not point the hosted endpoint at private or pre-release OpenAPI specs unless the spec is approved for third-party processing. Self-host the Worker for private API contracts. Review operation details before asking Claude to write integration code. OpenAPI descriptions and examples are model context and can contain stale, incomplete, or user-controlled text. Swagger 2.0 specs may be converted through the Swagger converter service before the server returns operation details. Use OpenAPI 3.x specs directly when you want fewer intermediaries.The server is read-only: it fetches and searches public AWS documentation and does not call AWS service APIs or modify any AWS resources. It requires no AWS account or credentials; do not add AWS access keys for this server. `AWS_DOCUMENTATION_PARTITION` selects the docs partition (`aws` global, or `aws-cn` for China); the available tools differ between partitions.Brave Search MCP uses BRAVE_API_KEY from the MCP client environment or command-line options. The server defaults to stdio transport in version 2.x and can also run an HTTP transport when explicitly configured. Tools can send web, news, image, video, local, place, and LLM-context queries to the Brave Search API. Local and place tools may use location strings, coordinates, postal codes, or optional location headers. Summarizer workflows depend on summary keys returned by web search and should be checked against cited source URLs. API usage may be metered or plan-limited, especially for Pro-only local search capabilities and extra snippets.
Privacy notesThe hosted endpoint can receive your natural-language search queries, requested API IDs, product interests, integration plans, and troubleshooting topics through the MCP client. Returned documentation can enter the model conversation alongside your prompt, code, route names, environment names, webhook examples, or product decisions. Do not paste Twilio Account SIDs, Auth Tokens, API keys, SendGrid keys, Segment write keys, phone numbers, customer identifiers, message bodies, call recordings, transcripts, or production webhook payloads into prompts while using the public docs server. Use synthetic examples when asking Claude to draft Messaging, Voice, Verify, SendGrid, Segment, or support workflows from retrieved docs.The hosted MCP endpoint receives the API identifier or raw spec URL you ask Claude to inspect, plus the operationId or route requested through `getApiOperation`. The service fetches OpenAPI documents via OpenAPI Search/OAPIS redirects or from the raw spec URL you provide. Returned overviews and operation details can include endpoint paths, parameters, request bodies, response schemas, server URLs, security scheme names, examples, and descriptions in the model conversation. The public setup path does not require API credentials and should not be used to send API keys, Bearer tokens, cookies, or internal auth headers. The repository is deployed as a Cloudflare Worker. Hosted-service logging, retention, and operational access are controlled by the service operator. Self-host when you need your own logging and retention boundary.Documentation URLs and search terms you ask about are sent to the official AWS documentation search/read endpoints to retrieve content. The server fetches public documentation pages over HTTPS and returns them as markdown; no private account data is read.Search queries, location parameters, result filters, language settings, freshness windows, and optional headers may reveal user intent, location, research topics, or sensitive business context. BRAVE_API_KEY should stay out of prompts, issues, logs, screenshots, and committed files. Returned snippets, summaries, search results, local-business metadata, images, videos, and news items can include third-party copyrighted or sensitive content. HTTP transport should be bound and exposed carefully so the API key and search tools are not reachable by untrusted clients.
Prerequisites
  • MCP-capable client with remote HTTP transport support, such as Claude Code, Claude Desktop connector support, Cursor, OpenCode, Codex, or another compatible client
  • Network access to `https://mcp.twilio.com/docs`
  • Agreement that the current hosted Twilio MCP server should receive the Twilio, SendGrid, or Segment documentation questions your team asks through the MCP client
  • Separate Twilio, SendGrid, or Segment account credentials only when you later write or run application code outside this read-only MCP server
  • MCP-capable client with remote HTTP transport support, such as Claude Code or another modern MCP client
  • Network access to `https://openapi-mcp.openapisearch.com/mcp`
  • OpenAPI Search identifier, OAPIS identifier, or raw OpenAPI spec URL for the API you want Claude to inspect
  • Understanding that the hosted service fetches and processes the OpenAPI spec instead of running locally in your project
  • Python 3.10 or newer installed.
  • `uv` / `uvx` installed (Astral) to run the published Python package.
  • An MCP client that supports stdio servers (Claude Code, Claude Desktop, Cursor, Kiro, or VS Code).
  • Outbound HTTPS access so the server can fetch and search AWS documentation.
  • Brave Search API account and API key.
  • Node.js and npm available in the MCP client runtime.
  • API plan review for web, local, extra snippets, summarizer, and LLM context usage.
  • Tool whitelist or blacklist if the client should expose only selected search tools.
Install
claude mcp add --transport http twilio-docs https://mcp.twilio.com/docs
claude mcp add --transport http openapi https://openapi-mcp.openapisearch.com/mcp
uvx awslabs.aws-documentation-mcp-server@latest
npx -y @brave/brave-search-mcp-server --transport stdio
Config
{
  "mcpServers": {
    "twilio-docs": {
      "url": "https://mcp.twilio.com/docs",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "openapi": {
      "url": "https://openapi-mcp.openapisearch.com/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "awslabs.aws-documentation-mcp-server": {
      "command": "uvx",
      "args": ["awslabs.aws-documentation-mcp-server@latest"],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_DOCUMENTATION_PARTITION": "aws"
      },
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "brave-search": {
      "command": "npx",
      "args": ["-y", "@brave/brave-search-mcp-server", "--transport", "stdio"],
      "env": {
        "BRAVE_API_KEY": "<your-brave-search-api-key>"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.