cachly is a persistent AI memory platform for developers. It gives AI coding assistants like Claude Code, Cursor, GitHub Copilot and Windsurf a brain that remembers every lesson, fix, and architecture decision — forever. It connects via the MCP (Model Context Protocol) standard and includes 122 MCP tools. Free tier available. Runs on German (EU) servers.

How does cachly work?

Run 'npx @cachly-dev/mcp-server@latest autopilot' once. The wizard auto-detects every AI editor you have installed (Claude Code, Cursor, Copilot, Windsurf, Cline, Zed) and writes the correct config for each. It then reads your entire git history with brain_from_git and loads years of team knowledge into your Brain before your first session. From that point, sessions start automatically, memory is shared across all your editors simultaneously, and a git post-commit hook teaches cachly from every commit.

Does cachly auto-detect my editors?

Yes. The cachly setup wizard automatically detects Claude Code, Cursor, GitHub Copilot, Windsurf, Cline, Zed, and Continue.dev — any editor that supports MCP. It writes the correct config file for each editor in one pass. You never manually edit JSON config files.

Is memory shared across all my AI editors?

Yes. cachly uses a single Brain that all your AI editors connect to simultaneously. A lesson remembered in Claude Code is instantly available in Cursor and GitHub Copilot. If your team uses different editors, all of you share the same persistent memory pool.

What is brain_from_git?

brain_from_git is a cachly tool that reads your entire git history before your first session and extracts lessons from every commit, PR, and revert. Your AI arrives knowing years of architectural decisions, bug fixes, and team conventions — without you writing a single line of documentation. Zero onboarding.

What is causal_trace?

causal_trace is a cachly tool that traces the history of any file or bug across your entire git history in seconds — replacing 30+ minutes of manual git blame. Describe a problem in plain English. It returns the root cause, the failure chain, and the exact fix that worked — with date, command, and file path.

What is brain_predict?

brain_predict is a cachly tool that scans your Brain for failure patterns before every deploy, migration, or dependency upgrade. It returns probability-weighted warnings based on your team's actual incident history — so you catch the next incident before it happens.

Does cachly work with Claude Code, Cursor, and GitHub Copilot?

Yes. cachly works with Claude Code, Cursor, GitHub Copilot, Windsurf, Cline, Zed, and Continue.dev — anywhere that supports MCP. Run 'npx @cachly-dev/mcp-server@latest autopilot' to configure all editors in one step. Memory is shared across all editors simultaneously.

Can cachly search memory across languages?

Yes. cachly uses semantic vector embeddings, not keyword search. A lesson stored in German appears when you search in English. A fix documented in Arabic matches a Japanese query about the same bug pattern. Supported languages include English, German, French, Spanish, Italian, Portuguese, Japanese, Chinese (Simplified and Traditional), Korean, Arabic, Hebrew, and more.

How is cachly different from mem0?

mem0 is a memory layer for Python LLM apps and chatbots — great for building AI products. cachly is built specifically for developer tooling: it connects to your AI editor via MCP, learns from your git history automatically, predicts failures before deploy, and gives your whole team shared memory. cachly runs on EU servers and is GDPR-native. For developers using Claude Code, Cursor, or Copilot, cachly is the right choice.

Is cachly GDPR compliant?

Yes. cachly runs exclusively on German servers (Hetzner). All data stays in the EU. No data is shared with third parties. cachly is fully GDPR compliant. An AVV (Auftragsverarbeitungsvertrag / Data Processing Agreement) is available for Business and Enterprise customers.

We're the #1 MCP memory server on npm

The numbers (May 23, 2026)

npm package	Weekly installs
@cachly-dev/mcp-server	472
mcp-memory-ts	27
memory-mcp-lite	20
codex-mcp-memory-server	19
mag-memory	17

Source: npm registry downloads API, May 16–22, 2026.

That's 5.7× the runner-up, and more than the next four memory-focused MCP servers combined.

The first real users showed up this week

We hit a stranger milestone this week than the npm one. A real human we don't know found cachly, signed up, and used it. Then a second one subscribed to the newsletter from a different country. No launch post, no Show HN, no Product Hunt. They each got there through search and MCP discovery.

We've been writing about cachly for two months. This week was the first time we got to watch our own product receive the kind of quiet, unprompted signups that mean: this solves a real problem for someone.

What we think drove the lead

1. We picked one job and did it ridiculously well

The other memory MCPs are general key-value stores or vector databases with an MCP wrapper. cachly does one job: make your AI act like it remembers yesterday. Every tool, every default, every doc page is pointed at that outcome.

That focus shows up in concrete features: causal_trace walks the Causal Knowledge Graph to find the actual root cause of a bug. memory_crystalize distills 200 lessons into a briefing your AI can absorb in one tool call. brain_predict warns the AI before a known failure pattern is about to repeat. None of those exist in the other memory MCPs.

2. Zero-friction onboarding

The single biggest growth lever: npx @cachly-dev/mcp-server@latest autopilot detects every installed editor (Claude Code, Cursor, Windsurf, Cline, VS Code, Copilot, Zed) and writes the MCP config for each of them automatically. No copy-paste. No JSON editing. The OAuth device-flow login takes one browser click — no password, no API token to copy.

We measured significant drop-off improvements when users switched from manually editing JSON to our init wizard.

3. Ambient learning — the AI never asks the user to remember

Every other memory system has the same flaw: it asks the user (or the AI) to explicitly call save_memory(). That never works in practice. AIs don't remember to remember.

cachly turned this inside out. We install a git post-commit hook during setup. Every commit auto-extracts a lesson. Every session_end fires automatically when the editor closes. Every session_start automatically loads relevant past lessons before the AI even responds to the user.

The result: 1,247 lessons stored per month per active brain on average. The next-closest memory MCP, when we tested with the same user, stored 0 — because the AI never called the save tool.

4. We shipped on the right calendar

2026 is the year “context engineering” replaced “prompt engineering” as the headline skill. Every major editor — Claude Code, Cursor, Windsurf, Zed — added MCP support in the last six months. Anthropic published the official MCP registry in March. Developers started searching for “mcp memory” and “persistent context” at 4× the rate of January.

We didn't cause the wave. We were just early enough to put a really good package at the top of the npm search results when the wave hit.

What didn't work

Twitter / X: zero qualified installs. The developer crowd uses MCP servers but doesn't go to Twitter to find them.
The cache pitch: cachly began life as a semantic cache. Nobody's LLM bill was a problem yet. The memory pivot in April was the unlock.
Generic “AI for developers” framing: too broad, doesn't survive the npm search filter. “Memory for Claude Code” converted 6× better.

What's next

We shipped @cachly-dev/[email protected] alongside this post: 84 verified tools, 350 passing tests, a tightened description for npm search, and 20 new keywords aimed at the 2026-era search vocabulary (context-engineering, agent-memory, long-term-memory, rag-memory).

We're also opening up the Knowledge Commons — verified lessons that any cachly user can publish (with provenance) and any other cachly user can import. The first cross-team brain transfer happened last Thursday. We'll write that one up separately.

Try it

One command. No credit card. No expiry.

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

Or read the full docs first.