Featured

Deploy OpenClaw in 60 seconds β€” 20% off logoDeploy OpenClaw in 60 seconds β€” 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger β†’
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger β†’
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free β†’
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now β†’
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data β€” no proxies, no parsers, no maintenance.

Start building free β†’
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it β€” secured from day one.

Get it set up for you β†’
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free β†’
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here β†’

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

DomDemetz/claude-soul MCP server](https://glama.ai/mcp/servers/DomDemetz/claude-soul/badges/score.svg)](https://glama.ai/mcp/servers/DomDemetz/claude-soul) πŸ“‡ 🏠 🍎 🐧 - Self-improving learning engine for Claude Code.

README.md

Claude Soul

![npm version](https://www.npmjs.com/package/claude-soul) ![npm downloads](https://www.npmjs.com/package/claude-soul) ![License: MIT](https://opensource.org/licenses/MIT)

Claude Code forgets everything between sessions. Claude Soul doesn't.

npx claude-soul init --starter

One command. No API key, no cloud, everything local.

Prerequisites: Node.js >= 18, Claude Code (Pro or Max plan).

Three things it does

1. Remembers across sessions

Cross-session memory with semantic search. Facts, decisions, lessons β€” all searchable by meaning, not just keywords. Uses local SQLite + optional Ollama embeddings.

You: "what did we decide about the auth flow last week?"
Claude: [searches memory β†’ finds the decision, context, and reasoning]

2. Tracks your corrections

Every time you correct your Claude β€” "that's wrong", "you missed this", "stop doing that" β€” the system detects the pattern, classifies it, and tracks whether it's getting better or worse.

$ claude-soul shadow --brief

  premature_done: 26 corrections across 10 sessions ↑ [active]
  robot_mode: 7 corrections across 6 sessions ↓↓ [internalized]
  authenticity: 5 corrections across 5 sessions ↓↓ [internalized]

Patterns move through lifecycle stages: new β†’ active β†’ improving β†’ internalized. After 200 sessions of real data: robot_mode went from 0.8 corrections/session to zero.

3. Develops judgment over time

The system extracts behavioral signals from every session and periodically reflects on them. Frameworks that keep working get promoted. Bad ones get retired. After a few weeks, you get a Claude that pushes back on bad ideas, catches its own confabulation, and develops techniques you never prompted.

Install

Quick start (no extra dependencies)

npx claude-soul init --starter

Add this to your CLAUDE.md:

## Soul System
Call `soul_context()` at the start of every conversation.
Use `soul_reflect` when you have idle time.

Done. Memory works with keyword search, everything else runs automatically.

With semantic memory

Semantic search finds memories by meaning β€” "auth decision" finds a memory stored as "chose JWT tokens for login." Without it, search is keyword-based (still works, just less flexible).

# 1. Install Ollama (https://ollama.com)
# 2. Pull the embedding model
ollama pull nomic-embed-text
# 3. Then install as usual
npx claude-soul init --starter

The system auto-detects Ollama. No configuration needed.

For agents (non-interactive)

npx claude-soul init --starter --skip-identity

Skips the name/context questions. Add the CLAUDE.md snippet to your agent's working directory and it works the same way β€” memory, correction tracking, and framework evolution all run through Claude Code's hooks and MCP server regardless of whether a human is typing or an agent is running.

Already installed? Upgrade

npm install -g claude-soul@latest
claude-soul upgrade

Your soul files, frameworks, and data stay untouched. The upgrade re-registers hooks and MCP server with the latest version and adds any new features.

After upgrading, run claude-soul index once to backfill existing data into the memory system.

<details> <summary><b>What's new in v0.2</b></summary>

  • Memory system β€” 6 new MCP tools (memory_save, memory_search, recall, etc.) for cross-session fact storage with semantic search
  • Correction tracking β€” auto-detects when you correct your Claude and classifies the pattern
  • Shadow analysis β€” claude-soul shadow shows behavioral patterns with trend arrows and lifecycle stages
  • Indexing β€” claude-soul index loads your existing journals and soul files into the memory database

</details>

<details> <summary><b>CLI commands</b></summary>

These are optional β€” the system runs automatically. The CLI is for inspecting collected data from your terminal.

| Command | What it does | |---------|-------------| | claude-soul status | System health β€” frameworks, signals, phase | | claude-soul shadow | Your correction patterns with trends | | claude-soul shadow --generate | Auto-generate a SHADOW.md from your data | | claude-soul index | Index existing files into memory database | | claude-soul upgrade | Update hooks without touching your data |

</details>

How it works

Session N
  β”‚
  β”œβ”€ Load identity + frameworks + memory
  β”‚
  β”œβ”€ Normal Claude Code usage
  β”‚
  β”œβ”€ Session ends β†’ extract signals + corrections + index to memory
  β”‚
  └─ Reflection threshold? β†’ evolve frameworks β†’ Session N+1

Everything runs through Claude Code's official extension points: an MCP server (15 tools) and hooks (signal extraction, journaling, memory indexing, correction tracking).

<details> <summary><b>MCP Tools (15 total)</b></summary>

Identity & Learning

| Tool | Purpose | |------|---------| | soul_context | Load identity + frameworks + state at session start | | soul_activate | Select relevant frameworks for current conversation | | soul_framework | Load a single framework with full evidence history | | soul_signal | Record observed interaction patterns | | soul_reflect | Trigger a reflection cycle (quick/deep/meta) | | soul_self_evaluate | Record a self-evaluation of a complex response | | soul_read | Read soul files (SOUL.md, SHADOW.md, etc.) | | soul_write | Write to user-editable soul files | | soul_status | Get current system status |

Memory

| Tool | Purpose | |------|---------| | memory_save | Save facts, decisions, or lessons | | memory_search | Semantic search across all memories | | memory_journal | Search or browse conversation journals | | memory_recent | List recently saved memories | | memory_stats | Memory system statistics | | recall | Unified "ask anything about the past" search |

</details>

<details> <summary><b>Soul files (in ~/.soul/files/)</b></summary>

| File | Purpose | Managed by | |------|---------|-----------| | SOUL.md | Your identity β€” who you are, how you work | You + Claude | | SHADOW.md | Blind spots and behavioral tendencies | You + Claude | | STORY.md | Timeline of growth and key moments | You + Claude | | CORRECTIONS.md | Patterns to avoid, learned from mistakes | You + Claude | | STATE.md | System telemetry (confidence, phase, counts) | Auto | | FRAMEWORKS.md | Active framework index | Auto |

</details>

<details> <summary><b>Configuration</b></summary>

All settings in ~/.soul/config.json:

{
  "signals": { "enabled": true, "maxLogSizeKb": 50 },
  "reflection": {
    "enabled": true,
    "quickSignalThreshold": 20,
    "deepSignalThreshold": 100,
    "quickModel": "haiku",
    "deepModel": "sonnet"
  },
  "contextBudget": { "maxTokens": 4500 },
  "tensions": { "enabled": true },
  "metaOptimization": { "enabled": true },
  "writeProtection": { "enabled": true }
}

</details>

Philosophy

  1. Evidence over assertion β€” Frameworks earn their place through repeated confirmation.
  2. Local-first β€” No cloud, no accounts, no telemetry.
  3. Invisible when working β€” Extracts signals automatically, reflects in the background.

Contributing

Contributions welcome. Open an issue to discuss before submitting large PRs.

License

MIT

See related servers & alternatives β†’

Related MCP servers

Browse all β†’

Related guides

Hand-picked reading to help you choose and use Developer Tools servers.