MCP Debug Recorder

io.github.oaslanankaPublished by GitHub account oaslanankav1.0.1Updated Oct 24, 2026

Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Records debug sessions, commands, failed attempts, and successful fixes into a local SQLite history for later lookup.

What you can do
MCP Debug Recorder stores debugging activity — commands run, attempts that failed, and fixes that worked — in a local SQLite database. It keeps this history on the user's machine and supports fuzzy reranking of stored entries, with the database location, fuzzy match threshold, and log level configurable through environment variables.
When to use it
Useful when you want an assistant to keep a searchable record of debugging sessions so past failures and fixes can be recalled instead of rediscovered. Best suited to local, desktop-based development workflows where history should stay on the machine.
Requirements
Runs as a local stdio process installed from the npm package mcp-debug-recorder, so Node.js is needed. Desktop only; no web execution. No authentication is declared. Optional environment variables: DEBUG_RECORDER_DB, FUZZY_THRESHOLD, LOG_LEVEL.
Before you install
It writes debugging history to a local SQLite database, so recorded commands and fixes may contain sensitive values; review what gets stored and where DEBUG_RECORDER_DB points. No credentials, payments, or third-party data sharing are indicated.

Installation

In SourceWeft

  1. Open MCP Debug Recorder in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.