Bird MCP integration for AI agents.
Connect AI agents to Bird through 12 structured actions, including get channel, create contact, and delete contact. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bird integration exposes
The Bird Agent App exposes 12 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent retrieve a specific bird workspace channel by id, create a bird contact with identifiers, attributes, display name, or list ids, and delete a bird contact by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bird account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bird capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_channelREADRetrieve a specific Bird workspace channel by ID.
INPUTS: workspaceId / channelId
create_contactWRITECreate a Bird contact with identifiers, attributes, display name, or list IDs.
INPUTS: workspaceId / contact
delete_contactHIGH IMPACTDelete a Bird contact by ID.
INPUTS: workspaceId / contactId
get_contactREADRetrieve a Bird contact by ID, optionally requesting specific attributes.
INPUTS: workspaceId / contactId / attribute
get_messageREADRetrieve a Bird channel message by ID.
INPUTS: workspaceId / channelId / messageId
list_channelsREADList channels configured for a Bird workspace with optional filters.
INPUTS: workspaceId / limit / pageToken / reverse / platform
list_contactsREADList contacts in a Bird workspace.
INPUTS: workspaceId
list_message_interactionsREADList interactions recorded for a Bird channel message.
INPUTS: workspaceId / channelId / messageId
search_contact_by_identifierREADSearch Bird contacts by an identifier key and value.
INPUTS: workspaceId / identifier
send_batch_messagesWRITESend a batch of up to 100 messages through a Bird workspace channel and return the accepted batch IDs.
INPUTS: workspaceId / channelId / messages
send_messageWRITESend one message through a Bird workspace channel.
INPUTS: workspaceId / channelId / message
update_contactWRITEUpdate a Bird contact's identifiers, attributes, or list memberships.
INPUTS: workspaceId / contactId / patch
INPUT CONTRACTS
Know what the action needs before it runs.
get_channel
workspaceIdOPTIONAL- The Bird workspace ID.
channelIdOPTIONAL- The Bird channel ID.
create_contact
workspaceIdOPTIONAL- The Bird workspace ID.
contactOPTIONAL- The Bird contact fields to create.
delete_contact
workspaceIdOPTIONAL- The Bird workspace ID.
contactIdOPTIONAL- The Bird contact ID.
get_contact
workspaceIdREQUIRED- The Bird workspace ID.
contactIdREQUIRED- The Bird contact ID.
attributeOPTIONAL- A contact attribute name to include in the response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Channel
Retrieve a specific Bird workspace channel by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_channelControl Create Contact
Create a Bird contact with identifiers, attributes, display name, or list IDs. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Contact
Retrieve a Bird contact by ID, optionally requesting specific attributes. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contactSAFETY BOUNDARY
Operate Bird with explicit limits
- Authorize Bird with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bird rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bird task completed successfully.
CONNECTION MODEL
API key
Bird access key used in the Authorization header for API requests. Create and manage access keys in Bird security settings: https://app.bird.com/settings/security/access-keys
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bird.