Airbrake MCP integration for AI agents.
Connect AI agents to Airbrake through 8 structured actions, including get group, get deploy, and get notice status. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 8
- 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 Airbrake integration exposes
The Airbrake Agent App exposes 8 provider-backed actions for developer tools and data work. Its current contract lets an authorized agent get details for one airbrake error group, get details for one airbrake deploy, and get airbrake processing status for a notice uuid. 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 Airbrake account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Airbrake capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_groupREADGet details for one Airbrake error group.
INPUTS: projectId / groupId
get_deployHIGH IMPACTGet details for one Airbrake deploy.
INPUTS: projectId / deployId
get_notice_statusREADGet Airbrake processing status for a notice UUID.
INPUTS: projectId / noticeUuid
get_projectREADGet details for one Airbrake project.
INPUTS: projectId
list_deploysREADList deploys for one Airbrake project.
INPUTS: projectId / page / limit
list_groupsREADList error groups for one Airbrake project with optional filters.
INPUTS: projectId / page / limit / deployId / archived
list_noticesREADList notices for one Airbrake error group.
INPUTS: projectId / groupId / page / limit / version
list_projectsREADList Airbrake projects visible to the User API key.
INPUTS: page / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_group
projectIdREQUIRED- The Airbrake project integer identifier.
groupIdREQUIRED- The Airbrake group integer identifier.
get_deploy
projectIdREQUIRED- The Airbrake project integer identifier.
deployIdREQUIRED- The Airbrake deploy integer identifier.
get_notice_status
projectIdREQUIRED- The Airbrake project integer identifier.
noticeUuidREQUIRED- The Airbrake notice UUID returned by notice creation.
get_project
projectIdREQUIRED- The Airbrake project integer identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Group
Get details for one Airbrake error group. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_groupControl Get Deploy
Get details for one Airbrake deploy. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
get_deployVerify with Get Notice Status
Get Airbrake processing status for a notice UUID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_notice_statusSAFETY BOUNDARY
Operate Airbrake with explicit limits
- Authorize Airbrake with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `get_deploy` 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 Airbrake rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Airbrake task completed successfully.
CONNECTION MODEL
API key
Airbrake User API key sent as the key query parameter. Airbrake documents User API keys for accessing project data: https://docs.airbrake.io/docs/devops-tools/api/#authentication
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
- 0
- 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 Airbrake.