Connect Honeycomb to Andromity with the Honeycomb MCP server

Honeycomb hosts an official MCP server at https://mcp.honeycomb.io/mcp. With it, Andromity can run queries against your datasets, fetch traces and look up columns while it investigates a slow or failing code path.

Honeycomb prefers OAuth, so connecting is one browser sign-in. Your team needs Honeycomb Intelligence enabled.

What the agent can do with Honeycomb

• Run queries and look up dataset columns (find_columns, get_dataset_columns).
• Fetch traces.
• Search OpenTelemetry semantic conventions (search_semconv).
• Start Canvas investigations.
• Create and update Boards (create_board, update_board).
• Create and update Triggers, SLOs and notification recipients when write access is granted.

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Honeycomb MCP server”.

• Query Honeycomb for the slowest spans in the checkout service in the last hour and find the function in this repo that creates them.
• Fetch the trace for the failing request ID in this bug report and explain where the time went.
• Check which attribute names Honeycomb has for the payments dataset and make sure our instrumentation in this repo uses the same names.
• Create a Honeycomb board with the latency and error queries we just wrote.

Connect Honeycomb

1. Confirm your Honeycomb team has Honeycomb Intelligence enabled.
2. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Honeycomb and select Connect.
3. Sign in to Honeycomb in your browser and approve the connection. Grant the write scope only if you want the agent to create or update resources.
4. Andromity saves Honeycomb to ~/.andromity/mcp.json and connects it.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

• Read access is required for all MCP operations. Tools that create or update Boards, Triggers, SLOs, notification recipients and Canvas investigations need the mcp:write scope, which you grant explicitly.
• Honeycomb documents an X-MCP-Toolset header (all, query or canvas) to limit which tools load. It does not grant access; your scopes and plan still apply. Set it by hand in mcp.json.
• The Activity Log Environment is exposed through MCP only to Team Owners.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

• Honeycomb Intelligence must be enabled for your team.
• EU teams use https://mcp.eu1.honeycomb.io/mcp. Add it by hand in mcp.json if your team is in the EU.
• Honeycomb recommends API keys only for unattended agents, and only team owners can create them.

Questions

Does Honeycomb have an official MCP server?

Yes. Honeycomb hosts it at https://mcp.honeycomb.io/mcp and documents it in its docs.

Is there an EU URL for Honeycomb MCP?

Yes. Honeycomb lists https://mcp.eu1.honeycomb.io/mcp for EU teams.

Can the agent change my Honeycomb data?

Only if you grant the write scope. Without mcp:write, tools that create or update resources are not available.

Sources

This guide is based on Honeycomb’s own documentation. The app controls its server, so tools can change; check the source for the current list.

• Honeycomb MCP
• Honeycomb MCP configuration guide

Honeycomb is a trademark of its owner. Andromity is not affiliated with or endorsed by Honeycomb.