Honeybadger MCP Server

A Model Context Protocol (MCP) server implementation for interacting with the Honeybadger API. This server allows AI agents to fetch and analyze

Local serverstdioPython

What is the Honeybadger MCP MCP server?

Honeybadger mcp mcp server connects Honeybadger MCP to AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server implementation for interacting with the Honeybadger API. This server allows AI agents to fetch and analyze error data from your Honeybadger projects.

What Honeybadger MCP does

A Model Context Protocol (MCP) server implementation for interacting with the Honeybadger API. This server allows AI agents to fetch and analyze error data from your Honeybadger projects.

This MCP server provides a bridge between AI agents and the Honeybadger error monitoring service. It follows the best practices laid out by Anthropic for building MCP servers, allowing seamless integration with any MCP-compatible client.

Key capabilities

  • Search by text query
  • Filter by creation or occurrence timestamps
  • Sort by frequency or recency
  • Paginate results
  • Filter notices by creation time
  • Paginate through notices
  • Results ordered by creation time descending

Installing the honeybadger mcp mcp server

The server is distributed via a container image as honeybadger/mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 2 environment variables: HONEYBADGER_API_KEY, HONEYBADGER_PROJECT_ID. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • Python 3.10+ - Honeybadger API key and Project ID - Docker if running the MCP server as a container (recommended)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Honeybadger MCP sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by bobtista, written in Python.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the honeybadger mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

How to install the Honeybadger MCP MCP server

### Docker Configuration

```json
{
  "mcpServers": {
    "honeybadger": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "honeybadger/mcp",
        "--transport",
        "stdio",
        "--api-key",
        "YOUR-API-KEY",
        "--project-id",
        "YOUR-PROJECT-ID"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Python 3.10+ - Honeybadger API key and Project ID - Docker if running the MCP server as a container (recommended)
VariableDescriptionRequired
HONEYBADGER_API_KEYCredential the server authenticates with.Yes
HONEYBADGER_PROJECT_IDConfiguration value read at startup.Optional

Frequently asked questions

It connects Honeybadger MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Honeybadger MCP directly.