debug-recorder-mcp
Why this exists
Debugging knowledge usually disappears into chat windows, terminals, and commit history. debug-recorder-mcp gives MCP-enabled agents and IDEs a durable local memory so they can answer:
“Have I fixed this before?”
에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
DEBUG_RECORDER_DB=<value> LOG_LEVEL=<value> FUZZY_THRESHOLD=<value> DEBUG_RECORDER_REDACT_BEFORE_STORE=<value> HOST=<value> PORT=<value> DEBUG_RECORDER_HTTP_TOKEN=<secret> DEBUG_RECORDER_ALLOWED_HOSTS=<value> DEBUG_RECORDER_ALLOWED_ORIGINS=<value> DEBUG_RECORDER_MAX_BODY_BYTES=<value> DEBUG_RECORDER_REMOTE_HTTP=<value> claude mcp add io.github.oaslananka-debug-recorder-mcp -- npx -y debug-recorder-mcp@1.1.3터미널에서 실행합니다.
{ "mcpServers": { "io.github.oaslananka-debug-recorder-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "DEBUG_RECORDER_DB": "<value>", "LOG_LEVEL": "<value>", "FUZZY_THRESHOLD": "<value>", "DEBUG_RECORDER_REDACT_BEFORE_STORE": "<value>", "HOST": "<value>", "PORT": "<value>", "DEBUG_RECORDER_HTTP_TOKEN": "<secret>", "DEBUG_RECORDER_ALLOWED_HOSTS": "<value>", "DEBUG_RECORDER_ALLOWED_ORIGINS": "<value>", "DEBUG_RECORDER_MAX_BODY_BYTES": "<value>", "DEBUG_RECORDER_REMOTE_HTTP": "<value>" } } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
Debugging knowledge usually disappears into chat windows, terminals, and commit history. debug-recorder-mcp gives MCP-enabled agents and IDEs a durable local memory so they can answer:
“Have I fixed this before?”
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
It stores each debugging session, error, command, attempted fix, working fix, tags, and context in a local SQLite database. Search combines SQLite FTS5 with fuzzy reranking, reusable presets, pagination metadata, related-session groups, and optional Markdown exports.
get_diagnostics returns redacted runtime, schema, package, and health signals for support without leaking raw paths, tokens, stack traces, or command output.Requires Node.js 22 LTS or 24 LTS and npm 10+.
npx debug-recorder-mcp
Default database path:
~/.debug-recorder-mcp/sessions.db
Use a custom database path:
DEBUG_RECORDER_DB=/path/to/custom.db npx debug-recorder-mcp
{
"mcpServers": {
"debug-recorder-mcp": {
"command": "npx",
"args": ["debug-recorder-mcp"]
}
}
}
Create or update .vscode/mcp.json:
{
"servers": {
"debug-recorder-mcp": {
"type": "stdio",
"command": "npx",
"args": ["debug-recorder-mcp"]
}
}
}
More setup examples are in Client setup recipes.
Ask your MCP client:
I am getting
TypeError: Cannot read properties of undefined. Have I seen this before?
The client can call find_similar_errors, then inspect the best match with get_session_context.
start_debug_session with the problem title and error details.record_command.add_fix.update_session.close_session.export_sessions with format: "json". The response is marked with
format: "json" and contains the full sessions, fixes, and commands
arrays.import_sessions.payload.For a lightweight inventory, call export_sessions with format: "summary".
Summary responses are marked with format: "summary", include aggregate
stats and abbreviated session rows, and are not restore payloads.
The package also supports local Streamable HTTP:
npm run start:http
Useful routes:
GET /healthGET /versionPOST /mcpHTTP mode is local-first by default. It binds to 127.0.0.1, creates an isolated stateless MCP server/transport per request, validates Host, validates browser Origin when present, and enforces a JSON body-size limit before the MCP transport receives the request.
For deliberate non-loopback exposure, set all of these:
HOST=0.0.0.0
DEBUG_RECORDER_REMOTE_HTTP=true
DEBUG_RECORDER_HTTP_TOKEN=replace-with-a-long-random-token
DEBUG_RECORDER_ALLOWED_HOSTS=debug-recorder.example.com
DEBUG_RECORDER_ALLOWED_ORIGINS=https://debug-recorder.example.com
npm run start:http
Wildcard origins are rejected for remote mode. The static bearer token is private/shared-secret mode: every caller shares one identity, one authority level, and one SQLite dataset. It is suitable for loopback, an encrypted trusted network, or a private authenticating proxy, but it is not OAuth and does not provide per-user scopes or revocation.
Public multi-user HTTP is not supported by the current release. The accepted target architecture uses an external authorization server and MCP-aware gateway with protected-resource discovery, audience-bound tokens, scopes, rate limits, audit events, and subject-aware storage. See Public HTTP authorization and ADR-0006.
Boolean configuration also accepts false, 0, and no; values are
case-insensitive, whitespace is ignored, and unsupported values fail fast.
Diagnostics reports the resolved effective values rather than re-reading changed
environment strings.
better-sqlite3.~/.debug-recorder-mcp/sessions.db.
better-sqlite3uses a native addon. If Node versions change and bindings fail, runnpm rebuild better-sqlite3.
docker build -t debug-recorder-mcp:local .
docker run --rm -p 127.0.0.1:3000:3000 \
-e HOST=0.0.0.0 \
-e DEBUG_RECORDER_REMOTE_HTTP=true \
-e DEBUG_RECORDER_HTTP_TOKEN=replace-with-a-long-random-token \
-e DEBUG_RECORDER_ALLOWED_HOSTS=127.0.0.1:3000,localhost:3000 \
-e DEBUG_RECORDER_ALLOWED_ORIGINS=http://127.0.0.1:3000,http://localhost:3000 \
debug-recorder-mcp:local
The image installs with npm ci, preserves reviewed native install scripts, prunes development dependencies, and runs as the non-root node user.
Published documentation is generated by npm run docs:site and published to GitHub Pages:
https://oaslananka.github.io/debug-recorder-mcp/
Important docs:
npm ci
npm run format:check
npm run lint
npm run check:dead-code
npm run test:coverage
npm run test:fuzz
npm run build
npm run test:e2e
npm run audit
npm run check:install-scripts
npm pack --dry-run
npm run check:package-size
npm run check:version
npm run check:mcp
npm run check:security-policy
npm run check:sbom
npm run docs:site
Full local gate:
npm run ci:local
Release readiness:
npm run prepublishOnly
npm run check:mcp-registry
The normal release workflow uses Release Please, builds release assets, generates SBOM/checksums, attests the tarball, uploads GitHub Release assets, and publishes to npm with provenance.
For the first npm package creation, use the manual Initial npm Token Publish workflow with repository secret NPM_TOKEN. After the package exists and npm trusted publishing is configured, the regular Release workflow can publish through GitHub OIDC. Details are in Release flow.
Released under the MIT License. package.json also declares "license": "MIT", and the npm package includes LICENSE.
If this project saves you debugging time, support development here:
Funding metadata is available in both .github/FUNDING.yml and package.json.
This repository owns the product-level agent plugin, MCP runtime configuration, and product-specific skills for debug-recorder-mcp. The central agent-tools repository should catalog this plugin, but the manifest and workflow instructions live here so they stay synchronized with the actual MCP server package.
Validate plugin packaging locally:
claude plugin validate .
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
{ "mcpServers": { "io.github.oaslananka-debug-recorder-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "DEBUG_RECORDER_DB": "<value>", "LOG_LEVEL": "<value>", "FUZZY_THRESHOLD": "<value>", "DEBUG_RECORDER_REDACT_BEFORE_STORE": "<value>", "HOST": "<value>", "PORT": "<value>", "DEBUG_RECORDER_HTTP_TOKEN": "<secret>", "DEBUG_RECORDER_ALLOWED_HOSTS": "<value>", "DEBUG_RECORDER_ALLOWED_ORIGINS": "<value>", "DEBUG_RECORDER_MAX_BODY_BYTES": "<value>", "DEBUG_RECORDER_REMOTE_HTTP": "<value>" } } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
게시자가 등록한 환경 변수: DEBUG_RECORDER_DB, LOG_LEVEL, FUZZY_THRESHOLD, DEBUG_RECORDER_REDACT_BEFORE_STORE, HOST, PORT, DEBUG_RECORDER_HTTP_TOKEN, DEBUG_RECORDER_ALLOWED_HOSTS, DEBUG_RECORDER_ALLOWED_ORIGINS, DEBUG_RECORDER_MAX_BODY_BYTES, DEBUG_RECORDER_REMOTE_HTTP.
MCP Debug Recorder은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-10. Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.