Bird MCP connector
The Bird connector lets Claude, ChatGPT, Cursor and the Elaichi Agent send email, SMS and WhatsApp messages, set up sending domains and numbers, and check delivery, with every person signed in as themselves and every call logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Bird to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Bird once
-
Open Connections, choose Add connection, and pick Bird.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Bird. Bird's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Bird 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.
Bird 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 today. The plugin directory lives at chatgpt.com/plugins.
Bird 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.
Connect Bird 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.
Use cases
What teams do with Bird through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Send the launch email and confirm it landed
Ask for the announcement to go out by email from your Bird sending domain, then check delivery to see which messages arrived and which bounced.
-
Support
Reply to a customer on WhatsApp
Answer a waiting customer on WhatsApp straight from the chat, using the number your support team already sends from in Bird.
-
Sales
Text a prospect after the call
Send a short SMS follow-up with the next step and the meeting time, without opening Bird or copying the number by hand.
-
Operations
Send appointment and delivery reminders by SMS
Queue reminders for tomorrow's appointments or shipments and ask afterward whether every message was delivered.
-
IT
Set up a new sending domain or number
Add a sending domain or a phone number for a new region and check what your Bird workspace already has configured before you do.
-
Customer success
Check whether the renewal notice delivered
Before chasing an account, ask whether the renewal email or WhatsApp message reached them and when it was delivered.
Try asking
- “Send a WhatsApp reminder to Maria about tomorrow's appointment.”
- “Did this morning's email to the London list deliver?”
- “Which sending numbers are set up in our workspace?”
Compare
Elaichi vs Zapier MCP vs Composio for Bird
All three can connect Bird 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 Bird tools | Allow or restrict single Bird 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 Bird 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 | $15 per user per month. | 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.
See it in Elaichi
What connecting Bird gets you
5 screens from the product, each doing one job for your Bird account.
The agent
Ask about Bird messages in plain words.
Check whether an email landed or send a WhatsApp reply, from one chat.
- messages
- domains
- numbers
- channels
Ask Elaichi to work across your apps.
Send a WhatsApp reminder to Maria about tomorrow's appointment.
Did this morning's email to the London list deliver?
Which sending numbers are set up in our workspace?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Bird to every client.
Claude, ChatGPT and Cursor reach Bird through one governed endpoint, no SDK, no shared API key.
Copy the endpoint
Toolboxes
Each team gets its own Bird toolbox.
Support sends on WhatsApp and Marketing sends email, each scoped to its own work.
- Marketing
- Support
- Sales
- Operations
Shared connections
Share one Bird connection without sharing a credential.
Teammates send through a shared Bird account and still sign in as themselves.
- Marketing
- Support
- Sales EMEA
- Operations
Audit log
Every Bird message has a name behind it.
See who sent what, on which channel, and when, in one append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Every Monday, Bird delivery results become a digest.
A schedule fetches Bird messages, groups them, drafts a digest, and posts after a person approves.
Bird digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch messages
Bird
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 Michael Brennan
Approve Deny -
Post the digest
Bird
Queued
Collections and dashboards
Bird delivery numbers, refreshed without asking.
Messages sent, delivered and bounced over 14 days, by team, with no model in the math.
Bird health
Refreshed 4 minutes ago · every 15 minutes · from the messages collection
Messages
1,284 ↓ 12%
Domains
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Messages created
Last 14 days
By team
Share of activity
Marketing 34%
Support 27%
Sales EMEA 21%
Operations 18%
FAQ
Frequently asked questions
How do I connect Bird to Claude?
Connect Bird in Elaichi first: choose Bird from the catalog, and Bird opens its own sign-in screen where you approve access with your usual Bird login. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs in to Elaichi and Bird is ready to use.
Does Bird work with ChatGPT and Cursor as well as Claude?
Yes. Bird is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. Each person signs in as themselves in whichever client they use.
What can an AI agent actually do with my Bird data?
Once Bird is connected, an agent can send email, SMS and WhatsApp messages, set up sending domains and phone numbers, and check whether a message was delivered or what your Bird workspace has set up. Exactly what is available depends on what your own Bird account has configured. Short, concrete asks work best, such as asking it to text a customer that her order shipped rather than writing a long paragraph.
Does connecting Bird give the AI my whole Bird workspace?
No. Everything runs inside the access of the person who signed in to Bird, so the agent can only reach the channels, domains and numbers that person can already use. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Bird itself allows.
Can I stop an agent from sending or changing things in Bird?
Yes. Restrictions in Elaichi apply per action, so you can allow checking delivery while blocking sending, or allow sending while blocking changes to domains and numbers. A restricted Bird action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Bird connection when someone leaves?
Offboarding a person in Elaichi ends their access to Bird at once, in every client they used. A Bird connection shared with the team keeps working for everyone else. If you want Bird gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client together.
Does the Bird MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Bird 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, 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 Bird?
Yes. Both let Claude, ChatGPT or Cursor use Bird. 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 Bird call.
How is Elaichi different from Composio for Bird?
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 Bird: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Bird in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.