cachly-dev/cachly-mcp

Your AI is brilliant for one session. Then it forgets you.

Every morning you re-explain your architecture, your deploy process, the bug you already fixed last week. cachly gives your AI — and your whole team — a permanent, shared brain that gets smarter with every commit.

The story you already live every day

You are a good engineer. You want to ship, not babysit a forgetful assistant.

But every session starts at zero. Your AI doesn't remember the race condition you chased for three hours on Tuesday. It doesn't know your deploy gotchas. It can't tell you that Carol already solved this exact bug in March — because Carol's knowledge lives in Carol's head, and yours in yours.

So you re-explain. You re-research. Your team makes the same mistake in five different branches. And when someone leaves, their hard-won knowledge walks out the door with them.

The villain isn't your AI. It's amnesia. Context death between sessions, and knowledge silos between people. The average developer loses ~45 minutes a day re-establishing context that should already exist.

You don't need a smarter model. You need a memory that doesn't reset — and one that your whole team shares.

Meet your guide

cachly is the brain layer that sits under whatever AI you already use. We've watched hundreds of teams lose the same knowledge the same way, and we built the fix:

• It learns automatically — from every commit, every fix, every session. No extra calls.
• It arrives pre-briefed — your AI opens each session already knowing your stack.
• It's shared — one engineer's solved bug becomes the whole team's reflex.
• It's provable — quality-aware recall beats raw text search by +22.2 % Precision@1 (see the benchmark). A claim without a number is marketing; this is the number.
• It's neutral — speaks MCP, so it works with Claude, Cursor, Copilot, Windsurf, Cline, Zed. Switch models anytime — your brain stays.

We're not the hero of this story. You are. cachly is the thing that makes you the engineer whose AI never forgets and whose team compounds knowledge instead of losing it.

Taste it first — no account, no risk

npx @cachly-dev/mcp-server@latest demo

Run it in any project folder. It reads YOUR git history and shows what your AI would know — your bugs fixed, your patterns, your past decisions. Nothing leaves your machine.

┌─────────────────────────────────────────────────────────────┐
│  Brain Preview — What your AI would know                    │
├─────────────────────────────────────────────────────────────┤
│  Commits: 847   Lessons: 634   Contributors: 7              │
│  Date range: 2024-01-12 → 2026-05-14                        │
├─────────────────────────────────────────────────────────────┤
│  Security fixes your AI would know:                         │
│  • fix(auth): JWT expiry check before signature validation  │
│  • security: sanitize webhook payload before JSON.parse     │
├─────────────────────────────────────────────────────────────┤
│  Bug fixes your AI would remember:                          │
│  • fix: Redis pub/sub race condition under high concurrency │
│  • fix: k8s readinessProbe threshold too low for cold start │
│  • fix: Stripe idempotency_key missing on retry path        │
├─────────────────────────────────────────────────────────────┤
│  With cachly, your AI arrives pre-briefed every session.    │
└─────────────────────────────────────────────────────────────┘

Like what you see? Make it permanent in the next step.

The plan — three steps, then it's automatic

1. Run one command

npx @cachly-dev/mcp-server@latest setup

It signs you in (one browser click, no password, no credit card), detects every AI editor you use, writes the MCP config, seeds your brain from git history, and installs a git hook so it keeps learning.

2. Restart your editor

That's it. From now on your AI arrives pre-briefed — every session.

3. Just work

cachly learns in the background. You never have to "remember to save." Every fix, every commit, every session feeds the brain automatically.

Already inside Claude / Cursor / Copilot? Paste this to your AI and it configures everything itself:

Set up cachly for this project. Run: npx @cachly-dev/mcp-server@latest setup
It gives my AI persistent memory across sessions. Follow the browser login
(one click, no credit card), then restart the editor.

Our agreement with you: Free forever tier. GDPR, EU servers. No model lock-in — leave anytime and take your data. No code content is ever stored.

What changes the moment you turn it on

This is the transformation: from the engineer who re-explains everything every morning → to the team whose collective brain never forgets and gets sharper with every commit.

cachly vs. Claude's built-in memory

Anthropic now ships memory for Claude — and it's genuinely good for one developer, using only Claude, alone. That's not the game we're playing. Here's the honest map:

