get_referenceLABSCO SUMMARY
Error triage plus the query language, with the schema fetched rather than guessed.
The reference tool is what makes the rest work: BadgerQL, chart configuration, dashboard widget schemas and alarm trigger_config are all pulled from Honeybadger's own LLM documentation and cached, so a generated query or alarm matches the real schema instead of a plausible-looking invention — and the alarm tools name the topics to read first. Writes stay off until you turn them on, which is the right default when deleting a project is one of the things in scope.
What it is
A Honeybadger client covering projects, faults and their notices, Insights — BadgerQL queries, streams, dashboards and alarms — and check-ins. It also ships a reference tool that fetches Honeybadger's own LLM documentation, so queries and alarm configs get written against the real schema.
What you get
- Honeybadger's own reference documentation fetched by topic — badgerql, queries, charts, dashboards, alarms, errors — and cached, with each tool declaring which topics it needs
- Projects listed and inspected, with occurrence counts grouped by hour, day, week or month, their integrations, and their report data; created, updated and deleted once writes are enabled
- Faults listed with filtering and ordering, one fault in detail, and fault count statistics for a project
- The individual notices behind a fault, and the users it affected with their occurrence counts
- A fault's resolved, ignored, assignee and resolve-on-deploy state changed, with the fields you omit left alone
- BadgerQL queries executed against Insights data, and the project's Insights data streams listed
- Insights dashboards listed, read, created, updated and deleted
- Insights alarms listed, read, created and updated with their trigger_config, deleted, and their trigger history read
- Check-ins for cron and scheduled tasks listed, read, created, updated and deleted — the listing returns the first 25
- A search across the server's own tools, which in read-only mode returns only the read-only ones
Requirements
A Honeybadger personal auth token, from the Authentication tab of your user settings, in HONEYBADGER_PERSONAL_AUTH_TOKEN. It runs from the ghcr.io/honeybadger-io/honeybadger-mcp-server Docker image, or as a Go binary built from source, and will also read ~/.honeybadger-mcp-server.yaml. Read-only is the default: the write tools — creating and deleting projects, dashboards, alarms and check-ins — are only registered when HONEYBADGER_READ_ONLY is set to false or --read-only=false is passed. On the EU region, set HONEYBADGER_API_URL to https://eu-app.honeybadger.io and use an EU token; a US token will not authenticate there, and the reverse holds too.
Setup effort
One command plus a key — docker pull ghcr.io/honeybadger-io/honeybadger-mcp-server:latest, then supply credentials
USE CASES
01
Triaging what is actually breaking
List the faults with filtering, open the worst of them, and read the notices behind it.
02
Finding out who it hit
Read the affected users with their occurrence counts, alongside the fault's count statistics.
03
Closing an error out
Mark it resolved, assign it, or set it to resolve on the next deploy — only the fields you pass change.
04
Asking a question the fault list cannot answer
Read the BadgerQL reference, then run the query against Insights data.
05
Building an alarm that will not misfire
Fetch the alarms, queries and badgerql topics first, then create the alarm with its trigger_config.
06
Checking whether a scheduled job ran
List the project's check-ins and read the one you are asking about.
07
Watching error volume over time
Pull occurrence counts grouped by hour, day, week or month, filtered to an environment.
08
Putting a view together for the team
List the dashboards that exist, read the widget schema from the reference, then create one.
34 tools
Listed in project docs. Your client may show a different list.
list_projectsget_projectcreate_projectupdate_projectdelete_projectget_project_occurrence_countsget_project_integrationsget_project_reportlist_faultsget_faultupdate_faultget_fault_countslist_fault_noticeslist_fault_affected_usersquery_insightslist_streamslist_dashboardsget_dashboardcreate_dashboardupdate_dashboarddelete_dashboardlist_alarmsget_alarmcreate_alarmupdate_alarmdelete_alarmget_alarm_historylist_check_insget_check_increate_check_inupdate_check_indelete_check_insearch_toolsBEFORE YOU INSTALL
What to know first
Tools you get
34 tools named in the project's documentation.
Requires
- docker on PATH
- HONEYBADGER_PERSONAL_AUTH_TOKEN in your environment
Where it runs
All 6 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
docker pull ghcr.io/honeybadger-io/honeybadger-mcp-server:latestMCP Clients
Cursor, Windsurf, Claude Desktop
JSON
{
"mcpServers": {
"honeybadger": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HONEYBADGER_PERSONAL_AUTH_TOKEN",
"ghcr.io/honeybadger-io/honeybadger-mcp-server"
],
"env": {
"HONEYBADGER_PERSONAL_AUTH_TOKEN": "<YOUR_HONEYBADGER_PERSONAL_AUTH_TOKEN>"
}
}
}
}Claude Code
Run this; <YOUR_HONEYBADGER_PERSONAL_AUTH_TOKEN> is the personal auth token from the Authentication tab of your Honeybadger user settings (https://app.honeybadger.io/users/edit#authentication).
CLAUDE CODE · TERMINAL
claude mcp add honeybadger -- docker run -i --rm -e HONEYBADGER_PERSONAL_AUTH_TOKEN="<YOUR_HONEYBADGER_PERSONAL_AUTH_TOKEN>" ghcr.io/honeybadger-io/honeybadger-mcp-server:latestVS Code
VS CODE · JSON
{
"inputs": [
{
"type": "promptString",
"id": "honeybadger_auth_token",
"description": "Honeybadger Personal Auth Token",
"password": true
}
],
"servers": {
"honeybadger": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HONEYBADGER_PERSONAL_AUTH_TOKEN",
"ghcr.io/honeybadger-io/honeybadger-mcp-server"
],
"env": {
"HONEYBADGER_PERSONAL_AUTH_TOKEN": "${input:honeybadger_auth_token}"
}
}
}
}Zed
ZED · JSON
{
"context_servers": {
"honeybadger": {
"command": {
"path": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HONEYBADGER_PERSONAL_AUTH_TOKEN",
"ghcr.io/honeybadger-io/honeybadger-mcp-server"
],
"env": {
"HONEYBADGER_PERSONAL_AUTH_TOKEN": "<YOUR_HONEYBADGER_PERSONAL_AUTH_TOKEN>"
}
},
"settings": {}
}
}
}
