Bird AI Marketplace
Skills for driving the Bird platform from your coding agent. Your agent operates Bird through the bird CLI; the bird plugin in this marketplace installs the skills that teach it Bird's workflows, and on clients that read the plugin's MCP declaration it wires up Bird's hosted MCP server too.
Quick start
Every client starts the same way: install the CLI and sign in.
curl -fsSL https://cli.bird.com/install.sh | sh
bird auth login
On macOS or Linux you can also install with Homebrew: brew install messagebird/tap/bird.
Then jump to your client below. The fastest path is to paste the setup prompt and let your agent do the rest; a manual path is under each one.
No Bird account yet?
bird auth login signs in to an account you already have. An agent with no account can create one from the terminal — no browser, no password. Three commands take you from nothing to a stored credential:
bird auth signup you@example.com
bird auth verify-email you@example.com --code 123456
bird auth create-org "Acme" --workspace-name "Production" --region us1 --onboarding-ticket obt_…
bird auth status
The code arrives by email, so it comes from outside the CLI — read it from the inbox and pass it to step 2. Signup and verification are region-agnostic; you pick the region once, at create-org, so there is no host or environment variable to set. Every step is self-describing: append --help for the flags, --example for a ready-to-edit request body, or --response-schema for what it returns — none of them need a credential, so an agent can plan the whole chain before running it. Full walkthrough: Self-serve signup.
Any Agent Plugins client
The plugin ships a root plugin.json and mcp.json following Agent Plugins, the portable plugin format. A client that implements the specification loads it from this repository as it is: the skills and the hosted MCP server, in one install. Point the client at github.com/messagebird/bird-ai and install bird from plugins/bird.
For a client with its own plugin format, or none, find it below.
Claude Code
Paste this prompt into Claude Code and it installs the CLI, signs you in, installs the skills, and sends a test email:
Bird is a communications platform you can operate end to end: email, SMS, WhatsApp, and voice through one API and one login. Set Bird up for me, end to end.
1. Install the Bird CLI: run `curl -fsSL https://cli.bird.com/install.sh | sh`.
2. Sign me in: run `bird auth login` and open the browser link for me.
3. Install Bird's skills so you know the workflows: run `claude plugin marketplace add messagebird/bird-ai`, then `claude plugin install bird@bird-ai`.
4. Confirm who I am: run `bird whoami`, which prints the email of the account you're acting as.
5. Send me a test email so I see it land in my own inbox: use my address from `bird whoami` as the recipient, send from onboarding@messagebird.dev, then confirm delivery with `bird email get`. Subject: "Your Bird account is ready". Body: "You're set up and ready to send. This email is the proof. Cheers, The Bird team".
Then let's discuss next steps, given what Bird can do.
Or install the plugin manually:
claude plugin marketplace add messagebird/bird-ai
claude plugin install bird@bird-ai
MCP server: installing the plugin registers Bird's hosted server at https://mcp.bird.com, so there is nothing to configure. You do have to sign in once, because the server is OAuth-gated: run /mcp, select bird, press Enter, and choose Authenticate. Your browser opens Bird's consent screen; approve it and the tools work. Until then claude mcp list reports bird as ! Needs authentication and every tool call fails. For a headless run (claude -p) there is no /mcp panel, so authenticate first with claude mcp login bird.
Cursor
Paste this prompt into Cursor:
Bird is a communications platform you can operate end to end: email, SMS, WhatsApp, and voice through one API and one login. Set Bird up for me, end to end.
1. Install the Bird CLI: run `curl -fsSL https://cli.bird.com/install.sh | sh`.
2. Sign me in: run `bird auth login` and open the browser link for me.
3. Give yourself Bird's skills (Cursor installs plugins through its UI, so set them up by file instead): fetch the skills from https://github.com/messagebird/bird-ai and write them into `.cursor/rules/` as `.mdc` files.
4. Confirm who I am: run `bird whoami`, which prints the email of the account you're acting as.
5. Send me a test email so I see it land in my own inbox: use my address from `bird whoami` as the recipient, send from onboarding@messagebird.dev, then confirm delivery with `bird email get`. Subject: "Your Bird account is ready". Body: "You're set up and ready to send. This email is the proof. Cheers, The Bird team".
Then let's discuss next steps, given what Bird can do.
To set the skills up by hand, add the messagebird/bird-ai marketplace under Settings → Plugins, or write the skills from this repo into .cursor/rules/ as .mdc files yourself.
MCP server: add the hosted server once in ~/.cursor/mcp.json:
{
"mcpServers": {
"bird": { "url": "https://mcp.bird.com" }
}
}
Then sign in: open Cursor Settings → Tools & Integrations, and under MCP Tools click Needs login next to bird. Approve Bird's consent screen in the browser and return to Cursor. The tools fail until you do.
Codex
Paste this prompt into Codex:
Bird is a communications platform you can operate end to end: email, SMS, WhatsApp, and voice through one API and one login. Set Bird up for me, end to end.
1. Install the Bird CLI: run `curl -fsSL https://cli.bird.com/install.sh | sh`.
2. Sign me in: run `bird auth login` and open the browser link for me.
3. Install Bird's skills so you know the workflows: run `codex plugin marketplace add messagebird/bird-ai`, then `codex plugin add bird@bird-ai` (check `codex plugin --help` if the exact form differs).
4. Confirm who I am: run `bird whoami`, which prints the email of the account you're acting as.
5. Send me a test email so I see it land in my own inbox: use my address from `bird whoami` as the recipient, send from onboarding@messagebird.dev, then confirm delivery with `bird email get`. Subject: "Your Bird account is ready". Body: "You're set up and ready to send. This email is the proof. Cheers, The Bird team".
Then let's discuss next steps, given what Bird can do.
Or install the plugin manually:
codex plugin marketplace add messagebird/bird-ai
codex plugin add bird@bird-ai
MCP server: add the hosted server once in ~/.codex/config.toml:
[mcp_servers.bird]
url = "https://mcp.bird.com"
Then sign in, which opens your browser for Bird's consent screen:
GitHub Copilot
Paste this prompt into Copilot:
Bird is a communications platform you can operate end to end: email, SMS, WhatsApp, and voice through one API and one login. Set Bird up for me, end to end.
1. Install the Bird CLI: run `curl -fsSL https://cli.bird.com/install.sh | sh`.
2. Sign me in: run `bird auth login` and open the browser link for me.
3. Install Bird's skills so you know the workflows: run `copilot plugin marketplace add messagebird/bird-ai`, then `copilot plugin install bird@bird-ai`.
4. Confirm who I am: run `bird whoami`, which prints the email of the account you're acting as.
5. Send me a test email so I see it land in my own inbox: use my address from `bird whoami` as the recipient, send from onboarding@messagebird.dev, then confirm delivery with `bird email get`. Subject: "Your Bird account is ready". Body: "You're set up and ready to send. This email is the proof. Cheers, The Bird team".
Then let's discuss next steps, given what Bird can do.
Or install the plugin manually:
copilot plugin marketplace add messagebird/bird-ai
copilot plugin install bird@bird-ai
MCP server: add the hosted server once in .vscode/mcp.json:
{
"servers": {
"bird": { "type": "http", "url": "https://mcp.bird.com" }
}
}
VS Code asks you to trust the server the first time it starts, then runs the sign-in itself: approve Bird's consent screen in the browser window it opens. If no window appears, start bird from the MCP: List Servers command. Your grant is listed under the Accounts menu → Manage Trusted MCP Servers, which is also where you revoke it.
Factory Droid
Paste this prompt into Droid:
Bird is a communications platform you can operate end to end: email, SMS, WhatsApp, and voice through one API and one login. Set Bird up for me, end to end.
1. Install the Bird CLI: run `curl -fsSL https://cli.bird.com/install.sh | sh`.
2. Sign me in: run `bird auth login` and open the browser link for me.
3. Install Bird's skills so you know the workflows: Droid loads skills from `.factory/skills/`, so clone https://github.com/messagebird/bird-ai and copy every directory in `plugins/bird/skills/` into `.factory/skills/`.
4. Confirm who I am: run `bird whoami`, which prints the email of the account you're acting as.
5. Send me a test email so I see it land in my own inbox: use my address from `bird whoami` as the recipient, send from onboarding@messagebird.dev, then confirm delivery with `bird email get`. Subject: "Your Bird account is ready". Body: "You're set up and ready to send. This email is the proof. Cheers, The Bird team".
Then let's discuss next steps, given what Bird can do.
To set the skills up by hand:
git clone https://github.com/messagebird/bird-ai
cp -r bird-ai/plugins/bird/skills/. .factory/skills/
MCP server: add the hosted server once:
droid mcp add bird https://mcp.bird.com --type http
Then run /mcp inside droid and complete the browser sign-in from the server manager.
OpenCode
Paste this prompt into OpenCode:
Bird is a communications platform you can operate end to end: email, SMS, WhatsApp, and voice through one API and one login. Set Bird up for me, end to end.
1. Install the Bird CLI: run `curl -fsSL https://cli.bird.com/install.sh | sh`.
2. Sign me in: run `bird auth login` and open the browser link for me.
3. Install Bird's OpenCode plugin so you know the workflows: run `opencode plugin github:messagebird/bird-ai --global`, then tell me to restart OpenCode and run `opencode mcp auth bird`.
4. Confirm who I am: run `bird whoami`, which prints the email of the account you're acting as.
5. Send me a test email so I see it land in my own inbox: use my address from `bird whoami` as the recipient, send from onboarding@messagebird.dev, then confirm delivery with `bird email get`. Subject: "Your Bird account is ready". Body: "You're set up and ready to send. This email is the proof. Cheers, The Bird team".
Then let's discuss next steps, given what Bird can do.
Or install the plugin by hand:
opencode plugin github:messagebird/bird-ai --global
opencode mcp auth bird
The plugin adds Bird's skills and the hosted MCP server to your OpenCode config. By default OpenCode adds every MCP tool to the model's context, so the plugin connects to https://mcp.bird.com/dynamic, which offers two tools: search finds the Bird tool for a task and execute runs it. With OpenCode's experimental code mode on (OPENCODE_EXPERIMENTAL_CODE_MODE=1, or OPENCODE_EXPERIMENTAL=1), OpenCode keeps MCP tools behind its own search, so the plugin connects to the full catalog at https://mcp.bird.com instead.
By default the plugin makes OpenCode ask before each call that can change your workspace: before bird_execute on /dynamic, and before every Bird tool in code mode. Your own opencode.json takes precedence: a bird_* rule you set, a single permission value for every tool, or a bird server you configured replaces the plugin's.
What's in the bird plugin
bird-cli: operate the Bird API from the terminal. One reference per CLI command group, covering sending and inspecting messages on every channel Bird runs, the setup each channel needs before it can send, one-time-passcode verification, recipient lookup, contacts and audiences, messaging preferences, Realtime provisioning, webhooks, API keys, support tickets, and documentation search.email-audit: grade a domain's live DMARC, SPF, DKIM, BIMI, and MX records and read the findings back as a prioritized fix list. DNS-only, so it needs no sign-in.- Bird MCP server: the hosted server at
https://mcp.bird.com, so your agent can call Bird directly with a browser sign-in and no API key. Registered for you on Claude Code, OpenCode and any Agent Plugins host; a one-time config elsewhere (above). Every client needs the one-time browser sign-in described in its section: the server is OAuth-gated, and a client that has the URL but no grant lists the tools and fails every call.
License
MIT.