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.
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.
- 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
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.
One command plus a key — docker pull ghcr.io/honeybadger-io/honeybadger-mcp-server:latest, then supply credentials