--- title: "Honeycomb MCP: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/honeycomb/ description: "Explore production telemetry and save investigations in Honeycomb, with additional write scope for operational changes." --- # Honeycomb MCP: review, setup & limitations · Undominated.ai > Explore production telemetry and save investigations in Honeycomb, with additional write scope for operational changes. [← Explore all mcp servers](/mcp-servers/) OBSERVABILITY / Honeycomb # Honeycomb MCP Explore production telemetry and save investigations in Honeycomb, with additional write scope for operational changes. See setup guidance ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 3 linked sources Publisher Honeycomb Licence Not established Read what was—and wasn’t—checked ↓ “It lets AI agents query, explore, and iterate on telemetry data just like you do in our UI.” Honeycomb · upstream description ↗ Our analysis follows below. 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. ### A good fit for - Investigate unexpected latency or failures in Honeycomb. - Capture an approved investigation on a shared Board. ### Weigh up before choosing - Read access exposes telemetry to the connected client. - Write tools require mcp:write; enabling that scope allows changes to alerting and investigation resources. - The endpoint must match the US or EU region, and some environment access is role-restricted. 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. Upstream setup instructions ↗ DOCUMENTED COMMAND claude mcp add honeycomb --transport http https://mcp.honeycomb.io/mcp Copy command ↗ Copying 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" } } } Copy configuration ↗ ### Compatibility Claude Code · Claude Desktop · Cursor · VS Code ### Transports HTTP ### Remote OAuth or scoped API key - Queries telemetry and returns investigation results. - With explicit write scope, creates/updates Boards, Triggers, SLOs, notification recipients and Canvas investigations. ### Cost model Honeycomb plan and telemetry usage apply; the connected AI client is billed separately. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Honeycomb MCP setup and scope ↗ Checked 2026-09-21 https://docs.honeycomb.io/integrations/mcp/ Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review - Honeycomb regional setup and authorization ↗ Checked 2026-09-21 https://docs.honeycomb.io/integrations/mcp/configuration-guide Supports: install, access, compatibility, transports, review - Honeycomb tool scope reference ↗ Checked 2026-09-21 https://docs.honeycomb.io/integrations/mcp/tools Supports: whySelected, limitations, access, review KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Datadog MCP ↗ Query Datadog telemetry and operate permitted monitoring resources from an authenticated AI client.](/mcp-servers/datadog/)[### Grafana MCP Server ↗ Connects dashboards, logs, metrics and related Grafana data sources to an assistant, with separate controls for writes and query execution.](/mcp-servers/grafana/)[### Langfuse data MCP ↗ Inspect Langfuse observations, prompts and evaluation data, and manage supported project resources through its native MCP endpoint.](/mcp-servers/langfuse/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)