Honeybadger

This MCP server lets you fetch and analyze Honeybadger errors directly from Cursor IDE, so you can inspect faults, review occurrences, and get actionable fix suggestions without leaving your development environment.

How to use

From Cursor, connect to the Honeybadger MCP server and run the available tools to list faults, view details, fetch error occurrences, and analyze issues. Use the dedicated commands to explore recent production errors, inspect a specific fault, or request suggested fixes. Each tool accepts optional filters such as project, environment, and whether an issue is resolved.

How to install

Prerequisites: ensure you have Node.js 18+ installed, a Honeybadger account with API access, and Cursor IDE with MCP support.

Step 1. Install the MCP server globally or use it as a project dependency. You can install globally with npm and then configure Cursor to use the global command.

Command to install globally:

npm install -g honeybadger-mcp

Step 2. Configure Cursor to run the MCP server as a stdio process using the global command. The API key and project ID must be provided via environment variables.

{
  "mcpServers": {
    "honeybadger": {
      "command": "honeybadger-mcp",
      "env": {
        "HONEYBADGER_API_KEY": "your_api_key_here",
        "HONEYBADGER_PROJECT_ID": "your_project_id"
      }
    }
  }
}

Step 3. Alternatively, install the MCP server as a project dependency and run it via Node. In this setup, Cursor should point to the local installation inside node_modules.

Command to run from a local project installation:

{
  "mcpServers": {
    "honeybadger": {
      "command": "node",
      "args": ["./node_modules/honeybadger-mcp/dist/index.js"],
      "env": {
        "HONEYBADGER_API_KEY": "your_api_key_here",
        "HONEYBADGER_PROJECT_ID": "your_project_id"
      }
    }
  }
}

Step 4. Create environment variables file if you prefer. In your project root, create a .env file with the required values.

# Required: Your Honeybadger API key
HONEYBADGER_API_KEY=your_api_key_here

# Optional: Default project ID (can be overridden per request)
HONEYBADGER_PROJECT_ID=your_project_id

# Optional: Custom Honeybadger URL (defaults to https://app.honeybadger.io)
HONEYBADGER_BASE_URL=https://app.honeybadger.io

Additional configuration and prerequisites

Credentials you’ll need are a Honeybadger API key and a project ID. Obtain the API key from Honeybadger and locate the project ID in your Honeybadger project settings.

Environment variables allowed by the server include HONEYBADGER_API_KEY, HONEYBADGER_PROJECT_ID, and optionally HONEYBADGER_BASE_URL. Keep keys secure and avoid committing them to version control.

Security notes

Store API keys securely and rotate them regularly. Prefer read-only tokens when possible to minimize risk.

Troubleshooting

If you encounter authentication errors, verify that your API key is correct and has the necessary permissions. If the project cannot be found, double-check the PROJECT_ID value. For connection issues, ensure your development environment can reach Honeybadger’s API.

Getting started with credentials

To begin, generate a Personal Auth Token in Honeybadger and note the project ID from the project’s settings page. Use these values to populate your environment variables.

Notes

When you run with a local project installation, Cursor will use the path to dist/index.js as shown in the setup examples. If you upgrade the MCP server, re-run the installation steps to refresh the global command or local package in your project.

Available tools

list_honeybadger_faults

Lists recent faults with optional filtering by project, environment, and resolved status.

get_honeybadger_fault

Fetches detailed information about a specific fault.

get_honeybadger_notices

Fetches notices (error occurrences) for a specific fault.

analyze_honeybadger_issue

Provides comprehensive analysis with fix suggestions for a fault.