Skip to content
actionlake
Start free

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 freeSee 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
  • 95actionsin one signed file
  • 48readlook, never change
  • 31writecreate and update
  • 16wait for a yesdestructive, 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_tokenHoneybadger personal auth token (user settings > Authentication)
    • hostWhere 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 callcheck { 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 2026docs.honeybadger.iodocs.honeybadger.io
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.

  • 48readlook, never change
  • 31writecreate and update
  • 16destructivewait 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.

ActionWhat it doesEffectSame name in
honeybadger.faults.listList faults (errors)List faults (errors).readmonitoring.alert.list51 connectors
honeybadger.sites.listList uptime checks (sites)List uptime checks (sites).readmonitoring.monitor.list32 connectors
honeybadger.teams.listList teamsList teams.readidentity.group.list262 connectors
honeybadger.projects.listList projectsList projects.readwork.project.list109 connectors
honeybadger.team_members.listList team membersList team members.readidentity.group_member.list103 connectors
honeybadger.deploys.listList deploysList deploys.readdevops.deployment.list22 connectors
honeybadger.sites.createCreate an uptime check (site)Create an uptime check (site).writemonitoring.monitor.create27 connectors
honeybadger.faults.getGet a fault (error)Get a fault (error).readmonitoring.alert.get33 connectors
honeybadger.teams.createCreate a teamCreate a team.writeidentity.group.create205 connectors
honeybadger.sites.deleteDelete an uptime check (site)Delete an uptime check (site).destructivemonitoring.monitor.delete31 connectors
honeybadger.projects.createCreate a projectCreate a project.writework.project.create102 connectors
honeybadger.deploys.getGet a deployGet a deploy.readdevops.deployment.get22 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. Readread

    Give me a one-line status for every active Honeybadger project.

    callshoneybadger.projects.list

  2. Writewrite

    Create an uptime check (site) in Honeybadger. Show me exactly what you will send before you save it.

    callshoneybadger.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 faulthoneybadger.faults.delete
  • Delete a teamhoneybadger.teams.delete
  • Delete a projecthoneybadger.projects.delete
  • Delete a deployhoneybadger.deploys.delete
  • Delete an Insights dashboardhoneybadger.dashboards.delete
  • Delete an environmenthoneybadger.environments.delete
  • Delete an Insights alarmhoneybadger.alarms.delete
  • Delete a fault commenthoneybadger.comments.delete
  • Delete a check-inhoneybadger.check_ins.delete
  • Delete a status pagehoneybadger.status_pages.delete
  • Remove a team memberhoneybadger.team_members.delete
  • Remove a user from the accounthoneybadger.account_users.delete
  • Sync all check-ins (replaces the set)honeybadger.check_ins.replace_all
  • Delete a team invitationhoneybadger.team_invitations.delete
  • Delete an account invitationhoneybadger.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.

dohoneybadger.sites.deleteconfirm_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: "[email protected]" },    { match: "honeybadger.faults.delete", approver: "[email protected]" },    { match: "honeybadger.teams.delete", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 95 Honeybadger actions
  • 95actions pageeach page of a long list is one call
  • 48reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Honeybadger action.

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

Faults13
  • honeybadger.faults.affected_usersList users affected by a faultread
  • honeybadger.faults.deleteDelete a faultdestructive
  • honeybadger.faults.getGet a fault (error)read
  • honeybadger.faults.linkLink a fault to an issuewrite
  • honeybadger.faults.listList faults (errors)read
  • honeybadger.faults.occurrencesCount occurrences for a faultread
  • honeybadger.faults.pausePause fault notificationswrite
  • honeybadger.faults.resolve_allBulk-resolve faultswrite
  • honeybadger.faults.summaryCount faultsread
  • honeybadger.faults.unlinkUnlink a fault from an issuewrite
  • honeybadger.faults.unpauseUnpause fault notificationswrite
  • honeybadger.faults.unpause_allUnpause all faults in a projectwrite
  • honeybadger.faults.updateUpdate a fault (resolve, ignore, assign)write
Projects8
  • honeybadger.projects.createCreate a projectwrite
  • honeybadger.projects.deleteDelete a projectdestructive
  • honeybadger.projects.getGet a projectread
  • honeybadger.projects.integrationsList project integrationsread
  • honeybadger.projects.listList projectsread
  • honeybadger.projects.occurrencesCount occurrences for a projectread
  • honeybadger.projects.occurrences_allCount occurrences across all projectsread
  • honeybadger.projects.updateUpdate a projectwrite
Alarms6
  • honeybadger.alarms.createCreate an Insights alarmwrite
  • honeybadger.alarms.deleteDelete an Insights alarmdestructive
  • honeybadger.alarms.getGet an Insights alarmread
  • honeybadger.alarms.historyGet alarm trigger historyread
  • honeybadger.alarms.listList Insights alarmsread
  • honeybadger.alarms.updateReplace an Insights alarmwrite
Check ins6
  • honeybadger.check_ins.createCreate a check-inwrite
  • honeybadger.check_ins.deleteDelete a check-indestructive
  • honeybadger.check_ins.getGet a check-inread
  • honeybadger.check_ins.listList check-insread
  • honeybadger.check_ins.replace_allSync all check-ins (replaces the set)destructive
  • honeybadger.check_ins.updateUpdate a check-inwrite
Account invitations5
  • honeybadger.account_invitations.createInvite a user to the accountwrite
  • honeybadger.account_invitations.deleteDelete an account invitationdestructive
  • honeybadger.account_invitations.getGet an account invitationread
  • honeybadger.account_invitations.listList account invitationsread
  • honeybadger.account_invitations.updateUpdate an account invitationwrite
Comments5
  • honeybadger.comments.createComment on a faultwrite
  • honeybadger.comments.deleteDelete a fault commentdestructive
  • honeybadger.comments.getGet a fault commentread
  • honeybadger.comments.listList fault commentsread
  • honeybadger.comments.updateUpdate a fault commentwrite
Dashboards5
  • honeybadger.dashboards.createCreate an Insights dashboardwrite
  • honeybadger.dashboards.deleteDelete an Insights dashboarddestructive
  • honeybadger.dashboards.getGet an Insights dashboardread
  • honeybadger.dashboards.listList Insights dashboardsread
  • honeybadger.dashboards.updateReplace an Insights dashboardwrite
Environments5
  • honeybadger.environments.createCreate an environmentwrite
  • honeybadger.environments.deleteDelete an environmentdestructive
  • honeybadger.environments.getGet an environmentread
  • honeybadger.environments.listList environmentsread
  • honeybadger.environments.updateUpdate an environmentwrite
Sites5
  • honeybadger.sites.createCreate an uptime check (site)write
  • honeybadger.sites.deleteDelete an uptime check (site)destructive
  • honeybadger.sites.getGet an uptime check (site)read
  • honeybadger.sites.listList uptime checks (sites)read
  • honeybadger.sites.updateUpdate an uptime check (site)write
Status pages5
  • honeybadger.status_pages.createCreate a status pagewrite
  • honeybadger.status_pages.deleteDelete a status pagedestructive
  • honeybadger.status_pages.getGet a status pageread
  • honeybadger.status_pages.listList status pagesread
  • honeybadger.status_pages.updateUpdate a status pagewrite
Team invitations5
  • honeybadger.team_invitations.createInvite a user to a teamwrite
  • honeybadger.team_invitations.deleteDelete a team invitationdestructive
  • honeybadger.team_invitations.getGet a team invitationread
  • honeybadger.team_invitations.listList team invitationsread
  • honeybadger.team_invitations.updateUpdate a team invitationwrite
Teams5
  • honeybadger.teams.createCreate a teamwrite
  • honeybadger.teams.deleteDelete a teamdestructive
  • honeybadger.teams.getGet a teamread
  • honeybadger.teams.listList teamsread
  • honeybadger.teams.updateRename a teamwrite
Account users4
  • honeybadger.account_users.deleteRemove a user from the accountdestructive
  • honeybadger.account_users.getGet an account userread
  • honeybadger.account_users.listList account usersread
  • honeybadger.account_users.updateUpdate an account user's rolewrite
Reports4
  • honeybadger.reports.notices_by_classReport: notices by error classread
  • honeybadger.reports.notices_by_locationReport: notices by locationread
  • honeybadger.reports.notices_by_userReport: notices by userread
  • honeybadger.reports.notices_per_dayReport: notices per dayread
Team members4
  • honeybadger.team_members.deleteRemove a team memberdestructive
  • honeybadger.team_members.getGet a team memberread
  • honeybadger.team_members.listList team membersread
  • honeybadger.team_members.updateUpdate a team memberwrite
Deploys3
  • honeybadger.deploys.deleteDelete a deploydestructive
  • honeybadger.deploys.getGet a deployread
  • honeybadger.deploys.listList deploysread
Accounts2
  • honeybadger.accounts.getGet an accountread
  • honeybadger.accounts.listList accountsread
Insights1
  • honeybadger.insights.queryRun an Insights (BadgerQL) queryread
Notices1
  • honeybadger.notices.listList notices (error occurrences)read
Outages1
  • honeybadger.outages.listList outages for a siteread
Streams1
  • honeybadger.streams.listList Insights streamsread
Uptime checks1
  • honeybadger.uptime_checks.listList uptime check results for a siteread

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

Joins with, on shared entities

Browse

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 freeSee pricing

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