Bird

An agent signs in to Bird through browser OAuth and then acts with a scoped, revocable grant. Through the hosted MCP server it sends email, SMS, WhatsApp messages and one time passcodes, orders phone numbers, adds sending domains and senders, and manages templates, contacts, audiences and preferences.

Grants cover only the overlap of what the client asked for, what the user approved and what the user holds, and owner and platform admin scopes can never be delegated. In the other direction, webhook destination connectors hand each inbound message to a Claude Managed Agents session or a Grok routine. Connections to the customer's own business systems are the customer's agent's to make.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

Events move to the agent and its output moves back out through Bird. Each inbound WhatsApp, SMS, Apple Messages or mailbox message is delivered as event JSON, failed deliveries are retried, and a webhook can be paused or deleted.

The sequence of steps an agent takes, its tools and its decisions run in the customer's agent platform, and for voice the customer's application owns speech, reasoning and business tools while Bird carries the call.

There is no workflow builder or multistep runtime for agents inside Bird, so a reminder sequence or an escalation path is something the customer's agent or its own scheduler runs.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

No knowledge base for an agent to search sits inside Bird. Its skills are instruction packs for the agent itself, one routing requests to the right CLI command group and one auditing a sending domain's authentication and mail records, and the knowledge base Bird runs is customer help for account setup, deliverability and billing. Grounding an agent in a company's own documents happens in whatever agent platform the customer runs. Templates, contacts and audiences in Bird hold messaging data, which an agent can read through the MCP server but which is not indexed for retrieval.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

A person approves each agent's access on a consent screen that flags the client name as unverified, can revoke the grant at once under connected apps, and can pause a webhook to stop deliveries.

The outbound call tool prepares a call that a person reviews and places from the browser, template versions reach recipients only once submitted, and destructive tools carry annotations so the agent host can ask before running them.

Sends of email, SMS and WhatsApp go out when the agent calls the tool, with no Bird approval step in between, and handing a conversation to a person is left to the customer's own systems.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

Teams are organized into workspaces with member roles, API keys are scoped per channel with none, read or write access to email, SMS and WhatsApp, and agent access runs on OAuth grants limited to what the user holds and approved. Bird holds ISO/IEC 27001:2022, SOC 2 Type 2 and SOC 3 reports and HIPAA compliance, and its trust center supplies an ISO certificate bundle, statement of applicability and penetration test letters on request. Bird does not mention single sign on for its dashboard.

Sourcebird.com/securityread 2026-10-11

Audit logs record changes such as API key updates and member invitations, each webhook attempt shows the agent platform's response status and body or a failure reason, and call records and voice events track phone calls, with every message kept as a record in its region. That shows what reached the agent and what Bird sent. The agent's own reasoning and tool sequence are logged in the platform that runs it.

Sourcebird.com/securityread 2026-10-11

Every routed message starts a new session or run, and the agent receives the event payload for that message alone, so any history across messages lives in the customer's agent platform. Message records, contacts and audiences persist in the organization's region as the messaging data model, and an agent can look a contact up through the MCP server. Nothing in Bird stores what an agent learned about a person or hands it back on the next message.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Each organization picks the us1 or eu1 region at signup, starting from a guess based on location, and the choice is fixed afterward. The workspace, API keys, messages, recipient data and event logs stay in that region and are never copied across, with only sign in and account administration held globally. Keys carry their region in the prefix, and a request to the wrong region is refused with a 421 error.

Sourcebird.com/docs/api/regionsread 2026-10-11

Agent skills and plugins come for Claude Code, Codex, Cursor, OpenCode and Antigravity, including a CLI router skill and an email audit skill, plus AI builder guides and a setup prompt to paste into an existing agent. These equip an agent the customer already runs. Bird offers no ready made agents for support or sales.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

Inbound WhatsApp, SMS, Apple Messages and agent mailbox email each fire an event, whatsapp.received, sms.received, amb.received and email_mailbox.message_received, that a webhook delivers to the agent and that starts a new agent run. MCP Events let an MCP client subscribe to events such as new mail and receive each as a signed webhook. Voice calls reach a customer built voice application over SIP, and agent mailboxes give an agent an address of its own.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

No model runs inside Bird. The customer's agent platform, whether Claude, Codex, Cursor, Grok or its own voice application, reaches Bird through the CLI, MCP or webhooks, and which model that agent uses is decided entirely outside Bird. The webhook connectors are set up for Claude Managed Agents and Grok, and any other platform receives the same event JSON through a plain webhook.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

Every public endpoint sits in an API reference generated from an OpenAPI spec, with SDKs for TypeScript, Python and Go and a bird CLI for the shell. The MCP server comes in three forms, a hosted endpoint with the full tool catalog, a dynamic endpoint exposing only search and execute for clients with tool limits, and a local server inside the CLI. All three sign in through OAuth with dynamic client registration and PKCE, and their tools create and change Bird's own objects, such as messages, numbers, domains, senders, templates and contacts.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

Each webhook attempt can be inspected with the agent platform's response status and body or the reason a delivery failed, which traces why an agent did not run. Template versions stay away from recipients until they are submitted, so an agent's draft can go out as a test message and be checked on a real phone first. Testing what the agent itself says or does belongs to the agent platform the customer uses.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Agents use Bird through API calls, CLI commands and MCP tools for messaging, numbers and domains. No hosted browser, remote desktop or screen control is part of the platform. Even the outbound call tool stops short of acting on its own, preparing a call that a person reviews and places from the browser.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11