Hny MCP Server

Model Context Protocol server for Honeycomb. Exposed over MCP by the hny mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol server for interacting with Honeycomb observability data. This server enables LLMs like Claude to directly analyze and query your Honeycomb datasets across multiple environments.

• Query Honeycomb datasets across multiple environments
• Run analytics queries with support for:
• Multiple calculation types (COUNT, AVG, P95, etc.)
• Breakdowns and filters
• Time-based analysis
• Monitor SLOs and their status (Enterprise only)

Its toolset

Everything the assistant can do here goes through one of these:

• list_datasets — List all datasets in an environment
• get_columns — Get column information for a dataset
• run_query — Run analytics queries with rich options
• analyze_columns — Analyzes specific columns in a dataset by running statistical queries and returning computed metrics
• list_slos — List all SLOs for a dataset
• get_slo — Get detailed SLO information
• list_triggers — List all triggers for a dataset
• get_trigger — Get detailed trigger information
• get_trace_link — Generate a deep link to a specific trace in the Honeycomb UI
• get_instrumentation_help — Provides OpenTelemetry instrumentation guidance
• Resources — Access Honeycomb datasets using URIs in the format: honeycomb://{environment}/{dataset}
• Tools — The Tools tool exposed by this server

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 3 environment variables: HONEYCOMB_API_KEY, HONEYCOMB_ENV_PROD_API_KEY, HONEYCOMB_ENV_STAGING_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ - Honeycomb API key with full permissions: - Query access for analytics - Read access for SLOs and Triggers - Environment-level access for dataset operations Honeycomb MCP is effectively a complete alternative interface to Honeycomb, and thus you need broad permissions for the API.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Hny MCP's toolset — list_datasets, get_columns, run_query and 9 more — is a fair guide to whether it matches your workflow. It is maintained by austinlparker; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Hny MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the hny mcp mcp server does with a few real requests.