honeybadger-mcp-server
Honeybadger MCP server providing an MCP interface (via stdio/docker) to access Honeybadger API data and actions such as projects, faults, notices, and insights. Defaults to read-only mode to prevent write/destructive operations unless explicitly enabled.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The server is configured to run in read-only mode by default, reducing accidental write/destructive operations. Authentication relies on a personal auth token provided via environment variables; the README emphasizes caution for enabling write mode. The content provided does not state TLS/transport guarantees, token scope granularity, or how secrets are logged/redacted, nor does it document rate limiting or specific error safety behaviors.
⚡ Reliability
Best When
You want MCP tool-based access to Honeybadger data for an agent-driven debugging/triage or reporting workflow, and you keep the server in default read-only mode.
Avoid When
You need guaranteed safety for destructive actions, or you cannot securely handle environment-variable secrets and client configuration.
Use Cases
- • Letting an AI assistant query Honeybadger faults and project details via MCP tools
- • Generating operational summaries from Honeybadger reports and insights (e.g., occurrences, counts)
- • Assisting incident triage workflows by searching faults and retrieving related notices/users
- • Automating (optionally) project configuration changes in Honeybadger via MCP tools when write mode is enabled
Not For
- • Running without protecting a Honeybadger personal auth token (token still grants API access)
- • High-safety production write automation unless you tightly control and monitor token usage
- • Use as a general Honeybadger API proxy without understanding MCP client configuration
- • Workloads requiring explicit retry/idempotency guarantees beyond what Honeybadger/MCP semantics provide
Interface
Authentication
Authentication is a Honeybadger personal auth token passed to the container/server. The README does not describe OAuth flows or fine-grained scopes for this MCP wrapper.
Pricing
No pricing information for the MCP server itself is provided in the provided content. Honeybadger subscription/usage costs would still apply for API calls.
Agent Metadata
Known Gotchas
- ⚠ Default read-only mode may block create/update/delete tools until explicitly set to read-only=false.
- ⚠ Write/delete tools can be destructive; ensure the MCP client and token access are tightly controlled.
- ⚠ Pagination for some endpoints is via limit/page parameters; agents may need to loop to retrieve full datasets.
- ⚠ Secrets are provided through environment variables or MCP client password/inputs; misconfiguration could leak tokens.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for honeybadger-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.