Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Solve it once. From then on, your AI knows. Experience for coding agents, hosted in the EU.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"cachly-dev": {
"command": "npx",
"args": [
"-y",
"@cachly-dev/mcp-server"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add cachly-dev -- npx -y @cachly-dev/mcp-serverIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"cachly-dev": {
"command": "npx",
"args": [
"-y",
"@cachly-dev/mcp-server"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"cachly-dev": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cachly-dev/mcp-server"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto cachly-dev bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.10.231) kam gestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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.
/plugin marketplace add cachly-dev/cachly-mcp
/plugin install cachly-brain@cachly
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 Solo 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 short briefing: the 5 most-reused lessons (on a new Brain: starter tips) |
UserPromptSubmit | Puts the lessons that match your prompt next to it |
Stop | Saves a lesson when the AI's last message clearly reports a fix. It skips messages that say something failed or is unclear. It tells you nothing when it saves. |
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.
npx @cachly-dev/mcp-server@latest claim
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.
npx @cachly-dev/mcp-server@latest autopilot
autopilot finds the editors you use and writes the MCP config for each. It also writes the rule file each editor reads in every chat (CLAUDE.md, AGENTS.md, .cursor/rules/cachly.mdc, .github/copilot-instructions.md, .windsurfrules, .clinerules; GEMINI.md, .junie/guidelines.md and .continue/rules/cachly.md where you use Gemini CLI, Junie or Continue), which tells your AI to check its memory before a task. 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. Without a rule file, Claude Code still starts each task with smart_recall, because the server's instructions ask for it. Gemini CLI also passes them on. Some editors do not (Cline, Continue and Zed, for example); there, the rule file from autopilot is what makes your AI use its memory.
Already inside Claude, Cursor or Copilot? Paste this to your AI:
`
Set up cachly for this project. Run: npx @cachly-dev/mcp-server@latest autopilot
Follow the browser sign-in, then restart the editor.
`
Install [cachly Brain](https://marketplace.visualstudio.com/items?itemName=cachly-dev.cachly-brain). It creates your Brain on first start, with no account form.
Install [Cachly Brain](https://plugins.jetbrains.com/plugin/32059-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.
The server is listed in the official [MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=cachly) as io.github.cachly-dev/mcp-server. Clients that browse the registry find it by name. The entry points at this npm package.
| 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. |
| JetBrains plugin guide | What the plugin does, and how Claude Code, Junie and JetBrains AI Assistant use the Brain. |
| Repo X-ray | Enter a public GitHub repo. In a few seconds you see how many problems its team has solved, and which ones more than once. |
smart_recall looks up the lessons that match. It combines keyword search (BM25), meaning-based search and the causal graph, in 11 languages.causal_trace walks from the symptom to the cause and to the fix that worked.brain_predict lists failure patterns from past incidents.To see what your AI would know before you install anything, run npx @cachly-dev/mcp-server@latest demo in a project folder. It reads your git history and prints your fixes, patterns and decisions. Nothing leaves your machine.
Our agreement with you. You can leave and take your data: npx @cachly-dev/mcp-server@latest export writes every lesson to lessons.md (to read) and lessons.jsonl (to reuse). Code excerpts are stored only if you call index_project yourself, and only on your own EU instance. Read what leaves your machine before you decide.
Your editor sees 27 entries by default: the daily tools (26 of them) and one dispatcher, cachly_tool. This is on purpose. The full list of 124 costs about 28,000 tokens in every request. The 27 listed entries cost about 8,000. All other tools (98 of them) run through the dispatcher:
cachly_tool(tool: "team_roster") run any of them by name
cachly_tool(tool: "team_roster", describe: true) get its schema first
Nothing is unreachable. The server dispatches by name, so team_roster called directly still works. Set CACHLY_ALLE_WERKZEUGE=1 to list all 124. Set CACHLY_PROFILE=lean to list 8 plus cachly_tool, or CACHLY_PROFILE=recall to list the 3 read-only tools.
| Tool | What it does |
|---|---|
| `session_start` | Full briefing: last session, open failures, recent lessons, Brain health |
| `session_end` | Save what you built; extract lessons from the summary and the git log |
| `learn_from_attempts` | Store a structured lesson after any fix, deploy or discovery (with author, visibility) |
| `recall_best_solution` | The known fix for a topic, with its success and failure history |
| `smart_recall` | Hybrid BM25 + semantic + causal-graph search, 11 languages, quality-reranked |
| `remember_context` | Keep architecture findings, decisions and file summaries |
| `compact_recover` | Recover your context after you hit the context-window limit |
| Tool | What it does |
|---|---|
team_learn / team_recall | Share lessons across the team with author attribution |
team_confirm | A reviewer confirms a lesson (senior or peer); confirmed lessons rank higher in recall |
team_assign_role / team_roster / team_whoami | Roles (admin, reviewer, contributor, viewer), enforced once an admin is set |
team_audit | Admin-only governance trail: every role change and lesson confirmation |
| `brain_who_knows` | Find your team's experts on a topic, ranked from authorship |
| `brain_file_map` | Experts and lessons per file, before you touch it |
| `team_expertise_map` | The team's skills matrix in one table |
| `brain_collab_pairs` | Who works with whom, with bus-factor alerts |
| `brain_portability` | Config snippets for 7 MCP clients, so the same Brain serves any model |
| `skill_gaps` | Knowledge blind spots: unresolved failures, missing attribution |
| `brain_coverage` | A 0–100 health score for the knowledge of your codebase |
madc_deliberate | Specialist AI agents vote to resolve contradictory lessons |
memory_crystalize | Distill all lessons into a Crystal for instant team context |
team_crystallize | A Team Crystal: fixes that 2 or more teammates reached independently |
| Tool | What it does |
|---|---|
| `causal_trace` | Root-cause analysis through the causal knowledge graph |
`brain_predict` / brain_predict_failures | Predict likely failures before they happen |
| `brain_from_git` | Fill people, file
Nur der Anfang wird gezeigt; den Rest findest du im Repo