Honeybadger

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.

The server provides two essential tools for interacting with Honeybadger:
-

list_faults: List and filter faults from your Honeybadger project

- Search by text query
- Filter by creation or occurrence timestamps
- Sort by frequency or recency
- Paginate results

get_fault_details: Get detailed information about specific faults

- Filter notices by creation time
- Paginate through notices
- Results ordered by creation time descending

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

git clone https://github.com/bobtista/honeybadger-mcp.git cd honeybadger-mcp

Install development dependencies (optional):

cp .env.example .env # Edit .env with your configuration

docker build -t honeybadger/mcp --build-arg PORT=8050 .

Create a.envfile and configure your environment variables

You can configure the server using either environment variables or command-line arguments:

# Using environment variables: HONEYBADGER_API_KEY=your-key HONEYBADGER_PROJECT_ID=your-project uv run src/honeybadger_mcp_server/server.py # Using CLI arguments: uv run src/honeybadger_mcp_server/server.py --api-key your-key --project-id your-project

uv run src/honeybadger_mcp_server/server.py --transport stdio --api-key your-key --project-id your-project

# Using environment variables: HONEYBADGER_API_KEY=your-key HONEYBADGER_PROJECT_ID=your-project honeybadger-mcp-server # Using CLI arguments: honeybadger-mcp-server --api-key your-key --project-id your-project

honeybadger-mcp-server --transport stdio --api-key your-key --project-id your-project

docker run --env-file .env -p 8050:8050 honeybadger/mcp

With stdio, the MCP client itself can spin up the MCP server container, so nothing to run at this point.

Once you have the server running with SSE transport, you can connect to it using this configuration:

{ "mcpServers": { "honeybadger": { "transport": "sse", "url": "http://localhost:8050/sse" } } }

honeybadger-mcp-server --api-key your-key --project-id your-project

{ "mcpServers": { "honeybadger": { "transport": "sse", "url": "http://localhost:8050/sse" } } }

{ "mcpServers": { "honeybadger": { "command": "uv", "args": [ "run", "--project", "/path/to/honeybadger-mcp", "src/honeybadger_mcp_server/server.py", "--transport", "stdio", "--api-key", "YOUR-API-KEY", "--project-id", "YOUR-PROJECT-ID" ] } } }

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

result = await client.call_tool("list_faults", { "q": "RuntimeError", # Optional search term "created_after": 1710806400, # Unix timestamp (2024-03-19T00:00:00Z) "occurred_after": 1710806400, # Filter by occurrence time "limit": 10, # Max 25 results "order": "recent" # 'recent' or 'frequent' })

result = await client.call_tool("get_fault_details", { "fault_id": "abc123", "created_after": 1710806400, # Unix timestamp "created_before": 1710892800, # Optional end time "limit": 5 # Number of notices (max 25) })

# Install dev dependencies uv pip install -e ".[dev]" # Run tests pytest

# Run type checker pyright # Run linter ruff check .

Contributions are welcome! Please feel free to submit a Pull Request.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Bumblebee Endpoint Receipt is a paid remote MCP endpoint for developer endpoint scanner MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and a

A feature-rich gateway and proxy that federates MCP and REST services, unifying discovery, authentication, rate-limiting, and observability into a single endpoint for AI clients.

Full MCP server for the https://portkey.ai AI Gateway Admin API with 151 tools across 18 domains.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.

Enable AI Agents to fix build failures from CircleCI.

Tool platform by IBM to build, test and deploy tools for any data source

One remote MCP server for 500+ production APIs — Stripe, HubSpot, Postgres, Gmail, and more. OAuth and API key auth, credential management, and a CLI.

Integrates with PostHog for feature flag management and error tracking.

An MCP server for interacting with the Postman API, requiring an API key.