---
title: "Honeybadger MCP server for AI agents - actionlake"
description: "Give Claude 95 Honeybadger actions through one MCP server: faults, projects, alarms. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/honeybadger
updated: 2026-10-23
---

Connectors · Observability & analytics

# Honeybadger MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Honeybadger and the rest of your systems. It gives your agent 95 Honeybadger actions (48 reads, 31 writes and 16 that wait for a confirmation) and holds the Honeybadger credential itself, so the agent never does. It paces Honeybadger's limits and records every call.

[Connect Honeybadger free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "honeybadger.teams.list",
  intent: "check which Honeybadger account is connected"
}
# List teams · read · 1 upstream call
```

- 95 actions in one signed file
- 48 read look, never change
- 31 write create and update
- 16 wait for a yes destructive, confirmed first

Set up

## Connect Honeybadger in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Honeybadger.
   Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `auth_token` Honeybadger personal auth token (user settings > Authentication)
   - `host` Where your Honeybadger lives: your host
   ```
   account { op: "connections.requirements", service: "honeybadger" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "honeybadger.teams.list" }
   # list teams · read · 1 upstream call
   check { action: "honeybadger.sites.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Honeybadger at a glance

**Sign-in**

Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`auth_token`

**Setup fields**

`host`

**Limits we pace to**

360 calls an hour, per connection

**API covered**

Honeybadger Data API v2, at your Honeybadger instance's API base URL, which you enter when connecting

**Built from**

Honeybadger's documentation, read 23 October 2026[docs.honeybadger.io](https://docs.honeybadger.io/api/) [docs.honeybadger.io](https://docs.honeybadger.io/api/getting-started/)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

48 of 48 reads, for up to 1 minute; a write clears what it affects

**Shared entities**

6, so ask can line Honeybadger up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Honeybadger.

95 actions in 22 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **48** read look, never change
- **31** write create and update
- **16** destructive wait for a confirmation

1. ### Faults
   13
   5 read · 7 write · 1 destructive
   List faults (errors) · Get a fault (error) · Update a fault (resolve, ignore, assign) · Delete a fault
2. ### Projects
   8
   5 read · 2 write · 1 destructive
   List projects · Create a project · Get a project · Update a project
3. ### Alarms
   6
   3 read · 2 write · 1 destructive
   Create an Insights alarm · Get alarm trigger history · List Insights alarms · Get an Insights alarm
4. ### Check ins
   6
   2 read · 2 write · 2 destructive
   Create a check-in · List check-ins · Get a check-in · Update a check-in
5. ### Account invitations
   5
   2 read · 2 write · 1 destructive
   Invite a user to the account · List account invitations · Get an account invitation · Update an account invitation
6. ### Comments
   5
   2 read · 2 write · 1 destructive
   Comment on a fault · List fault comments · Get a fault comment · Update a fault comment
7. ### Dashboards
   5
   2 read · 2 write · 1 destructive
   List Insights dashboards · Create an Insights dashboard · Get an Insights dashboard · Replace an Insights dashboard
8. ### Environments
   5
   2 read · 2 write · 1 destructive
   List environments · Create an environment · Get an environment · Update an environment

**14 more areas · 42 actions**

- Sites **5**
- Status pages **5**
- Team invitations **5**
- Teams **5**
- Account users **4**
- Reports **4**
- Team members **4**
- Deploys **3**
- Accounts **2**
- Insights **1**
- Notices **1**
- Outages **1**
- Streams **1**
- Uptime checks **1**

Top actions

## The Honeybadger API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 35 of Honeybadger's 35 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `honeybadger.faults.list` List faults (errors) | List faults (errors). | read | `monitoring.alert.list` 51 connectors |
| `honeybadger.sites.list` List uptime checks (sites) | List uptime checks (sites). | read | `monitoring.monitor.list` 32 connectors |
| `honeybadger.teams.list` List teams | List teams. | read | `identity.group.list` 262 connectors |
| `honeybadger.projects.list` List projects | List projects. | read | `work.project.list` 109 connectors |
| `honeybadger.team_members.list` List team members | List team members. | read | `identity.group_member.list` 103 connectors |
| `honeybadger.deploys.list` List deploys | List deploys. | read | `devops.deployment.list` 22 connectors |
| `honeybadger.sites.create` Create an uptime check (site) | Create an uptime check (site). | write | `monitoring.monitor.create` 27 connectors |
| `honeybadger.faults.get` Get a fault (error) | Get a fault (error). | read | `monitoring.alert.get` 33 connectors |
| `honeybadger.teams.create` Create a team | Create a team. | write | `identity.group.create` 205 connectors |
| `honeybadger.sites.delete` Delete an uptime check (site) | Delete an uptime check (site). | destructive | `monitoring.monitor.delete` 31 connectors |
| `honeybadger.projects.create` Create a project | Create a project. | write | `work.project.create` 102 connectors |
| `honeybadger.deploys.get` Get a deploy | Get a deploy. | read | `devops.deployment.get` 22 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Honeybadger actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Give me a one-line status for every active Honeybadger project.
   calls `honeybadger.projects.list`
2. Write write
   Create an uptime check (site) in Honeybadger. Show me exactly what you will send before you save it.
   calls `honeybadger.sites.create`

Governance for Honeybadger

## Destructive actions wait for a yes.

16 Honeybadger actions are destructive. These are all of them:

- Delete an uptime check (site) `honeybadger.sites.delete`
- Delete a fault `honeybadger.faults.delete`
- Delete a team `honeybadger.teams.delete`
- Delete a project `honeybadger.projects.delete`
- Delete a deploy `honeybadger.deploys.delete`
- Delete an Insights dashboard `honeybadger.dashboards.delete`
- Delete an environment `honeybadger.environments.delete`
- Delete an Insights alarm `honeybadger.alarms.delete`
- Delete a fault comment `honeybadger.comments.delete`
- Delete a check-in `honeybadger.check_ins.delete`
- Delete a status page `honeybadger.status_pages.delete`
- Remove a team member `honeybadger.team_members.delete`
- Remove a user from the account `honeybadger.account_users.delete`
- Sync all check-ins (replaces the set) `honeybadger.check_ins.replace_all`
- Delete a team invitation `honeybadger.team_invitations.delete`
- Delete an account invitation `honeybadger.account_invitations.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do honeybadger.sites.delete confirm_policy: **human**

Delete an uptime check (site)?

**intent:** the user asked me to delete an uptime check (site)

run suspended · waiting for a named person · key _honeybadger-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "honeybadger-agent",
  allowed_actions: ["honeybadger.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "honeybadger.sites.delete", approver: "lead@example.com" },
    { match: "honeybadger.faults.delete", approver: "lead@example.com" },
    { match: "honeybadger.teams.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Honeybadger only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Honeybadger costs on actionlake.

Every Honeybadger action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Honeybadger refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 95 Honeybadger actions
- 95 actions page each page of a long list is one call
- 48 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Honeybadger action.

95 actions by area: the id your agent calls, what it does, and its effect.

**Faults 13**

- `honeybadger.faults.affected_users` List users affected by a fault read
- `honeybadger.faults.delete` Delete a fault destructive
- `honeybadger.faults.get` Get a fault (error) read
- `honeybadger.faults.link` Link a fault to an issue write
- `honeybadger.faults.list` List faults (errors) read
- `honeybadger.faults.occurrences` Count occurrences for a fault read
- `honeybadger.faults.pause` Pause fault notifications write
- `honeybadger.faults.resolve_all` Bulk-resolve faults write
- `honeybadger.faults.summary` Count faults read
- `honeybadger.faults.unlink` Unlink a fault from an issue write
- `honeybadger.faults.unpause` Unpause fault notifications write
- `honeybadger.faults.unpause_all` Unpause all faults in a project write
- `honeybadger.faults.update` Update a fault (resolve, ignore, assign) write

**Projects 8**

- `honeybadger.projects.create` Create a project write
- `honeybadger.projects.delete` Delete a project destructive
- `honeybadger.projects.get` Get a project read
- `honeybadger.projects.integrations` List project integrations read
- `honeybadger.projects.list` List projects read
- `honeybadger.projects.occurrences` Count occurrences for a project read
- `honeybadger.projects.occurrences_all` Count occurrences across all projects read
- `honeybadger.projects.update` Update a project write

**Alarms 6**

- `honeybadger.alarms.create` Create an Insights alarm write
- `honeybadger.alarms.delete` Delete an Insights alarm destructive
- `honeybadger.alarms.get` Get an Insights alarm read
- `honeybadger.alarms.history` Get alarm trigger history read
- `honeybadger.alarms.list` List Insights alarms read
- `honeybadger.alarms.update` Replace an Insights alarm write

**Check ins 6**

- `honeybadger.check_ins.create` Create a check-in write
- `honeybadger.check_ins.delete` Delete a check-in destructive
- `honeybadger.check_ins.get` Get a check-in read
- `honeybadger.check_ins.list` List check-ins read
- `honeybadger.check_ins.replace_all` Sync all check-ins (replaces the set) destructive
- `honeybadger.check_ins.update` Update a check-in write

**Account invitations 5**

- `honeybadger.account_invitations.create` Invite a user to the account write
- `honeybadger.account_invitations.delete` Delete an account invitation destructive
- `honeybadger.account_invitations.get` Get an account invitation read
- `honeybadger.account_invitations.list` List account invitations read
- `honeybadger.account_invitations.update` Update an account invitation write

**Comments 5**

- `honeybadger.comments.create` Comment on a fault write
- `honeybadger.comments.delete` Delete a fault comment destructive
- `honeybadger.comments.get` Get a fault comment read
- `honeybadger.comments.list` List fault comments read
- `honeybadger.comments.update` Update a fault comment write

**Dashboards 5**

- `honeybadger.dashboards.create` Create an Insights dashboard write
- `honeybadger.dashboards.delete` Delete an Insights dashboard destructive
- `honeybadger.dashboards.get` Get an Insights dashboard read
- `honeybadger.dashboards.list` List Insights dashboards read
- `honeybadger.dashboards.update` Replace an Insights dashboard write

**Environments 5**

- `honeybadger.environments.create` Create an environment write
- `honeybadger.environments.delete` Delete an environment destructive
- `honeybadger.environments.get` Get an environment read
- `honeybadger.environments.list` List environments read
- `honeybadger.environments.update` Update an environment write

**Sites 5**

- `honeybadger.sites.create` Create an uptime check (site) write
- `honeybadger.sites.delete` Delete an uptime check (site) destructive
- `honeybadger.sites.get` Get an uptime check (site) read
- `honeybadger.sites.list` List uptime checks (sites) read
- `honeybadger.sites.update` Update an uptime check (site) write

**Status pages 5**

- `honeybadger.status_pages.create` Create a status page write
- `honeybadger.status_pages.delete` Delete a status page destructive
- `honeybadger.status_pages.get` Get a status page read
- `honeybadger.status_pages.list` List status pages read
- `honeybadger.status_pages.update` Update a status page write

**Team invitations 5**

- `honeybadger.team_invitations.create` Invite a user to a team write
- `honeybadger.team_invitations.delete` Delete a team invitation destructive
- `honeybadger.team_invitations.get` Get a team invitation read
- `honeybadger.team_invitations.list` List team invitations read
- `honeybadger.team_invitations.update` Update a team invitation write

**Teams 5**

- `honeybadger.teams.create` Create a team write
- `honeybadger.teams.delete` Delete a team destructive
- `honeybadger.teams.get` Get a team read
- `honeybadger.teams.list` List teams read
- `honeybadger.teams.update` Rename a team write

**Account users 4**

- `honeybadger.account_users.delete` Remove a user from the account destructive
- `honeybadger.account_users.get` Get an account user read
- `honeybadger.account_users.list` List account users read
- `honeybadger.account_users.update` Update an account user's role write

**Reports 4**

- `honeybadger.reports.notices_by_class` Report: notices by error class read
- `honeybadger.reports.notices_by_location` Report: notices by location read
- `honeybadger.reports.notices_by_user` Report: notices by user read
- `honeybadger.reports.notices_per_day` Report: notices per day read

**Team members 4**

- `honeybadger.team_members.delete` Remove a team member destructive
- `honeybadger.team_members.get` Get a team member read
- `honeybadger.team_members.list` List team members read
- `honeybadger.team_members.update` Update a team member write

**Deploys 3**

- `honeybadger.deploys.delete` Delete a deploy destructive
- `honeybadger.deploys.get` Get a deploy read
- `honeybadger.deploys.list` List deploys read

**Accounts 2**

- `honeybadger.accounts.get` Get an account read
- `honeybadger.accounts.list` List accounts read

**Insights 1**

- `honeybadger.insights.query` Run an Insights (BadgerQL) query read

**Notices 1**

- `honeybadger.notices.list` List notices (error occurrences) read

**Outages 1**

- `honeybadger.outages.list` List outages for a site read

**Streams 1**

- `honeybadger.streams.list` List Insights streams read

**Uptime checks 1**

- `honeybadger.uptime_checks.list` List uptime check results for a site read

Questions

## The Honeybadger MCP server, answered.

**Is there a Honeybadger MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 95 Honeybadger actions across faults, projects, alarms and check ins, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Honeybadger.

**What do I need to connect Honeybadger?**

Honeybadger personal auth token (user settings > Authentication). Plus your host. The free call account { op: "connections.requirements", service: "honeybadger" } lists exactly what to paste.

**Can an AI agent delete or change things in Honeybadger?**

Only if its key allows it, and only with an explicit confirmation. 16 Honeybadger actions are destructive, including delete an uptime check (site), delete a fault and delete a team. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Honeybadger API limit?**

actionlake paces every call to the limits in the Honeybadger service file: 360 calls an hour per connection. Repeated reads are answered from cache (48 Honeybadger actions can be), which never reaches Honeybadger.

**What does a Honeybadger action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (95 Honeybadger actions page). Cache hits, searches, dry runs and calls Honeybadger refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Honeybadger API does it cover?**

The Honeybadger Data API v2 at your Honeybadger instance's API base URL, which you enter when connecting. It is built from Honeybadger's documentation as read on 23 October 2026. 95 actions in 22 areas, each one in the signed service file (version 1.0.0).

**Does actionlake keep my Honeybadger data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 1 minute, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Honeybadger credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Honeybadger

Shares the most action names with

- [Sentry 21](https://actionlake.com/connectors/sentry)
- [Axiom 15](https://actionlake.com/connectors/axiom)
- [IBM NS1 Connect 14](https://actionlake.com/connectors/ibm-ns1-connect)
- [Uptrends 14](https://actionlake.com/connectors/uptrends)
- [Domo 11](https://actionlake.com/connectors/domo)
- [Better Stack Telemetry 9](https://actionlake.com/connectors/better-stack-telemetry)

Joins with, on shared entities

- [Octopus Deploy 3](https://actionlake.com/connectors/octopus-deploy)
- [MongoDB Atlas 3](https://actionlake.com/connectors/mongodb-atlas)
- [Vercel 3](https://actionlake.com/connectors/vercel)
- [Workato 3](https://actionlake.com/connectors/workato)
- [ilert 3](https://actionlake.com/connectors/ilert)
- [Miro 3](https://actionlake.com/connectors/miro)

Browse

- [All Observability & analytics connectors](https://actionlake.com/connectors/category/observability-and-analytics)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Honeybadger; the name is the vendor's own. Counts are from the Honeybadger service file, version 1.0.0.

## Give your agent Honeybadger today.

[Connect Honeybadger free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/honeybadger
More: https://actionlake.com/llms.txt