BugCatcher
File bug reports, run AI-assisted diagnosis, and track bug status from Cursor, Claude, or Windsurf via MCP.
Overview
io.github.fDiosc/bugcatcher-mcp is an Operate-phase MCP server that handles bug reports, AI diagnosis, and status management for agent IDEs.
What is this MCP server?
- Bug reports with AI diagnosis from the agent session
- Status management for tracked issues
- Explicit support for Cursor, Claude, and Windsurf workflows
- npm bugcatcher-mcp v1.0.0 stdio package from fDiosc/bugcatcher
- Server version 1.0.0
- Transport: stdio
- registryType: npm bugcatcher-mcp
What problem does it solve?
Bugs get described in ad hoc chat threads without diagnosis or status your agent can update consistently.
Who is it for?
Solo builders who debug and ship from MCP IDEs and want a lightweight bug loop without leaving the agent.
Skip if: Large teams standardized on Jira-only workflows with no MCP, or orgs that need full APM instead of bug intake.
What do I get? / Deliverables
You get MCP-driven bug reports, AI diagnosis, and managed statuses aligned with Cursor, Claude, and Windsurf sessions.
- Structured bug reports from agent sessions
- AI-assisted diagnosis output
- Updated bug status records
Recommended MCP Servers
Journey fit
How it compares
Agent-native bug intake and diagnosis MCP, not a deployment or prompt marketplace server.
Common Questions / FAQ
Who is io.github.fDiosc/bugcatcher-mcp for?
Indie developers using Cursor, Claude Code, or Windsurf who want structured bugs and AI diagnosis from the same MCP session.
When should I use io.github.fDiosc/bugcatcher-mcp?
Use it when you are reproducing defects, triaging after ship, or handling support-driven fixes and need status tracking in the agent.
How do I add io.github.fDiosc/bugcatcher-mcp to my agent?
Register the stdio MCP entry for npm package bugcatcher-mcp v1.0.0 in your Cursor, Claude, or Windsurf MCP configuration.