Honeycomb
MCPHoneycomb is built for asking questions of high-cardinality telemetry, which is exactly what an investigation needs. Antimetal queries your datasets, traces, and triggers through Honeycomb's MCP server using a read-only Management API key.
#What Antimetal does with Honeycomb
- Run queries against your datasets to isolate the affected slice of traffic
- Analyze columns to find the dimension that separates failing requests from healthy ones
- Follow distributed traces to the span where latency or errors originate
- Read triggers to see which conditions your team alerts on
#Connecting Honeycomb
Prerequisites
- A Honeycomb team with Honeycomb Intelligence enabled
- Team owner permission, which is required to create a Management API key
-
Open API key settings
Log in to Honeycomb and go to Account > Team Settings > API Keys.
-
Create a Management API key
Click Create Management API Key and name it
Antimetal. -
Grant read scopes
Select the Model Context Protocol and Environments scopes, and grant Read on both. No write scopes are needed.
-
Copy the Key ID and Key Secret
Copy both values. The secret is shown only once — save it securely.
-
Share the key with Antimetal
Provide the key in
KEY_ID:KEY_SECRETformat. Antimetal selects the US (mcp.honeycomb.io) or EU (mcp.eu1.honeycomb.io) endpoint automatically based on your account.
#Permissions and access
Antimetal uses a read-only Management API key scoped to Model Context Protocol and Environments. It is restricted to listing and reading datasets, running queries, and analyzing columns. No write operations are performed.
All tenant data is processed in isolated environments. See security and compliance for details.
Contact us via Slack or at support@antimetal.com.
Related integrations
Correlate metrics, logs, and traces.
Dashboards, alerting, Prometheus, Loki, OnCall, and incidents.
Track application errors to their source.