Honeybadger MCP integration for AI agents.
Connect AI agents to Honeybadger through 5 structured actions, including report check in, report deployment, and report check in with payload. Review authent…
- ACTION CONTRACTS
- 5
- 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 Honeybadger integration exposes
The Honeybadger Agent App exposes 5 provider-backed actions for developer tools and security work. Its current contract lets an authorized agent report a honeybadger check-in by id or slug, report a deployment to honeybadger, and report a honeybadger check-in with payload data. 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 Honeybadger account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Honeybadger capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
report_check_inREADReport a Honeybadger check-in by id or slug.
INPUTS: id / slug
report_deploymentREVIEWReport a deployment to Honeybadger.
INPUTS: deploy
report_check_in_with_payloadREADReport a Honeybadger check-in with payload data.
INPUTS: checkInId / checkIn
report_eventREVIEWReport one or more Honeybadger Insights events.
INPUTS: events
report_exceptionREVIEWReport an exception notice to Honeybadger.
INPUTS: error / server / request
INPUT CONTRACTS
Know what the action needs before it runs.
report_check_in
idOPTIONAL- The Honeybadger check-in id or capability token.
slugOPTIONAL- The Honeybadger check-in slug to report by project API key.
report_deployment
deployREQUIRED- The deployment payload sent to Honeybadger.
report_check_in_with_payload
checkInIdREQUIRED- The Honeybadger check-in id or capability token used in the request path.
checkInREQUIRED- The payload body sent to a Honeybadger check-in endpoint.
report_event
eventsREQUIRED- The event objects to serialize into the Honeybadger NDJSON event stream.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Report Check In
Report a Honeybadger check-in by id or slug. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
report_check_inVerify with Report Check In With Payload
Report a Honeybadger check-in with payload data. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
report_check_in_with_payloadSAFETY BOUNDARY
Operate Honeybadger with explicit limits
- Authorize Honeybadger with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Honeybadger 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 Honeybadger rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Honeybadger task completed successfully.
CONNECTION MODEL
API key
Honeybadger project API key used by the Reporting API. Find or rotate it in your project API keys settings.
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
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 3
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 Honeybadger.