The honest takeaway: if you're a solo dev who only ever uses Claude, the built-in memory is great — use it. If you work on a team, switch tools, care about proof, or need governance and data residency, that's a gap Anthropic structurally can't close without breaking its own lock-in. That gap is where cachly wins. (Full strategic analysis: STRATEGY.md.)

vs. other memory tools

The standout moves

causal_trace in action:

causal_trace(problem="auth breaks after restart")

→ Root: k8s:namespace-terminating
→ Via:  keycloak:jwks-race
→ Fix:  PollUntilContextTimeout 3min  ← used this March 12, worked

30 minutes of git blame in one call.

What runs automatically after setup

CLI Commands

npx @cachly-dev/mcp-server@latest demo      # Preview your Brain (no account needed)
npx @cachly-dev/mcp-server@latest setup     # Wire up all your AI editors (1–5 minutes)
npx @cachly-dev/mcp-server@latest health    # Check token, API, editors, git hook
npx @cachly-dev/mcp-server@latest digest    # Weekly Brain summary — shareable
npx @cachly-dev/mcp-server@latest share     # Generate a shareable stats card + tweet
npx @cachly-dev/mcp-server@latest badge     # Get a live README badge for your Brain
npx @cachly-dev/mcp-server@latest invite    # Invite a teammate to share your Brain
npx @cachly-dev/mcp-server@latest index .   # Index a project's code into the Brain (CI-friendly)
npx @cachly-dev/mcp-server@latest learn-git # Auto-learn lessons from recent git commits

Tip — auto-learn on every merged PR: run learn-git in CI via the cachly-brain-setup GitHub Action with mode: learn. Each merged PR teaches your Brain automatically.

MCP Tools (100 total)

🧠 Session & Memory (most used)

👥 Team Brain & Org Knowledge Graph

🧬 Causal Intelligence

🌍 Knowledge Commons · ⚙️ Infrastructure · 📋 Roadmap

…and ~70 more. Run health to see what's wired up in your editor.

FAQ

Does my AI need to call session_start manually? No. Sessions start and end automatically on the first tool call and when the editor closes.

How is this different from Claude's built-in memory? Claude's memory is per-user, Claude-only, flat-file, and unbenchmarked. cachly is team-shared, model-neutral (any MCP client), structured + causal, governed, and has a published recall benchmark. See the comparison table above.

Can my whole team share one Brain? Yes — that's the point. team_learn / team_recall, or npx @cachly-dev/mcp-server@latest invite [email protected].

Is my code sent to cachly servers? No code content is stored. cachly stores lesson text, commit messages, session summaries, and key-value context. All data on EU servers, GDPR-compliant.

What is causal_trace and why is it unique? Given any error, it walks the Causal Knowledge Graph to find root cause, intermediate causes, and the exact fix that worked — including date and commands. No other memory system builds or queries a causal graph.

What if I hit the context-window limit mid-session? Call compact_recover. It reconstructs full context from Memory Crystal + recent sessions + WIP registry — typically one tool call.

Manual Setup

{
  "mcpServers": {
    "cachly": {
      "command": "npx",
      "args": ["-y", "@cachly-dev/mcp-server@latest"]
    }
  }
}

{
  "mcpServers": {
    "cachly": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cachly-dev/mcp-server@latest"]
    }
  }
}

{
  "context_servers": {
    "cachly": {
      "command": {
        "path": "npx",
        "args": ["-y", "@cachly-dev/mcp-server@latest"]
      }
    }
  }
}

Pricing

✅ All plans: EU servers · GDPR-compliant · 99.9% SLA · No credit card for Free

Environment Variables

🛠️ Ecosystem & Docs

• 🌐 cachly.dev — Dashboard & free signup
• 📖 Docs — Full documentation
• 📊 BENCH.md — The recall-quality proof
• 🧭 STRATEGY.md · VISION_10X.md · PROGRESS.md
• 💬 GitHub Issues — Bugs & feature requests

Stop re-explaining yourself to your own tools. Give your AI — and your team — a brain that remembers, learns, and gets sharper with every commit.

npx @cachly-dev/mcp-server@latest setup