AI / Any MCP client
A URL and a browser sign-in
Bird's MCP server is hosted, so any client that speaks MCP reaches it with one URL and one sign-in. There is nothing to install and no local process to keep running.
One URL, one sign-in, no install
Every client names this screen something different, so what follows is the shape rather than a menu path. If yours takes a remote server URL, this is all it needs.
{
"mcpServers": {
"bird": { "url": "https://mcp.bird.com" }
}
}
What the tools cover.The same three operations every Bird client gets. A chat client has no shell, so it calls the tools directly rather than driving the CLI.
Send a message. Send it, then read it back, because accepted is not the same as arrived.
$ email.send
$ email.get
Set up a sender. Create the domain, add the DNS records it hands you, then verify. Not immediately: DNS takes its time.
$ domains.create
$ domains.verify
Get notified of events. Tell Bird where to send them, then test that they land. Keep the signing secret from the create call, because it is never shown again.
$ webhooks.create
$ webhooks.test