Honeycomb MCP server

OfficialHoneycombConfig last verified Jun 1, 2026

Honeycomb's official MCP server: query traces, metrics, and logs, run BubbleUp, and manage Boards, Triggers, and SLOs from your agent.

The Honeycomb MCP server is Honeycomb's official integration that connects a coding agent to your observability data so it can investigate production behavior and cross-reference it with the codebase. Instead of bouncing between the Honeycomb UI and your editor, the agent can discover environments and datasets, write and run time-series queries with calculations and breakdowns, fetch saved or historical query results, and run BubbleUp to surface the dimensions that explain an anomaly. It reaches into traces and spans (rendering a trace as a waterfall, listing span names, drilling into span attributes), maps service-to-service dependencies, reviews active anomaly profiles, and even reads recent AI-agent conversation telemetry. A set of write tools lets it create and update Boards, Triggers, SLOs, and notification recipients, and invoke Canvas investigations for collaborative root-cause work.

The canonical deployment is the hosted remote endpoint at https://mcp.honeycomb.io/mcp (with an EU endpoint at https://mcp.eu1.honeycomb.io/mcp), authenticated via OAuth 2.1 so teams can onboard through the browser with no long-lived tokens on disk; an API-key option exists for headless agents. The previously published self-hosted server is deprecated in favor of the hosted endpoint. Read tools work with read scopes; the write tools (Boards, Triggers, SLOs, recipients, Canvas) require the corresponding write scopes.

Quick install

Copy-paste configs are provided for all 8 supported clients. Pick your client below.

Add to ~/.claude.json

~/.claude.json
json
{
  "mcpServers": {
    "honeycomb": {
      "type": "http",
      "url": "https://mcp.honeycomb.io/mcp"
    }
  }
}
Or via CLI
bash
claude mcp add --transport http honeycomb https://mcp.honeycomb.io/mcp

Heads up

  • First tool call opens a browser to authorize.

Available tools

ToolDescription
get_workspace_contextProvides team name, current time, and the environment list with dataset counts.
get_environmentReturns details for a single environment, including its datasets and calculated fields.
get_datasetRetrieves metadata and the full column schema for a dataset.
get_dataset_columnsReturns the column schema, with optional sample values for specific columns.
run_queryExecutes time-series aggregation queries with support for calculations and breakdowns.
get_query_resultsFetches results from a previously executed query by URL or ID.
find_queriesSearches query history and saved queries by intent.
find_columnsLocates columns and calculated fields using natural-language keywords.
run_bubbleupRuns BubbleUp analysis to identify statistically significant differences in query results.
get_traceRetrieves all spans for a trace ID and renders them as a waterfall.
list_spansLists span names ranked by count, with trace-root frequency.
get_span_detailsReturns attribute summaries and common values for specific span names.
get_service_mapShows service-to-service call dependencies for a time range.
get_anomaly_service_profilesReturns active anomaly-detection profiles for the team.
search_semconvSearches the semantic convention registry for matching attributes.
get_semconv_attributeReturns the full definitions of semantic convention attributes.
list_semconv_namespacesLists top-level semantic convention namespaces.
list_boardsLists Boards in an environment or shows the full contents of a Board.
create_boardCreates a Board with query, SLO, and text panels.
update_boardModifies an existing Board with panel changes and filter updates.
get_triggersLists Triggers or shows the detailed configuration for a single Trigger.
create_triggerCreates a Trigger that fires alerts when a query threshold is crossed.
update_triggerModifies an existing Trigger configuration.
get_slosLists SLOs or returns the detailed status and graphs for a specific SLO.
create_sloCreates an SLO with an auto-created Service Level Indicator derived column.
update_sloModifies an existing SLO configuration.
list_recipientsLists pre-registered notification destinations with their IDs.
create_recipientCreates a new notification recipient for Triggers and SLO burn alerts.
canvas_agent_invokeSends a message to a Canvas agent for a collaborative investigation.
canvas_agent_poll_responsePolls for results from a previously issued Canvas agent call.
list_aiconversationsLists recent AI-agent conversations with telemetry summaries.
get_aiconversationReturns the full event timeline for a single AI conversation.
refinery_docsReads Honeycomb Refinery documentation for configuration questions.
feedbackSubmits feedback about the Honeycomb MCP server experience.

Required configuration

  • HONEYCOMB_API_KEYOptional

    Honeycomb API key for headless/unattended agents. Not needed when using OAuth on the remote endpoint.

What you can do with it

Investigate a production spike without leaving the editor

The agent writes a query, runs BubbleUp to find the dimensions that explain an anomaly, then pulls the relevant trace waterfall and span attributes to point at the offending code path.

Manage observability config from the agent

Create or update Boards, Triggers, and SLOs and wire up notification recipients directly, so a new service ships with dashboards and alerting in the same session it was built.

FAQ

Is it free?
The MCP server itself is free and open source; you need a Honeycomb account, and usage of the underlying platform is governed by your Honeycomb plan. Querying enterprise data and the richer write tools follow your account's entitlements and scopes.
Does it support remote/OAuth?
Yes. The canonical deployment is the hosted remote endpoint at https://mcp.honeycomb.io/mcp (EU: https://mcp.eu1.honeycomb.io/mcp) using OAuth 2.1, so members onboard through the browser with no long-lived tokens on disk. An API-key option is available for headless agents, and the older self-hosted server is deprecated.
Can the agent change my dashboards and alerts?
Only with write scopes. Read tools work with read access; the write tools for Boards, Triggers, SLOs, recipients, and Canvas investigations require the corresponding write scopes, so you can grant a read-only token to keep an agent observational.
← Browse all monitoring-observability servers