The mcp-debug-recorder records debug sessions, terminal commands, and fixes in a local SQLite database, allowing users to query their debugging history in natural language.
From the registry: Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
Please install the `mcp-debug-recorder` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Node.js** — Required to run npx (https://nodejs.org)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["mcp-debug-recorder"]
- optional environment variables:
- `DEBUG_RECORDER_DB`: Override the SQLite database path (example: `/path/to/custom.db`)
- `LOG_LEVEL`: Structured log level (example: `info`)
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.DEBUG_RECORDER_DBoverride the SQLite database pathPORToverride the HTTP server port for Streamable HTTP modeLOG_LEVELminimum structured log level (`debug`, `info`, `warn`, `error`)FUZZY_THRESHOLDoverride the Fuse.js threshold used during rerankingReal-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.