honeybadger-mcp-server

honeybadger-io/honeybadger-mcp-server

3.4

If you are the rightful owner of honeybadger-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The Honeybadger MCP Server provides structured access to Honeybadger's API through the Model Context Protocol (MCP), enabling seamless integration with various development environments.

The Honeybadger MCP Server is a robust solution designed to facilitate structured and efficient access to Honeybadger's API using the Model Context Protocol (MCP). This server is particularly useful for developers who need to integrate Honeybadger's error monitoring and management capabilities into their development workflows. By leveraging Docker, the server ensures a consistent and isolated environment for running the MCP server, making it easy to deploy and manage. The server supports various development platforms, including VS Code, Zed, Cursor, Windsurf, and Claude Desktop, providing flexibility and ease of use across different environments. With features like project management, fault tracking, and integration management, the Honeybadger MCP Server is an essential tool for developers looking to enhance their error monitoring and management processes.

Features

  • Docker-based deployment for easy setup and management.
  • Supports multiple development platforms including VS Code, Zed, Cursor, Windsurf, and Claude Desktop.
  • Comprehensive project management tools including project creation, updating, and deletion.
  • Advanced fault tracking capabilities with detailed fault information and occurrence counts.
  • Integration management for seamless connection with various channels and services.

Usages

usage with cursor windsurf claude desktop

{
  "mcpServers": {
    "honeybadger": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HONEYBADGER_PERSONAL_AUTH_TOKEN",
        "ghcr.io/honeybadger-io/honeybadger-mcp-server"
      ],
      "env": {
        "HONEYBADGER_PERSONAL_AUTH_TOKEN": "your personal auth token"
      }
    }
  }
}

usage with vs code

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "honeybadger_auth_token",
        "description": "Honeybadger Personal Auth Token",
        "password": true
      }
    ],
    "servers": {
      "honeybadger": {
        "command": "docker",
        "args": [
          "run",
          "-i",
          "--rm",
          "-e",
          "HONEYBADGER_PERSONAL_AUTH_TOKEN",
          "ghcr.io/honeybadger-io/honeybadger-mcp-server"
        ],
        "env": {
          "HONEYBADGER_PERSONAL_AUTH_TOKEN": "${input:honeybadger_auth_token}"
        }
      }
    }
  }
}

usage with zed

{
  "context_servers": {
    "honeybadger": {
      "command": {
        "path": "docker",
        "args": [
          "run",
          "-i",
          "--rm",
          "-e",
          "HONEYBADGER_PERSONAL_AUTH_TOKEN",
          "ghcr.io/honeybadger-io/honeybadger-mcp-server"
        ],
        "env": {
          "HONEYBADGER_PERSONAL_AUTH_TOKEN": "your personal auth token"
        }
      },
      "settings": {}
    }
  }
}

usage with direct execution

{
  "mcpServers": {
    "honeybadger": {
      "command": "/path/to/honeybadger-mcp-server",
      "args": ["stdio"],
      "env": {
        "HONEYBADGER_PERSONAL_AUTH_TOKEN": "your personal auth token"
      }
    }
  }
}

Tools

  1. list_projects

    List all Honeybadger projects.

  2. get_project

    Get detailed information for a single project by ID.

  3. create_project

    Create a new Honeybadger project.

  4. update_project

    Update an existing Honeybadger project.

  5. delete_project

    Delete a Honeybadger project.

  6. get_project_occurrence_counts

    Get occurrence counts for all projects or a specific project.

  7. get_project_integrations

    Get a list of integrations (channels) for a Honeybadger project.

  8. get_project_report

    Get report data for a Honeybadger project.

  9. list_faults

    Get a list of faults for a project with optional filtering and ordering.

  10. get_fault

    Get detailed information for a specific fault in a project.

  11. get_fault_counts

    Get fault count statistics for a project with optional filtering.

  12. list_fault_notices

    Get a list of notices (individual error events) for a specific fault.

  13. list_fault_affected_users

    Get a list of users who were affected by a specific fault with occurrence counts.