← All integrations

Honeybadger MCP server

62 operations0 webhooks

Error tracking, uptime monitoring, check-ins, deploys and Insights queries from Honeybadger's v3 API.

Try Honeybadger with your agent

Connect Honeybadger, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Honeybadger on my account, then run one read-only example and show me the result.

Runs once, when you ask

Honeybadger tools and triggers

Tools are what your agent can do in Honeybadger through Corsair's MCP server. Triggers are the Honeybadger events a routine can start from.

Faults

  • Affected UsersRead-only

    Read the 500 users a fault affected most, ranked by notice count

    faults.affectedUsers

  • AssignWrite

    Assign a fault to a project member, who is notified of it

    faults.assign

  • DeleteDestructive

    Permanently delete a fault; its notices stay readable by ID until retention removes them

    faults.delete

  • GetRead-only

    Read one fault by ID; a merged fault redirects to the fault it was merged into

    faults.get

  • IgnoreWrite

    Ignore faults, which stops data collection for them, by ID or by query with `all: true`

    faults.ignore

  • ListRead-only

    List faults with error search, sorting and time filters; occurrence counts cover the requested window

    faults.list

  • MergeDestructive

    Merge one fault into another in the background; the merged fault keeps its tags, assignee and state on neither side, and its ID redirects for the retention period

    faults.merge

  • OccurrencesRead-only

    Read occurrence counts for one fault over a window, one bucket per interval including empty ones

    faults.occurrences

  • Pause RecordingWrite

    Stop recording a fault for an hour, a day or a week, discarding notices during the pause

    faults.pauseRecording

  • ResolveWrite

    Resolve named faults, or every fault a query and time filter match with `all: true`; `dry_run` reports what would change

    faults.resolve

  • Resume RecordingWrite

    Resume recording a fault; a fault that is not paused is unchanged

    faults.resumeRecording

  • SnoozeWrite

    Snooze notifications for a duration or an occurrence count, replacing any existing snooze

    faults.snooze

Connect Honeybadger to Claude, ChatGPT or Cursor

  1. 1

    Connect Honeybadger in Corsair

    Add your Honeybadger API key once in Corsair. Corsair stores the credential encrypted and makes the Honeybadger API calls for your agent, so it never goes into a prompt or a config file. Connect Honeybadger

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Honeybadger. On a ChatGPT personal plan, connect Honeybadger here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Honeybadger's read and write operations run right away and its 10 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/honeybadger, add the Honeybadger plugin, and connect with an API key. Then call methods like corsair.honeybadger.api.account.get() from your app. Corsair keeps each tenant isolated.

Yes. Honeybadger requires an API key from your Honeybadger account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Honeybadger, GitHub, Notion, Stripe, and the rest. Trigger Honeybadger from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for error tracking, uptime monitoring, check-ins, deploys and Insights queries from Honeybadger's v3 API. Common builds include sync jobs, admin tooling, and agents that call Honeybadger APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Honeybadger API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/honeybadger in the open repo. When Honeybadger ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Honeybadger data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Honeybadger data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Honeybadger on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 10 destructive Honeybadger operations. You can change a link's mode at hub.corsair.dev/me.