Bird

What Bird MCP server does

Bird MCP server gives coding agents access to Bird's communications platform. The documented workflows cover sending email, SMS, WhatsApp messages, and voice communications through Bird's infrastructure. The repository also provides agent skills that describe Bird workflows and a plugin declaration for clients that support the Agent Plugins format.

The MCP connection is hosted by Bird at https://mcp.bird.com, so the repository does not require you to run a local MCP process. The Bird MCP server is suited to agents that need to perform communications tasks as part of development or operational workflows.

How it works

The repository combines two pieces: the Bird CLI and a hosted MCP server. The CLI handles account access and related Bird operations, while the MCP endpoint exposes Bird capabilities to supported clients. The documented setup begins by installing the CLI and running bird auth login; authentication opens a browser and does not require an API key.

MCP access is OAuth-gated. After adding the hosted endpoint to a client, authenticate through that client's MCP controls and approve Bird's consent screen in a browser. Calls remain unavailable until authentication is complete. Clients with no plugin support can still configure the hosted endpoint directly, while plugin-capable clients can install the repository's skills and MCP declaration together.

Setup and configuration

Install the CLI with Bird's shell installer or Homebrew on macOS and Linux:

• curl -fsSL https://cli.bird.com/install.sh | sh
• brew install messagebird/tap/bird

Then sign in with bird auth login. New users can create an account from the terminal by signing up with an email address, verifying the emailed six-digit code, and creating an organization and workspace. The organization command accepts a region of us1 or eu1 and stores the resulting credential.

For direct MCP configuration, use the hosted URL. Cursor uses ~/.cursor/mcp.json, Codex uses ~/.codex/config.toml, and VS Code uses .vscode/mcp.json. Claude Code can register the server through the Bird plugin. Authentication commands include claude mcp login bird and codex mcp login bird; Cursor and VS Code provide sign-in controls in their interfaces.

Tools and capabilities

Documented communication areas include:

• Sending email and checking delivery with Bird workflows
• Sending SMS messages
• Sending WhatsApp messages
• Sending voice communications
• Managing Bird access and identity through the CLI
• Installing Bird skills for supported agent clients

The repository's examples use a test email sent through Bird and verify it with bird email get. Exact MCP tool names and schemas are not listed in the provided material, so applications should inspect the connected client's available tools rather than assume a fixed tool inventory.

Limitations and notes

A Bird account and successful OAuth or CLI sign-in are required before communication tools can be used. The hosted MCP server is not usable anonymously. Email verification for self-serve signup happens outside the CLI because the code is delivered to the user's inbox. The provided material documents Claude Code, Cursor, Codex, and GitHub Copilot or VS Code setup paths; other clients may require their own MCP configuration and authentication flow.