# Twilio MCP connector

The Twilio connector brings Twilio accounts, messages, and API keys into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can send texts, look up what was sent, and manage keys inside each person's own Twilio access.

Source: https://elaichi.ai/connectors/twilio/

## Facts

| | |
| --- | --- |
| Application | Twilio |
| Category | Application Development |
| AI tools | 19 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Twilio is connected

- Show me every text sent to +1 415 555 0199 this week.
- Text the customer that their delivery window moved to 2 to 4 pm.
- List the API keys on our production Twilio account.

## Connect Twilio in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Twilio.
2. Optionally set Share with, then press Connect.
3. Paste a Twilio API key. One person generates a token in Twilio and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Twilio tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Twilio MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Twilio MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Twilio MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Twilio MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Twilio MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Twilio to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Twilio tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Twilio through Elaichi

### Check what texts a customer received

Support. Ask for every Twilio message sent to a customer's number this week and read back the thread before replying. No digging through the Twilio console mid-ticket.

### Send a follow-up text after a call

Sales. Tell the agent to text the prospect a confirmation of the time you just agreed. The message goes out through Twilio from your own account.

### Send a shift or delivery notice

Operations. Draft a short text about a delivery window or a shift change and send it through Twilio to the right number in one ask.

### Rotate a Twilio API key safely

Engineering. Create a new Twilio key, confirm it is listed, then delete the old one, all from Cursor without opening the console.

### Set up a new Twilio subaccount

IT. Create a Twilio account for a new client or product line and update its friendly name so the billing view stays readable.

### Review what a campaign actually sent

Marketing. List the Twilio messages that went out during a campaign window and summarize who was reached and what was said.

## Elaichi vs Zapier MCP vs Composio for Twilio

All three can connect Twilio to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Twilio tools | Allow or restrict single Twilio tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Twilio call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Twilio to Claude?

In Elaichi, choose Twilio and paste the API key from your Twilio console, which is the whole sign-in step. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in Twilio and no client ID or secret to generate.

### Does Twilio work with ChatGPT and Cursor as well as Claude?

Yes. Twilio is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. Nothing is set up separately per client.

### What can an AI agent actually do with my Twilio data?

With Twilio connected, an agent can send a text, pull up the messages sent to or from a number, and update or delete a message record. It can also list your Twilio accounts and subaccounts, create a new one, and create, rotate, or remove API keys and account keys. Short concrete asks like "text this number that we are running ten minutes late" work better than long paragraphs.

### Does connecting Twilio give the AI everything in my Twilio account?

No. Every call runs inside the access of the person who signed in, so an agent can only reach the Twilio accounts, messages, and keys that person can already reach. Elaichi can narrow that access further with roles and restrictions, and it never widens it beyond what Twilio itself allows.

### Can my team share one Twilio connection?

Yes. One person connects Twilio in Elaichi and shares the connection with a team, and nobody else ever handles the Twilio API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who sent each message or changed each key.

### Can I stop an agent from deleting or changing things in Twilio?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting Twilio messages or creating Twilio keys for a role or for one person while leaving sending and reading open. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Twilio connection when someone leaves?

Offboarding a person in Elaichi ends their access to Twilio at once, across every client they used. A shared Twilio connection keeps working for everyone else on the team. If you disconnect Twilio in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.

### Does the Twilio MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Twilio is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Twilio?

Yes. Both let Claude, ChatGPT or Cursor use Twilio. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Twilio call.

### How is Elaichi different from Composio for Twilio?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Twilio: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 19 Twilio tools

Every tool below is callable through https://api.elaichi.ai/mcp once Twilio is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Twilio accounts** (List). List Twilio accounts, including the authenticated account and any subaccounts. Returns: id, sid, friendly_name, date_created, date_updated, uri, account_sid, api_version, body, date_sent, direction, error_code, error_message, from, messaging_service_sid, num_media, num_segments, price, price_unit, status, subresource_uris, to, flags.
- **Get single Twilio account by ID** (Get). Get a single Twilio account by id (the 34-character account SID, e.g. AC…). Returns: id, sid, friendly_name, date_created, date_updated, uri, account_sid, api_version, body, date_sent, direction, error_code, error_message, from, messaging_service_sid, num_media, num_segments, price, price_unit, status, subresource_uris, to. Required: id.
- **Create a Twilio account** (Create). Create a new Twilio subaccount under the authenticated parent account. Returns: id, sid, date_created, date_updated, uri, account_sid, api_version, body, date_sent, direction, from, num_media, num_segments, messaging_service_sid, status, subresource_uris, to, error_code, error_message, price, price_unit.
- **Update a Twilio account by ID** (Update). Update a Twilio account by id (the 34-character account SID, e.g. AC…). Returns: id, sid, friendly_name, date_created, date_updated, uri, account_sid, to, from, body, status, flags, api_version, date_sent, price. Required: id.
- **List all Twilio messages** (List). List the SMS and MMS messages of a Twilio account. Returns each message with sid, to, from, body, status, date_sent, and price. Required: account_sid.
- **Create a Twilio message** (Create). Send a new SMS message from a Twilio account. Returns the created message with sid, to, from, body, and status. Required: account_sid, to, body, from.
- **Get single Twilio message by ID** (Get). Get a single message by id from a Twilio account. Returns the full message record including sid, to, from, body, status, and date_created. Required: account_sid, id.
- **Update a Twilio message by ID** (Update). Update a message by SID: redact its text by setting Body to an empty string, or cancel a scheduled message by setting Status to canceled. Returns the updated message. Required: id.
- **Delete a Twilio message by ID** (Delete). Permanently delete a message by SID, including its media and feedback; it no longer appears in the Messaging logs and cannot be recovered. Returns no content (204). Required: id.
- **List all Twilio keys** (List). List the API keys of the connected Twilio account (Key resource v1), sorted by last update. Returns sid, friendly_name, date_created, date_updated and flags for each key. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Get single Twilio key by ID** (Get). Get one API key by its SID (Key resource v1). Returns sid, friendly_name, date_created, date_updated, flags. Required: id. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Create a Twilio key** (Create). Create a Standard or Restricted API key for the connected account (Key resource v1). Set KeyType to restricted and pass a Policy to limit permissions. Returns the key with its secret, which is shown only once. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Update a Twilio key by ID** (Update). Update an API key's name or, for Restricted keys, replace its permission Policy (Key resource v1). Returns the updated key. Required: id. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Delete a Twilio key by ID** (Delete). Delete (revoke) an API key by SID (Key resource v1). Requests using it stop working immediately. Returns no content. Required: id. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **List all Twilio account keys** (List). List the API keys of the connected Twilio account (Key resource v2010). Returns sid, friendly_name, date_created and date_updated for each key. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Get single Twilio account key by ID** (Get). Get one API key by its SID (Key resource v2010). Returns sid, friendly_name, date_created, date_updated. Required: id. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Create a Twilio account key** (Create). Create a Standard API key for the connected account (Key resource v2010; use the v1 create key tool for Restricted keys). Returns the key with its secret, shown only once. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Update a Twilio account key by ID** (Update). Rename an API key (Key resource v2010). Returns the updated key. Required: id. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
- **Delete a Twilio account key by ID** (Delete). Delete (revoke) an API key by SID (Key resource v2010). Requests using it stop working immediately. Returns no content. Required: id. Requires the connection's Account SID and Auth Token (or a Main API key); Standard keys cannot manage keys.
