Honeycomb MCP Server
Connect AI agents to Honeycomb observability — query traces, triggers, and SLOs via MCP.
Updated
What is Honeycomb MCP?
The Honeycomb MCP server is a Model Context Protocol server that gives AI agents direct, secure access to your Honeycomb observability data — traces, events, queries, triggers, and SLOs — so they can investigate production behavior in natural language.
It is a vendor-hosted remote server reachable at https://mcp.honeycomb.io/mcp (with an EU endpoint at https://mcp.eu1.honeycomb.io/mcp). Connection uses OAuth: you point an MCP client at the URL, authorize in your browser, and pick an environment and access level — there are no API keys to copy or share. Honeycomb has deprecated its earlier self-hosted MCP server in favor of this hosted option.
Once connected, agents in tools like Claude Code, Cursor, VS Code, and Claude Desktop can list datasets and columns, run queries, inspect traces, and check triggers and SLOs — cross-referencing production signals with the code you're working on. Access requires a Honeycomb team with Honeycomb Intelligence enabled.
Connect the Honeycomb MCP server
Claude Code
- 1
Add the hosted server
Run: claude mcp add honeycomb --transport http https://mcp.honeycomb.io/mcp (EU: use https://mcp.eu1.honeycomb.io/mcp).
- 2
Authorize via OAuth
Run /mcp in Claude Code to trigger authentication, then complete the browser OAuth flow.
- 3
Pick environment and access
Select your Honeycomb environment and choose read-only access when prompted. Requires Honeycomb Intelligence enabled.
Cursor
- 1
Open MCP settings
In Cursor, add a new MCP server using HTTP transport with the URL https://mcp.honeycomb.io/mcp (EU: https://mcp.eu1.honeycomb.io/mcp). The /honeycomb-setup command can guide this interactively.
- 2
Authorize via OAuth
Trigger the connection and complete the browser OAuth flow — no API keys required.
- 3
Select environment
Choose your Honeycomb environment and access level. Requires Honeycomb Intelligence enabled.
Sample use cases
An on-call agent triggered by an alert pulls the relevant traces and SLO status from Honeycomb to summarize what changed.
Faster incident triage with production context surfaced automatically.
A scheduled workflow queries recent latency and error-rate trends across an environment.
Regular observability digests without manually building queries.
A developer in their IDE cross-references production behavior with the code they're editing.
Code changes informed by real trace and event data.
Security & permissions
Authentication is OAuth — you authorize the connection in your browser instead of sharing API keys. During setup you select which Honeycomb environment the agent can access and can choose read-only access, scoping what data (datasets, queries, traces, triggers, SLOs) the agent can see. Because it is vendor-hosted, requests go to Honeycomb's mcp.honeycomb.io endpoint (or the EU mcp.eu1.honeycomb.io); grant only the environment and access level the workflow needs.
Using Honeycomb MCP with Gamut
In Gamut, you connect Honeycomb once and Gamut manages the OAuth connection so an agent can call the Honeycomb MCP server inside automated, event- or schedule-triggered workflows — for example, a scheduled run that queries recent error-rate or latency trends, or an alert-triggered agent that pulls the relevant traces and SLO status to summarize what changed in production. The agent only reads and analyzes the observability data the connection is authorized for; it does not replace Honeycomb's own alerting or triggers.
Frequently asked questions
What is the Honeycomb MCP server?
It is a Model Context Protocol server hosted by Honeycomb that lets AI agents query your observability data — traces, events, queries, triggers, and SLOs — in natural language. You connect at https://mcp.honeycomb.io/mcp and authorize via OAuth.
Is the Honeycomb MCP server free?
There is no separate MCP fee, but it requires a Honeycomb team with Honeycomb Intelligence enabled. The older self-hosted server was Enterprise-only and is now deprecated in favor of the hosted version.
How do I connect the Honeycomb MCP server to Claude Code or Cursor?
For Claude Code, run claude mcp add honeycomb --transport http https://mcp.honeycomb.io/mcp, then run /mcp and complete the browser OAuth flow. In Cursor, add an HTTP MCP server with the same URL (or use /honeycomb-setup) and authorize via OAuth.
Is the Honeycomb MCP server hosted or self-hosted?
It is hosted by Honeycomb at mcp.honeycomb.io (with an EU endpoint at mcp.eu1.honeycomb.io). Honeycomb's earlier self-hosted MCP server has been deprecated, and they recommend migrating to the hosted server.