
Honeycomb MCP Server
OfficialHoneycomb observability via AI: query datasets, alerts and boards (community + official).
Add to your client
Copy the config for your MCP client and paste it into its config file.
npx -y @kajirita2002/honeycomb-mcp-serverPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"honeycomb-mcp-server": {
"command": "npx",
"args": [
"-y",
"@kajirita2002/honeycomb-mcp-server"
],
"env": {
"HONEYCOMB_API_KEY": "<your-honeycomb-api-key>"
}
}
}
}Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
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
Honeycomb MCP Server lets AI assistants explore your Honeycomb observability data — running queries over datasets, inspecting schema/columns, and reading SLOs and Triggers. It is maintained by Honeycomb itself, so the tool surface maps directly onto Honeycomb's query and alerting model.
Important: this self-hosted, stdio-based server is deprecated. Honeycomb now points users to its hosted MCP solution; new users should generally start there. The repo remains useful as a reference and for self-hosted setups, and it requires a Honeycomb Enterprise subscription.
It is a single Node process you build locally (pnpm) and connect over stdio. It supports one or many environments via per-environment API keys, an EU endpoint override, and a configurable response cache to keep schema/SLO lookups fast.
Tools & capabilities (10)
list_datasetsList datasets in an environment
get_columnsGet a dataset's columns/schema
run_queryRun an analytics query against a dataset
analyze_columnsAnalyze columns to understand cardinality/usage
list_slosList Service Level Objectives
get_sloGet details for a specific SLO
list_triggersList Triggers (alerts)
get_triggerGet details for a specific Trigger
get_trace_linkBuild a deep link to a trace in the Honeycomb UI
get_instrumentation_helpReturn guidance on instrumenting code for Honeycomb
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
- 1Confirm you are on Honeycomb Enterprise (required) — and consider the hosted MCP, since this self-hosted server is deprecated
- 2Clone the repo and run `pnpm install` then `pnpm run build`
- 3Create a Honeycomb API key with query + SLO/Trigger read and environment access
- 4Set HONEYCOMB_API_KEY (or per-env HONEYCOMB_ENV_<NAME>_API_KEY); EU users set HONEYCOMB_API_ENDPOINT
- 5Add the built server to your MCP client config over stdio and restart the client
- 6Verify by asking the agent to call list_datasets and run_query
Security notes
The official self-hosted server requires Honeycomb Enterprise and is being deprecated toward a hosted MCP, so check entitlement before relying on it. API keys grant read access to all events in their environment, so scope keys per-environment and avoid management keys.
Honeycomb MCP Server FAQ
Is this server still maintained?
It is officially deprecated. Honeycomb recommends migrating to its hosted MCP solution; this self-hosted stdio server remains as a reference.
Do I need a paid plan?
Yes — the documentation states a Honeycomb Enterprise subscription is required to use the MCP server.
What permissions does the API key need?
Full permissions: query access for analytics, read access for SLOs and Triggers, and environment-level access for dataset operations.
How do I connect multiple Honeycomb environments?
Use per-environment variables like HONEYCOMB_ENV_PROD_API_KEY and HONEYCOMB_ENV_STAGING_API_KEY instead of a single HONEYCOMB_API_KEY.
I'm on the EU instance — what changes?
Set HONEYCOMB_API_ENDPOINT to https://api.eu1.honeycomb.io/ so requests hit the EU API.
Alternatives to Honeycomb MCP Server
Compare all alternatives →Official Elastic server: list indices, read mappings, and search with Query DSL.
Official PostHog server: product analytics, feature flags, experiments, error tracking and SQL.
Run PromQL queries and analyze Prometheus metrics from any MCP client.
Compare Honeycomb MCP Server with: