# Honeycomb MCP server

> Query Honeycomb traces, events, metrics, SLOs, triggers and boards to investigate production issues from your AI assistant.

- Listing: https://mcp.tc/i/honeycomb
- Connect: use the server's own URL `https://mcp.honeycomb.io/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Observability & Incidents](https://mcp.tc/c/observability)
- Vendor: Honeycomb
- Homepage: <https://docs.honeycomb.io/integrations/mcp>

## About

Connects an AI assistant to Honeycomb observability data. Agents can run queries against telemetry, explore traces, and work with SLOs, triggers and boards. Honeycomb's docs describe uses such as investigating latency or error spikes, finding performance outliers, and translating existing dashboards and alerts into Honeycomb queries.

Runs as a hosted streamable HTTP endpoint at https://mcp.honeycomb.io/mcp. Users sign in with OAuth through Honeycomb, with mcp:read and mcp:write scopes. No local install is needed.

## What it can do

- Query traces, events and metrics in Honeycomb
- Investigate latency and error spikes
- Find performance outliers
- Work with SLOs and triggers
- Create and read boards to capture findings
- Translate existing dashboards and alerts into Honeycomb queries

## Example prompts

- "Why did p99 latency spike on the checkout service in the last hour?"
- "Show the slowest traces for the payments service today"
- "Which SLOs are burning budget fastest right now?"
- "Create a board with the queries we used to investigate this error spike"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http honeycomb https://mcp.honeycomb.io/mcp
```

2. Start Claude Code, type `/mcp`, pick **honeycomb** and choose **Authenticate**. A browser window opens for the Honeycomb sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Honeycomb** and paste this URL:

```url
https://mcp.honeycomb.io/mcp
```

3. Click **Add**, then **Connect**, and sign in when Honeycomb asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Honeycomb&connectorUrl=https%3A%2F%2Fmcp.honeycomb.io%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.honeycomb.io/mcp` and click **Add**.

3. Click **Connect** and sign in when Honeycomb asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.honeycomb.io/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Honeycomb to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=honeycomb&config=eyJ1cmwiOiJodHRwczovL21jcC5ob25leWNvbWIuaW8vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "honeycomb": {
      "url": "https://mcp.honeycomb.io/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=honeycomb&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.honeycomb.io%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"honeycomb","type":"http","url":"https://mcp.honeycomb.io/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "honeycomb": {
      "type": "http",
      "url": "https://mcp.honeycomb.io/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "honeycomb": {
      "serverUrl": "https://mcp.honeycomb.io/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add honeycomb --url https://mcp.honeycomb.io/mcp
codex mcp login honeycomb
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.honeycomb]
url = "https://mcp.honeycomb.io/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http honeycomb https://mcp.honeycomb.io/mcp
```

Then, inside Gemini CLI, run `/mcp auth honeycomb` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "honeycomb": {
      "type": "http",
      "url": "https://mcp.honeycomb.io/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.honeycomb.io/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/honeycomb (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report