OBSERVABILITY / Honeycomb
Honeycomb MCP
Explore production telemetry and save investigations in Honeycomb, with additional write scope for operational changes.
“It lets AI agents query, explore, and iterate on telemetry data just like you do in our UI.”
01 / THE REASONING
Why this made the selection.
- Telemetry queries and investigation tools support iterative diagnosis from an agent.
- Explicit write scope separates basic reads from changes to Boards, Triggers, SLOs and other resources.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Honeycomb MCP overview, configuration guide and tool reference.
Our findings
- Most tools are read-only, but the server is not universally read-only.
- OAuth is the preferred interactive setup. Management API keys are an alternative for unattended clients, with explicit MCP and environment scopes.
Not established by this review
- Server launch, authenticated tool calls, and release-to-source parity were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
claude mcp add honeycomb --transport http https://mcp.honeycomb.io/mcpCopying does not execute this command. It may retrieve a newer version than the reviewed source.
- For a US account in Claude Code, use the command below; use the EU endpoint from the official setup guide for EU data.
- Finish OAuth and review requested read/write scopes.
- Use the client-specific configuration format; the JSON example is the documented Cursor shape for the US endpoint.
Before you start
- Honeycomb team access and telemetry data.
- An OAuth-capable client, or a suitably scoped management API key for unattended access.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"honeycomb": {
"url": "https://mcp.honeycomb.io/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.honeycomb.io/integrations/mcp/
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
https://docs.honeycomb.io/integrations/mcp/configuration-guide
Supports: install, access, compatibility, transports, review
https://docs.honeycomb.io/integrations/mcp/tools
Supports: whySelected, limitations, access, review