cachly-dev/cachly-mcp

> **Solve it once. From then on, your AI knows.**
>
> Every fix, every decision and every dead end becomes experience your AI uses at
> the right moment. You build faster, and your team builds on what you figured out.
@cachly-dev/mcp-server connects cachly to Claude Code, Cursor,
GitHub Copilot, Windsurf, Cline, Continue.dev, Zed, Codex CLI and Gemini CLI over
MCP. It offers 124 MCP tools. Your editor lists 27 entries
by default and reaches the rest through one of them, cachly_tool (details under MCP
Tools below). Your AI stores a lesson after a fix, and finds it again when the same
problem returns. Your Brain (the store of your lessons) lives on EU servers.
Start without an account
Claude Code
There is no JSON to write, no path to set and no key to copy. Without a key, cachly creates
a test Brain on EU servers when the session starts (the plugin hook does it; the first tool
call does it if the hook did not). The test Brain has 14 days of
the Dev tier. After that it runs on the free tier with the same key.
Check it with claude mcp list. You should see plugin:cachly-brain:cachly … ✔ Connected.
claude plugin details shows MCP servers (0) even when the server runs, because it
does not count them.
The plugin adds three Claude Code hooks:
| Hook | What it does |
|------|--------------|
| SessionStart | Gives your AI a briefing: last session, open failures, recent lessons |
| UserPromptSubmit | Puts the lessons that match your prompt next to it |
| Stop | Can record a fix while it is fresh |
Turn on auto-update once: /plugin → **Marketplaces** → **cachly** → **Enable auto-update**.
Claude Code leaves it off for marketplaces outside Anthropic's own. The MCP server updates
itself on every start, but the hooks come with the plugin and update only with it. If an
update is waiting, the first session_start of a session says so in one line.
Keep your test Brain
You sign in once in the browser. The test Brain then moves into your account with all
its lessons. Every test key is revoked, and you get a new key that is stored where your
editor and hooks look for it. The Brain restarts once, which takes about 20 seconds.
If you already have a free Brain, the one-Brain limit of the free tier applies and the
move is refused with a message.
Cursor, Windsurf, VS Code, Cline, Continue.dev, Zed
autopilot finds the editors you use and writes the MCP config for each. It adds a git
hook that learns from your commits and fills your Brain from your git history. You sign
in once in the browser (a device code, no password, no credit card), so the Brain
belongs to your own account from the start. Restart your editor afterwards.
You can also add the server by hand (see Manual Setup). Without a key,
the first tool call creates the same test Brain as in Claude Code.
> **Already inside Claude, Cursor or Copilot?** Paste this to your AI:
>
VS Code extension
Install **cachly Brain**.
It creates your Brain on first start, with no account form.
JetBrains plugin
Install **Cachly Brain**
from the JetBrains Marketplace (IntelliJ IDEA, PyCharm, GoLand, WebStorm, Rider). The
status bar, the Brain health and the lessons view live in the IDE. The source is at
cachly-dev/cachly-intellij. The
JetBrains plugin guide shows how Claude Code, Junie
and JetBrains AI Assistant get the Brain over MCP.
MCP Registry
The server is listed in the official
**MCP Registry** as
io.github.cachly-dev/mcp-server. Clients that browse the registry find it by name. The
entry points at this npm package.
Guides
| Guide | What you find there |
|-------|---------------------|
| Claude Code hooks: which event to use when | SessionStart, UserPromptSubmit, PreToolUse, Stop and more, sorted by when they fire. What each one can block, add and change. |
| A UserPromptSubmit hook for Claude Code | The stdin JSON, additionalContext, a working Node script and five traps to avoid. |
| The same hooks in VS Code and Copilot CLI, Codex CLI and Gemini CLI | Which event takes context in each editor, and the exact file setup writes there. |
| Comparisons: Supermemory, Zep, claude-mem, Basic Memory, mem0, Letta | Side by side, each row with its source and a visible date, including when the other product fits better. |
| EU-hosted MCP server: what leaves your machine | Where data lands: storage in Germany, embeddings in the EU, the network edge, and a checklist. |
| Lessons learned for coding agents | How to write a lesson your agent finds again: symptom, decisive fact first, what failed, files, a check. With examples and a LESSONS.md. |