Honeycomb MCP Server

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "honeycomb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@kajirita2002/honeycomb-mcp-server"
      ],
      "env": {
        "HONEYCOMB_API_KEY": "<your-honeycomb-api-key>"
      }
    }
  }
}

Before you start

• Node.js 18 or higher
• A Honeycomb Enterprise subscription (required)
• A Honeycomb API key with full permissions: query access for analytics, read access for SLOs and Triggers, and environment-level access for dataset operations — created in Honeycomb's environment settings
• pnpm to install and build the server locally
• EU customers must set HONEYCOMB_API_ENDPOINT to https://api.eu1.honeycomb.io/

About Honeycomb MCP Server

Tools & capabilities (10)

When to use it

• Use it when you want an agent to run Honeycomb analytics queries and summarize results in chat
• Use it when investigating an incident and you need to inspect dataset columns and high-cardinality fields
• Use it when you want to check SLO burn or budget status without opening the Honeycomb UI
• Use it when reviewing Triggers/alerts and their configuration from an assistant
• Use it when you need a direct deep link to a specific trace to share or open
• Use it when asking for instrumentation guidance while adding OpenTelemetry spans

Quick setup

1. 1Confirm you are on Honeycomb Enterprise (required) — and consider the hosted MCP, since this self-hosted server is deprecated
2. 2Clone the repo and run `pnpm install` then `pnpm run build`
3. 3Create a Honeycomb API key with query + SLO/Trigger read and environment access
4. 4Set HONEYCOMB_API_KEY (or per-env HONEYCOMB_ENV_<NAME>_API_KEY); EU users set HONEYCOMB_API_ENDPOINT
5. 5Add the built server to your MCP client config over stdio and restart the client
6. 6Verify by asking the agent to call list_datasets and run_query

Honeycomb MCP Server FAQ