MCP Server for Claude Code
v5.0 20 tools included

Stop Claude Code
from breaking your code.

It remembers every error, warns before repeats, and blocks coding without a spec.

Claude Code is fast. But it forgets what it broke yesterday and breaks it again today.
Clouvel remembers.

Free and open source. 20 tools included.

Works with:
Claude Code CLI Claude Desktop VS Code Cursor

pip install clouvel · works everywhere MCP is supported

PyPI version Python 3.10+ MCP Compatible 60+ Tools

The Problem

Claude Code is fast. But without memory, speed creates chaos.

1

AI recreates bugs it fixed yesterday

No error memory between sessions. Same mistake, different day.

2

You ship without anyone reviewing

No second pair of eyes. Blind spots go straight to production.

3

"Why did we do it this way?"

Decisions lost when context resets. Waste hours rediscovering context.

4

New session = same old mistakes

AI starts from zero every time. No learning, no improvement.

What Clouvel Does

Three things. All automatic.

1. Error Memory

AI that learns from mistakes.

Warning: This error happened before.

Root cause: Missing null check on DB query

Prevention: Always validate query results

(Memory #7 - prevented 3 times)

2. Spec Gate

Think before AI codes.

You: "Build login"

BLOCKED - No PRD found.

You: *writes PRD*

PASS - Ready to code.

3. Quick Check

Blind spots in 10 seconds.

PM: "What happens when login fails 5 times?"

CTO: "Rate limiting needed for brute force."

See it in action

Real output from Clouvel

No spec = BLOCKED BLOCK
Claude Code โ€” my-project

claude> Build a login page with OAuth support

๐Ÿšซ BLOCK | Missing: PRD, Acceptance

Fix: start(path=".")

Found: None | Missing (required): PRD.md, Acceptance Criteria

Next: write PRD with Acceptance Criteria section first

Why spec first? 10 min spec = 2 hours saved (no rework)

claude> โ–Š

Spec found = PASS PASS
Claude Code โ€” my-project

claude> Build a login page with OAuth support

โœ… PASS | Required: PRD โœ“ Acceptance โœ“ | 12 tests

Ready to code

โœ“ docs/PRD.md (OAuth, password reset, rate limiting defined)

โœ“ Acceptance Criteria: 8 items

โœ“ Tests: 12 test files

Claude

I'll implement the login page based on your PRD specifications:

  • โ€ข OAuth providers: Google, GitHub (as specified in PRD ยง4.1)
  • โ€ข Password reset flow with email verification
  • โ€ข Rate limiting: 5 attempts per 15 minutes
  • โ€ข Session timeout: 24 hours

Creating src/auth/login.ts...

claude> โ–Š

error_learn

# Error Learning Analysis

Pattern Analysis:

  import_error    3x   Learning needed

  null_check     2x   Observing

CLAUDE.md Updated:

  + NEVER: import from deleted module

  + ALWAYS: check query result before use

Learned: 2 rules · Analyzed: 5 errors

meeting

# C-Level Meeting: Auth System

PM: "What happens when the token expires mid-session?"

CTO: "Are we hashing passwords with bcrypt or argon2?"

CSO: "Rate limiting on login? Brute force is day-one risk."

QA: "Edge case: user logs in on two devices simultaneously?"

4 managers · 8 blind spots found

ship

SHIP READY

[โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–‘] 3/4 PASS

  PASS   LINT        2.5s

  PASS   TYPECHECK   1.8s

  PASS   TEST        4.2s

  SKIP   BUILD

Evidence: .claude/evidence/auth_0221.md

All Features

Everything included. No tiers, no limits.

Feature Included
Error history Full history + patterns
Context slots 50 + timeline
Manager feedback 8 managers, 2+ questions
Error learning Auto-generates rules
Cross-project memory Share lessons everywhere
Drift detection Catches scope creep
Ship pipeline Full verify + evidence

Tools

20 tools. All included.

Core Tools

can_codeBlocks coding without a spec
startSet up project with PRD templates
save_prdSave PRD from conversation
error_checkWarns before repeating mistakes
error_recordRecords errors with root cause
context_saveSaves state before context runs out
context_loadRestores state in new session
quick_perspectivesQuick blind-spot check
gateRun lint, test, build in sequence
license_statusCheck installation status

Advanced Tools

error_learnAuto-generates NEVER/ALWAYS rules
memory_statusError memory dashboard
memory_searchSearch past errors by keyword
memory_global_searchCross-project error patterns
drift_checkDetects scope drift from goals
planDetailed execution plans
meetingFull 8-manager C-Level review
shipOne-click lint+test+build+evidence
record_decisionPersistent knowledge base
search_knowledgeSearch past decisions

Quick Start

3 commands. Under 60 seconds.

# 1. Install

pip install clouvel

# 2. Auto-configure for your client

clouvel install

# If 'clouvel' not recognized:
# py -m clouvel install      (Windows)
# python3 -m clouvel install (Mac/Linux)

# 3. Start coding

claude

# Clouvel runs automatically

That's it. Clouvel runs automatically when you use Claude Code.

How it plays out

Day 1:  Install → start → write PRD → can_code PASS → code

Day 3:  Error happens → error_record saves it

Day 5:  Same file → error_check warns "this broke before"

Day 7:  5+ errors → error_learn auto-generates rules

Day 10: Context runs out → context_save/load preserves everything

Day 14: Cross-project memory shares lessons across repos

Built for developers who ship

Join early adopters using Clouvel in production

60+
MCP Tools
Weekly
Updates
100%
Open Source
On GitHub

Using Clouvel in your project? We'd love to hear about it.

Share your experience

FAQ

What exactly does Clouvel do?

Clouvel is an MCP server that runs alongside Claude Code. It records every error with root cause analysis, warns you before repeating past mistakes, and blocks coding until you have a spec document. Think of it as persistent memory for your AI coding assistant.

Why not just use CLAUDE.md?

CLAUDE.md is static rules you write by hand. Clouvel learns automatically from your actual errors and decisions. It detects patterns across sessions and warns you before you repeat a mistake. You can't write a CLAUDE.md rule for a bug you haven't encountered yet.

Does it work offline?

Yes. Everything works fully offline. All data stays local on your machine.

Does it touch my code or project files?

No. Clouvel is an MCP server - it provides tools to Claude Code but never modifies your source code. It stores its data in a .claude/ folder. Your project structure stays untouched.

What tools are included?

All 20 tools are included: spec gating, full error history with pattern learning, context save/load, cross-project memory, 8-manager C-Level review, one-click ship with evidence, and more.

What data does Clouvel send to the server?

Nothing. Clouvel runs entirely offline. Your code, documents, and error history never leave your machine.

What if I change my computer?

Just install Clouvel on your new machine with pip install clouvel. Your project-level data lives in .claude/ inside each repo, so it travels with your code.

Contact Us

Machine reset, license issues - we'll help you quickly

Or reach us at GitHub Issues

Built by a solo developer

I built Clouvel because I was tired of Claude Code breaking the same thing twice. Every error I fixed yesterday came back tomorrow. So I built a memory layer that actually learns.

Clouvel is actively maintained and updated weekly. Questions, bugs, or ideas — I read every GitHub Issue.

If Clouvel saves you time, help others find it

A GitHub star helps independent dev tools get discovered

Star on GitHub