messagebird.com
MessageBird/Bird provides communications infrastructure for sending and managing email, SMS, voice, WhatsApp, and related messaging workflows. Its newer Bird platform also includes agent-oriented access via a CLI and MCP server.
messagebird.com exposes two documented HTTP API families (legacy MessageBird REST and newer regional Bird REST), plus a Bird CLI and both hosted and local MCP server surfaces; all require service-issued credentials.
- Bird MCP server (local via CLI)discovered
- MessageBird REST APIdiscovered
- Bird REST APIdiscovered
- Bird CLIdiscovered
In the MessageBird dashboard, go to Developers → API access (Access Keys) and create or copy an access key for your account/workspace. Send it on API requests in the Authorization header as AccessKey <key>. The legacy MessageBird API docs describe this as an access key used by the API Authorization framework.
Create a key in the Bird dashboard under Developers → API keys, or programmatically via POST /v1/api-keys once you already have sufficient rights. Choose the minimal scopes you need; Bird shows the full key exactly once. Use it as Authorization: Bearer bk_{region}_... against the matching regional host.
$ bird auth loginAcquired by the CLI — running bird auth login opens the auth flow and stores the credential.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing