Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Claude Error CollectorRecord that I prefer async/await over .then() chains for all API calls"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Claude Error Collector
An MCP server for Claude Code that learns from your corrections. When you tell Claude "that was wrong" or "no, do it like this", it records the lesson as a rule in your CLAUDE.md - so the same mistake doesn't happen twice.
How It Works
You correct Claude during a coding session
Claude recognizes the correction and calls the
record_errortoolThe server derives a rule and writes it to the appropriate
CLAUDE.mdClaude reads that rule in future sessions and avoids repeating the mistake
The server automatically detects whether you're in a project directory (writes to project CLAUDE.md) or your home directory (writes to ~/.claude/CLAUDE.md).
Tools
record_error
Records a correction and saves it as a learned rule.
Parameter | Type | Required | Description |
| string | yes | What was wrong |
| string | yes | What is correct |
| string | yes | Derived guideline, e.g. "ALWAYS use X instead of Y" |
| string | no | Current working directory (for finding project CLAUDE.md) |
list_errors
Lists all learned rules from the relevant CLAUDE.md.
Parameter | Type | Required | Description |
| string | no | Current working directory |
Output Format
Rules are stored in a ## Learned Rules section in your CLAUDE.md:
Installation
The install script handles everything:
Installs dependencies and builds the project
Registers the MCP server with Claude Code (
claude mcp add)
No manual CLAUDE.md editing needed — the server provides its own instructions to Claude via MCP server metadata.
Restart Claude Code after installation to activate.
Manual Installation
If you prefer to set things up manually:
CLAUDE.md Resolution
The server finds the right CLAUDE.md using this logic:
If
project_diris provided: walk up the directory tree looking forCLAUDE.mdIf found and not in the home directory: use it (project-level rules)
Fallback:
~/.claude/CLAUDE.md(global rules)
Duplicate Detection
Before writing a rule, the server checks existing rules using case-insensitive substring matching. If the new rule is already covered by an existing one (or vice versa), it skips the write.
License
MIT