Honeycomb MCP server

What the model can do

Honeycomb observability for one environment: datasets and when they last received data, triggers and which are firing, SLOs, boards and deploy or incident markers. Can add, change or delete a marker, save and run a query (Enterprise) and name it, create a board or an SLO, and delete a trigger or an SLO.

Reads

• honeycomb_list_datasetsHoneycomb datasets in the connected environment: slug (used by the other tools), name, description…
• honeycomb_list_triggersHoneycomb triggers (alerts) and which are firing now: name, dataset, threshold, how often checked, firing and disabled state…
• honeycomb_list_slosHoneycomb SLOs: name, description, target, time window, the SLI column and datasets.
• honeycomb_list_boardsHoneycomb boards in the environment (secret boards excepted): name, description, how many panels and a link to open it.
• honeycomb_list_markersHoneycomb markers (deploys, incidents, notes drawn on graphs), newest first: message, type, start and end, link.

Acts, when you ask

These change something in Honeycomb. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• honeycomb_create_markerAdds a marker to Honeycomb graphs, for a deploy, an incident or anything worth seeing against the data.
• honeycomb_update_markerChanges a Honeycomb marker's message, type, link, start or end.
• honeycomb_delete_markerPermanently deletes a Honeycomb marker from the graphs.
• honeycomb_create_querySaves a Honeycomb query specification on a dataset (or __all__): calculations (COUNT by default), breakdowns, filters, order…
• honeycomb_run_queryRuns a saved Honeycomb query (from honeycomb_create_query) and returns its result rows, the link to the result and optionally the time series.
• honeycomb_name_queryNames and describes a saved Honeycomb query (a query annotation), so it shows in the query library and can go on a board.
• honeycomb_create_boardCreates an empty Honeycomb board (a flexible board) with a name and description, visible to the team in this environment…
• honeycomb_create_sloCreates a Honeycomb SLO on a dataset: a name, a target (for example 99.9 percent) over a window of days, and the SLI…
• honeycomb_delete_triggerPermanently deletes a Honeycomb trigger: its alerts stop and its recipients are not told.
• honeycomb_delete_sloPermanently deletes a Honeycomb SLO; its burn alerts stop.

Connect it

First connect Honeycomb on Dashboard → Connections, then add Memtro to your client once. The Honeycomb tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Honeycomb connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which Honeycomb triggers are firing right now?
• › When did we last deploy the checkout service?
• › Has any dataset stopped receiving data today?
• › Add a deploy marker for release 4.12 to the api dataset
• › Count errors by endpoint on the api dataset over the last 2 hours

Questions

Is this an official Honeycomb MCP server?

No. It is Memtro's MCP server with Memtro's Honeycomb connector behind it: the connector reads Honeycomb through its API with the credentials you connect on Dashboard → Connections, and Honeycomb publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Honeycomb?

Only when you ask, and only what it has been granted: add a marker (a deploy, incident or note) to an environment's or a dataset's graphs; change a marker's message, type, link or times; delete a marker; save a query specification; run a saved query and read its results; name and describe a saved query; create a board; create an SLO; permanently delete a trigger; permanently delete an SLO. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server