# 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.

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

## Facts

| | |
| --- | --- |
| Application | Bird |
| Category | Marketing Automation |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Bird builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@bird.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, 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 Bird is connected

- 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?

## Connect Bird in Elaichi

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

1. Open Connections, choose Add connection, and pick Bird.
2. Optionally set Share with, then press Connect.
3. Approve it in Bird. Bird's own window opens. Whoever approves it decides what this connection can reach.

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

## Bird 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.

## Bird 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 today. The plugin directory lives at chatgpt.com/plugins.

## Bird 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.

## Connect Bird 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

Only Read is granted by default, which is not enough to call a Bird tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Bird through Elaichi

### Send the launch email and confirm it landed

Marketing. 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.

### Reply to a customer on WhatsApp

Support. Answer a waiting customer on WhatsApp straight from the chat, using the number your support team already sends from in Bird.

### Text a prospect after the call

Sales. Send a short SMS follow-up with the next step and the meeting time, without opening Bird or copying the number by hand.

### Send appointment and delivery reminders by SMS

Operations. Queue reminders for tomorrow's appointments or shipments and ask afterward whether every message was delivered.

### Set up a new sending domain or number

IT. Add a sending domain or a phone number for a new region and check what your Bird workspace already has configured before you do.

### Check whether the renewal notice delivered

Customer success. Before chasing an account, ask whether the renewal email or WhatsApp message reached them and when it was delivered.

## 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. Endpoint: 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](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 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 my team share one Bird connection?

Yes. One person connects Bird in Elaichi and shares it with a team, and nobody else ever handles a Bird credential. Each teammate still signs in to Elaichi as themselves, so every message sent through the shared Bird connection is logged under the name of the person who asked for it.

### 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.