Honeycomb

by honeycombio

16 stars

334 downloads

Not rated

GitHub

About

Integrates with the Honeycomb API to enable direct querying and analysis of observability data for automated performance monitoring and troubleshooting.

Details

Author: honeycombio
Repository: honeycombio/honeycomb-mcp
GitHub stars: 16
Downloads: 334
License: MIT License
Categories: Cloud Service, Infrastructure, Other, AI, Design, Developer Tools, Search, API, Automation
Tags: #analytics

- 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)
- Analyze columns and data patterns
- View and analyze Triggers
- Access dataset metadata and schema information
- Optimized performance with TTL-based caching for all non-query API calls

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below
Plugin Name Honeycomb

Command (node, npx, python, etc.) node
Arguments
- Argument 1 /fully/qualified/path/to/honeycomb-mcp/build/index.mjs
Environment
- HONEYCOMB_API_KEY your_api_key
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/c",
                "node",
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/c",
                "node",
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/c",
                "node",
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/c",
                "node",
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/c",
                "node",
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

From the repository

To use this MCP server, you need to provide Honeycomb API keys via environment variables in your MCP config.

{
    "mcpServers": {
      "honeycomb": {
        "command": "node",
        "args": [
          "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
        ],
        "env": {
          "HONEYCOMB_API_KEY": "your_api_key"
        }
      }
    }
}

For multiple environments:

{
    "mcpServers": {
      "honeycomb": {
        "command": "node",
        "args": [
          "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
        ],
        "env": {
          "HONEYCOMB_ENV_PROD_API_KEY": "your_prod_api_key",
          "HONEYCOMB_ENV_STAGING_API_KEY": "your_staging_api_key"
        }
      }
    }
}

Important: These environment variables must bet set in the env block of your MCP config.

EU customers must also set a HONEYCOMB_API_ENDPOINT configuration, since the MCP defaults to the non-EU instance.

The MCP server implements caching for all non-query Honeycomb API calls to improve performance and reduce API usage. Caching can be configured using these environment variables:

bash

`list_datasets`

List all datasets in a specified environment. Parameters: environment (string)

`get_columns`

Get column information for a specified dataset in a specified environment. Parameters: environment (string), dataset (string)

`run_query`

Run analytics queries with rich options for a specified dataset in a specified environment. Parameters: environment (string), dataset (string), calculations (array), breakdowns (array), time_range (integer)

`analyze_columns`

Analyzes specific columns in a dataset by running statistical queries and returning computed metrics.

`list_slos`

List all SLOs for a specified dataset in a specified environment. Parameters: environment (string), dataset (string)

`get_slo`

Get detailed SLO information for a specified dataset in a specified environment. Parameters: environment (string), dataset (string), sloId (string)

`list_triggers`

List all triggers for a specified dataset in a specified environment. Parameters: environment (string), dataset (string)

`get_trigger`

Get detailed trigger information for a specified dataset in a specified environment. Parameters: environment (string), dataset (string), triggerId (string)

`get_trace_link`

Generate a deep link to a specific trace in the Honeycomb UI.

`get_instrumentation_help`

Provides OpenTelemetry instrumentation guidance for a specified language and file path. Parameters: language (string), filepath (string)

- list_datasets: List all datasets in an environment

  { "environment": "production" }

- get_columns: Get column information for a dataset

  {

    "environment": "production",

    "dataset": "api-requests"

  }

- run_query: Run analytics queries with rich options

  {

    "environment": "production",

    "dataset": "api-requests",

    "calculations": [

      { "op": "COUNT" },

      { "op": "P95", "column": "duration_ms" }

    ],

    "breakdowns": ["service.name"],

    "time_range": 3600

  }

- analyze_columns: Analyzes specific columns in a dataset by running statistical queries and returning computed metrics.

- list_slos: List all SLOs for a dataset

  {

    "environment": "production",

    "dataset": "api-requests"

  }

- get_slo: Get detailed SLO information

  {

    "environment": "production",

    "dataset": "api-requests",

    "sloId": "abc123"

  }

- list_triggers: List all triggers for a dataset

  {

    "environment": "production",

    "dataset": "api-requests"

  }

- get_trigger: Get detailed trigger information

  {

    "environment": "production",

    "dataset": "api-requests",

    "triggerId": "xyz789"

  }

- get_trace_link: Generate a deep link to a specific trace in the Honeycomb UI

- get_instrumentation_help: Provides OpenTelemetry instrumentation guidance

  {

    "language": "python",

    "filepath": "app/services/payment_processor.py"

  }

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "honeycomb": {
            "env": {
                "HONEYCOMB_API_KEY": "your_api_key"
            },
            "args": [
                "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
            ],
            "command": "node"
        }
    }
}

Linux

{
    "env": {
        "HONEYCOMB_API_KEY": "your_api_key"
    },
    "args": [
        "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
    ],
    "command": "node"
}

Macos

{
    "env": {
        "HONEYCOMB_API_KEY": "your_api_key"
    },
    "args": [
        "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
    ],
    "command": "node"
}

Windows

{
    "env": {
        "HONEYCOMB_API_KEY": "your_api_key"
    },
    "args": [
        "/c",
        "node",
        "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
    ],
    "command": "cmd"
}

Honeycomb MCP

> ⚠️ DEPRECATED: This self-hosted MCP server is deprecated. Please migrate to the hosted Honeycomb Model Context Protocol (MCP) solution at Honeycomb MCP Documentation.

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.

Requirements

- 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.

Honeycomb Enterprise Only

Currently, this is only available for Honeycomb Enterprise customers.

How it works

Today, this is a single server process that you must run on your own computer. It is not authenticated. All information uses STDIO between your client and the server.

Installation

pnpm install
pnpm run build

The build artifact goes into the /build folder.

Configuration

To use this MCP server, you need to provide Honeycomb API keys via environment variables in your MCP config.

{
    "mcpServers": {
      "honeycomb": {
        "command": "node",
        "args": [
          "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
        ],
        "env": {
          "HONEYCOMB_API_KEY": "your_api_key"
        }
      }
    }
}

For multiple environments:

{
    "mcpServers": {
      "honeycomb": {
        "command": "node",
        "args": [
          "/fully/qualified/path/to/honeycomb-mcp/build/index.mjs"
        ],
        "env": {
          "HONEYCOMB_ENV_PROD_API_KEY": "your_prod_api_key",
          "HONEYCOMB_ENV_STAGING_API_KEY": "your_staging_api_key"
        }
      }
    }
}

Important: These environment variables must bet set in the env block of your MCP config.

EU Configuration

EU customers must also set a HONEYCOMB_API_ENDPOINT configuration, since the MCP defaults to the non-EU instance.

```bash

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

list_datasets

get_columns

run_query

analyze_columns

list_slos

get_slo

list_triggers

get_trigger

get_trace_link

get_instrumentation_help

Claude Desktop / Cursor

Linux

Macos

Windows

Honeycomb MCP

Requirements

Honeycomb Enterprise Only

How it works

Installation

Configuration

EU Configuration

Install

More like this

Sequential Thinking

Aws Kb Retrieval Server

Filesystem

EverArt

Google Drive

Reactive Resume

`list_datasets`

`get_columns`

`run_query`

`analyze_columns`

`list_slos`

`get_slo`

`list_triggers`

`get_trigger`

`get_trace_link`

`get_instrumentation_help`