Bugsnag MCP integration for AI agents.
Connect AI agents to Bugsnag through 7 structured actions, including get latest error event, get organization, and list error events. Review authentication…
- ACTION CONTRACTS
- 7
- 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 Bugsnag integration exposes
The Bugsnag Agent App exposes 7 provider-backed actions for developer tools and security work. Its current contract lets an authorized agent get the latest event recorded on a bugsnag error, get a bugsnag organization by organization id, and list the events recorded on a bugsnag error. 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 Bugsnag account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bugsnag capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_latest_error_eventREADGet the latest event recorded on a Bugsnag error.
INPUTS: errorId
get_organizationREADGet a Bugsnag organization by organization ID.
INPUTS: organizationId
list_error_eventsREADList the events recorded on a Bugsnag error.
INPUTS: projectId / errorId / base / direction / perPage
list_organization_projectsREADList the projects that belong to a Bugsnag organization.
INPUTS: organizationId / query / sort / direction / perPage
list_organizationsREADList the organizations accessible to the current Bugsnag user.
INPUTS: admin / perPage
list_project_errorsREADList the errors reported on a Bugsnag project.
INPUTS: projectId / base / sort / direction / perPage
list_project_releasesREADList the releases associated with a Bugsnag project.
INPUTS: projectId / releaseStage / base / sort / offset
INPUT CONTRACTS
Know what the action needs before it runs.
get_latest_error_event
errorIdREQUIRED- The Bugsnag error identifier.
get_organization
organizationIdREQUIRED- The Bugsnag organization identifier to retrieve.
list_error_events
projectIdREQUIRED- The Bugsnag project identifier.
errorIdREQUIRED- The Bugsnag error identifier.
baseOPTIONAL- The ISO 8601 timestamp used as the time anchor for the event list.
directionOPTIONAL- The sort direction for the error events.
perPageOPTIONAL- The number of events to return per page.
list_organization_projects
organizationIdREQUIRED- The Bugsnag organization identifier that owns the projects.
queryOPTIONAL- The project-name search query.
sortOPTIONAL- The field used to sort Bugsnag organization projects.
directionOPTIONAL- The sort direction for the project list.
perPageOPTIONAL- The number of projects to return per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Latest Error Event
Get the latest event recorded on a Bugsnag error. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_latest_error_eventVerify with Get Organization
Get a Bugsnag organization by organization ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_organizationSAFETY BOUNDARY
Operate Bugsnag with explicit limits
- Authorize Bugsnag with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Bugsnag data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bugsnag rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bugsnag task completed successfully.
CONNECTION MODEL
API key
Bugsnag personal auth token sent with the Authorization header using the token prefix. Find it on your Bugsnag project overview page after signing in: https://app.bugsnag.com/.
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
- 0
- 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 Bugsnag.