Confucius Debug

io.github.sstklenPublished by GitHub account sstklenv2.0.1Updated Oct 24, 2026

AI debugging with 980+ verified fixes. Search the YanHui KB — never repeat a mistake.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant search a shared knowledge base of verified debugging fixes and contribute new ones, tracked by a user identifier.

What you can do
Confucius Debug is a local MCP server that gives an assistant access to a debugging knowledge base described as containing over 980 verified fixes. According to its description, it supports searching that knowledge base so an assistant can look up known solutions instead of repeating past mistakes, and it also offers analyze and contribute operations for submitting findings. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
When to use it
Consider it when debugging work would benefit from looking up previously verified fixes, or when you want to record solutions your assistant finds so they can be reused later. It is a desktop-only local process, so it is not usable from a web client.
Requirements
Runs as a local process over stdio, installed from the npm package confucius-debug-mcp, so Node.js and npm are needed. The environment variable CONFUCIUS_LOBSTER_ID is optional for search but required for analyze and contribute; it is described as any username used to track contributions. No authentication is declared.
Before you install
The server sends your search queries and any contributed fixes to a third-party knowledge base, so avoid including secrets, credentials, or proprietary code in queries or contributions. The CONFUCIUS_LOBSTER_ID value is a tracking identifier tied to your contributions and is not anonymous. Contribute operations write content to a shared external knowledge base, so review what is submitted before it is sent.

Installation

In SourceWeft

  1. Open Confucius Debug 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. v2.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.