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.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me every text sent to +1 415 555 0199 this week.
Working in Twilio with Elaichi
-
List all Twilio accounts
-
Get single Twilio account by ID
-
List all Twilio messages
How to connect Twilio to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Twilio MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Twilio MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Twilio through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Twilio is logged.
-
Support
Check what texts a customer received
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.
-
Sales
Send a follow-up text after a call
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.
-
Operations
Send a shift or delivery notice
Draft a short text about a delivery window or a shift change and send it through Twilio to the right number in one ask.
-
Engineering
Rotate a Twilio API key safely
Create a new Twilio key, confirm it is listed, then delete the old one, all from Cursor without opening the console.
-
IT
Set up a new Twilio subaccount
Create a Twilio account for a new client or product line and update its friendly name so the billing view stays readable.
-
Marketing
Review what a campaign actually sent
List the Twilio messages that went out during a campaign window and summarize who was reached and what was said.
Try asking
- “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.”
What connecting Twilio gets you
6 screens from Elaichi, each doing one job for your Twilio account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Twilio messages in plain language.
Three starter prompts pull live Twilio messages, accounts and keys into a plain answer.
Copy the endpoint
AI apps
One Twilio endpoint for every MCP client.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Tool catalog
19 Twilio tools, no custom code required.
Accounts, messages, keys and account keys, each with its resources and methods listed.
Toolboxes
Each team gets its own Twilio toolbox.
Support, Sales and Engineering each work from a toolbox scoped to their own jobs.
Shared connections
Teammates send Twilio messages without seeing a key.
One person connects Twilio, shares it with teams, and the API key stays private.
Audit log
Every Twilio message traces back to a person.
When, who, what happened, type and resource, recorded for every call in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Twilio digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Twilio
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Twilio
Queued
Workflows
A schedule sends the Twilio digest, you approve.
Messages are fetched, grouped and drafted into a digest, approved by a person, then posted back.
Twilio health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Messages
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Support 34%
Sales US 27%
Operations 21%
Engineering 18%
Collections and dashboards
Twilio message volume, computed without a model.
Four metrics, 14 days of messages created and a team breakdown, refreshed on a schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Twilio tools for your AI agents
19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Twilio, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Twilio in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot