Honeybadger MCP Server

Example Use Cases

• 1

  Search and filter Honeybadger faults by text, creation time, or occurrence time to identify relevant errors.

• 2

  Retrieve detailed notices for a given fault (with time filtering and pagination) to assist debugging and root-cause analysis.

• 3

  Integrate Honeybadger error data into MCP workflows or desktop clients (SSE or stdio) for automated monitoring and triage.

Description

This Model Context Protocol (MCP) server bridges MCP-compatible AI agents with the Honeybadger error monitoring API, enabling programmatic listing, filtering, and inspection of faults and notices. It provides two primary tools — list_faults (search, filter, sort, paginate faults) and get_fault_details (retrieve and paginate notices for a fault) — and supports SSE and stdio transports for integration with clients like Claude Desktop. The server is runnable locally, via Docker, or as an installed package and requires a Honeybadger API key and project ID. It is designed to help agents surface relevant error data for analysis, debugging, and triage workflows.