Cachly Dev

io.github.cachly-devPublished by GitHub account cachly-devv0.10.231Updated Nov 6, 2026

Solve it once. From then on, your AI knows. Experience for coding agents, hosted in the EU.

Overview

AI-generated overview

Cachly Dev gives coding assistants a persistent, EU-hosted memory of past fixes, decisions and pitfalls, plus a semantic cache and project roadmap.

What you can do
  • Recall and search stored lessons, context and brain data by keyword, meaning or causal chain
  • Store lessons after fixes, save and recall context, and delete stale entries
  • Run session briefings, session summaries and handoffs between chat windows
  • Manage a persistent project roadmap: add, update, list and pick the next item
  • Read and write key-value cache entries and semantically search cached entries
  • Index local source files and bootstrap lessons from git history or CI outcomes
When to use it
Useful for teams and solo developers who want an assistant to reuse knowledge across sessions and editors instead of re-reading the codebase, and who want known fixes surfaced before debugging, deploys or migrations.
Requirements
Runs locally over stdio via npx, so Node.js is needed. A Brain instance is created automatically on the first tool call without an account; signing in through the browser or setting CACHLY_JWT and CACHLY_BRAIN_INSTANCE_ID ties it to your own account. Network access to the hosted backend is required; optional embedding providers use OLLAMA_BASE_URL, OPENAI_API_KEY, GEMINI_API_KEY, MISTRAL_API_KEY or COHERE_API_KEY.
Before you install
Lesson text, commit messages, session summaries and key-value context are stored on the vendor's EU servers, and API traffic passes through Cloudflare. Code excerpts leave the machine only if index_project is called. autopilot writes editor configs, rule files and a git hook, and autopilot-style tools can overwrite an existing file at the target path. Telemetry pings include the API token and short smart_recall queries unless CACHLY_NO_TELEMETRY is set. Paid tiers exist above the free tier.

Installation

In SourceWeft

  1. Open Cachly Dev in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

cachly — experience for coding agents (MCP server)

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.

[npm version] [License: Apache-2.0]

@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

/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:

HookWhat it does
SessionStartGives your AI a short briefing: the 5 most-reused lessons (on a new Brain: starter tips)
UserPromptSubmitPuts the lessons that match your prompt next to it
StopSaves 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.

Keep your test Brain

bash
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.

Cursor, Windsurf, VS Code, Cline, Continue.dev, Zed

bash
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 autopilotFollow the browser sign-in, then restart the editor.

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

GuideWhat you find there
Claude Code hooks: which event to use whenSessionStart, UserPromptSubmit, PreToolUse, Stop and more, sorted by when they fire. What each one can block, add and change.
A UserPromptSubmit hook for Claude CodeThe 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 CLIWhich event takes context in each editor, and the exact file setup writes there.
Comparisons: Supermemory, Zep, claude-mem, Basic Memory, mem0, LettaSide 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 machineWhere data lands: storage in Germany, embeddings in the EU, the network edge, and a checklist.
Lessons learned for coding agentsHow 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 guideWhat the plugin does, and how Claude Code, Junie and JetBrains AI Assistant use the Brain.
Repo X-rayEnter a public GitHub repo. In a few seconds you see how many problems its team has solved, and which ones more than once.

How it works

  1. A fix, a decision or a dead end is stored as a lesson: topic, what worked, what failed, severity, file paths, commands and author.
  2. At the start of a session, your AI receives a briefing with the last session, open failures and recent lessons.
  3. When you ask for something, smart_recall looks up the lessons that match. It combines keyword search (BM25), meaning-based search and the causal graph, in 11 languages.
  4. When an error appears, causal_trace walks from the symptom to the cause and to the fix that worked.
  5. Before a deploy, brain_predict lists failure patterns from past incidents.
  6. A git hook and the CI templates add lessons from commits and from red-to-green runs.
  7. Lessons are shared in the team. Each one carries the name of whoever learned it.

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.

MCP Tools (124 total, 27 listed by default)

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 namecachly_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.

Session and lessons (most used)

ToolWhat it does
session_startFull briefing: last session, open failures, recent lessons, Brain health
session_endSave what you built; extract lessons from the summary and the git log
learn_from_attemptsStore a structured lesson after any fix, deploy or discovery (with author, visibility)
recall_best_solutionThe known fix for a topic, with its success and failure history
smart_recallHybrid BM25 + semantic + causal-graph search, 11 languages, quality-reranked
remember_contextKeep architecture findings, decisions and file summaries
compact_recoverRecover your context after you hit the context-window limit

Team Brain and org knowledge graph

ToolWhat it does
team_learn / team_recallShare lessons across the team with author attribution
team_confirmA reviewer confirms a lesson (senior or peer); confirmed lessons rank higher in recall
team_assign_role / team_roster / team_whoamiRoles (admin, reviewer, contributor, viewer), enforced once an admin is set
team_auditAdmin-only governance trail: every role change and lesson confirmation
brain_who_knowsFind your team's experts on a topic, ranked from authorship
brain_file_mapExperts and lessons per file, before you touch it
team_expertise_mapThe team's skills matrix in one table
brain_collab_pairsWho works with whom, with bus-factor alerts
brain_portabilityConfig snippets for 7 MCP clients, so the same Brain serves any model
skill_gapsKnowledge blind spots: unresolved failures, missing attribution
brain_coverageA 0–100 health score for the knowledge of your codebase
madc_deliberateSpecialist AI agents vote to resolve contradictory lessons
memory_crystalizeDistill all lessons into a Crystal for instant team context
team_crystallizeA Team Crystal: fixes that 2 or more teammates reached independently

Causal intelligence

ToolWhat it does
causal_traceRoot-cause analysis through the causal knowledge graph
brain_predict / brain_predict_failuresPredict likely failures before they happen
brain_from_gitFill people, files and lessons from git history, incrementally
brain_from_ciBulk-ingest CI outcomes: red→green becomes a fix lesson with a causal fixes edge, green→red a causes edge
memory_consolidateDetect contradictions, merge duplicates, expire stale lessons
ckg_inspectInspect the causal graph around a concept

Example:

causal_trace(problem="auth breaks after restart")
→ Root: k8s:namespace-terminating→ Via:  keycloak:jwks-race→ Fix:  PollUntilContextTimeout 3min

Shareable and public Brains

ToolWhat it does
brain_seed_starterSeed 16 universal lessons so your first smart_recall finds something; runs on a fresh repo
brain_sharePublish a Brain snapshot as a link (public or unlisted). For your own data, run npx @cachly-dev/mcp-server export
brain_importImport a shared Brain into yours: topic_prefix, min_confidence, dry_run
brain_share_list / brain_unshareList your shares; revoke one so the link goes dead
brain_discoverSearch the Brain marketplace for ready-made knowledge bases

Knowledge Commons, infrastructure and roadmap

ToolWhat it does
syndicate / fedbrain_searchContribute to, and search, the global Knowledge Commons
brain_marketplace / brain_installBrowse and install curated Domain Brains (Kubernetes, Auth, databases)
cache_get / cache_set / semantic_search / index_projectCache and semantic operations. Pass org_id on cache_get / cache_set to share the cache org-wide
cache_stats / cache_org_statsHits, estimated USD saved and a monthly projection, per instance or across your org
list_instances / create_instance / delete_instanceManage Brain instances
roadmap_add / roadmap_nextA project roadmap stored in the Brain

Run health to see what is wired up in your editor. The full catalog is generated from src/tools.ts.

CLI commands

bash
npx @cachly-dev/mcp-server@latest autopilot # One command: signs in, configures every editor, fills the Brain from git

Every command below runs as npx @cachly-dev/mcp-server@latest <command>. Key and Brain instance come from the environment or from ~/.cachly/credentials.json, the file autopilot writes.

Every day
statusLessons, recalls and team at a glance
ambient-statsTokens injected vs saved — the honest net, even when negative
doctorDiagnose a broken or missing install, with the fix for each step
healthCheck key, API, editor configs and git hook
digestWhat your Brain learned this week, shareable
Set up
demoPreview your Brain from git history (no account needed)
setup (alias autosetup)Interactive variant: pick editors yourself
init --editor <id>Write the config for one editor, with flags
claimMove a test Brain into your account, lessons included
upgradeCheck for updates
uninstallTake cachly out of this project again. Shows your numbers first, then the plan; --dry-run only lists, --global adds the home folder
Your data
exportWrite every lesson to lessons.md and lessons.jsonl
index [dir]Index a project's code into the Brain (CI-friendly)
learn-git [repo]Learn lessons from recent git commits
Team & sharing
invite [email]Invite a teammate to share your Brain
join <token>Accept a Brain invite
shareGenerate a shareable stats card
publishPublish your Brain as an importable link (--public)
badgeGet a live README badge for your Brain
More
benchRun the recall benchmark (no sign-in needed)
tool-specs / openapiTool definitions for other agent frameworks (OpenAI, Anthropic, LangChain, OpenAPI)

The method behind bench is described in BENCH.md.

Tip: learn from every merged PR. Run learn-git in CI with the cachly-brain-setup GitHub Action and mode: learn. Each merged PR then teaches your Brain.

CI integration

Every CI run is a lesson. A red→green transition is a proven fix, and a green→red one is a known cause. Ready-to-paste templates live in src/ci-integration/:

  • GitHub Actions: use cachly-dev/cachly-action. It needs the secrets CACHLY_API_KEY and CACHLY_BRAIN_INSTANCE_ID.
  • GitLab CI: pull in the GitLab template with include: remote:. It adds hidden jobs for learn, scan, confirm and hygiene; extend the ones you want.
  • Anything else: push-ci-outcome.mjs is a standalone Node.js helper with no dependencies. It always exits 0, so your CI never fails because of a Brain push.

Already have months of CI history? The brain_from_ci tool ingests past outcomes in one call, the way brain_from_git ingests commits.

FAQ

Does my AI need to call session_start by hand? No. A session starts on the first tool call and ends when the editor closes.

Can my whole team share one Brain? Yes. Use team_learn and team_recall, or npx @cachly-dev/mcp-server@latest invite [email protected].

Is my code sent to cachly servers? Only if you call index_project yourself. It stores a short excerpt (up to summary_chars, 1200 characters by default) per indexed file, on your own EU instance. Every other tool stores lesson text, commit messages, session summaries and key-value context, but no source code. Storage is in Germany and embeddings are computed in the EU. API traffic passes through Cloudflare, a US company. The EU guide lists every data flow.

What is causal_trace? Given an error, it walks the causal knowledge graph to find the root cause, the intermediate causes and the fix that worked, with its date and commands.

What if I hit the context-window limit mid-session? Call compact_recover. It rebuilds your context from the Crystal, the recent sessions and the registry of work in progress. Usually one tool call is enough.

How do I write lessons my agent finds again? Lead with the decisive fact. The lessons guide shows how, with examples.

Editor support matrix

npx @cachly-dev/mcp-server@latest autopilot detects and configures the editors below. Manual snippets are in Manual Setup.

Editor / clientAuto-setupConfig file writtenGlobal configNotes
Claude Codeyes.mcp.jsonwith the pluginWithout a key: test Brain at session start (plugin) or on the first tool call; browser sign-in only as fallback
Cursoryes, detected via .cursor/.cursor/mcp.json, hooks in .cursor/hooks.jsonnoProject-level; restart Cursor after setup. Lessons arrive with the first tool call of a turn
Windsurfyes, detected via .windsurf/.windsurf/mcp.jsonnoProject-level; restart Windsurf after setup
VS Code + Copilotyes, detected via .vscode/.vscode/mcp.json, hooks in .github/hooks/cachly-ambient.jsonnoNeeds the VS Code MCP support or Copilot chat. Briefing at session start, lessons before each prompt
Codex CLIyes, detected via ~/.codex.codex/config.toml ([mcp_servers.cachly]), hooks in .codex/hooks.jsonnoCodex loads both once you trust the folder; confirm the hook once in /hooks
Gemini CLIyes, detected via ~/.geminimcpServers.cachly and hooks in .gemini/settings.jsonnoGemini loads both once you trust the folder. Lessons are appended to the prompt (BeforeAgent)
Clineyes, detected via VS Code.vscode/mcp.jsonnoShares the config with Copilot; restart VS Code
Continue.devyes, detected via .continue/.continue/config.jsonnoUses the modelContextProtocolServers key
Zedyes, detected via .zed/.zed/settings.jsonnoUses the context_servers key
Windsurf (global)autosetup --editor windsurf~/.windsurf/mcp.jsonyesPass --editor to target the global config
Any other MCP clientautosetup --editor claude.mcp.jsonnoStandard mcpServers stdio format

Which sign-in path each case uses:

ScenarioPath
autosetup or autopilot from a terminal (TTY)OAuth device flow: one click in the browser, the API key is saved automatically
autosetup from a VS Code task or CI (no TTY)Detects the non-interactive run, opens the browser with a step-by-step guide, prints the CACHLY_JWT=... autosetup command
First tool call without any keyTest Brain: an anonymous Brain on EU servers. The key is saved to ~/.cachly/credentials.json, and the call goes through. If that fails (offline, rate limit), the inline device flow starts with a URL and a code
First tool call with CACHLY_BRAIN_INSTANCE_ID set but no keyInline device flow. You already have a Brain, so no second account is created
CACHLY_JWT=cky_live_xxx npx ... autosetupSkips the sign-in step and uses the key you pass

Manual Setup

Claude Code (.mcp.json in the project)
json
{  "mcpServers": {    "cachly": {      "command": "npx",      "args": ["-y", "@cachly-dev/mcp-server@latest"]    }  }}

For all your projects at once, use the plugin above, or claude mcp add -s user cachly -- npx -y @cachly-dev/mcp-server@latest (Claude Code stores that in ~/.claude.json).

Without a key, the first tool call creates a test Brain on EU servers. No sign-up. Run npx @cachly-dev/mcp-server@latest autopilot to use your own account instead.

Cursor / Windsurf / VS Code / Copilot / Cline
json
{  "mcpServers": {    "cachly": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@cachly-dev/mcp-server@latest"]    }  }}
Zed (.zed/settings.json)
json
{  "context_servers": {    "cachly": {      "command": {        "path": "npx",        "args": ["-y", "@cachly-dev/mcp-server@latest"]      }    }  }}

Self-hosting and bring-your-own embeddings

Embeddings turn text into vectors for the meaning-based search. By default, cachly computes them on its own servers in the EU as soon as you are signed in. Your text goes to a third-party provider only when you name that provider yourself:

ProviderEnv varsModel
cachly (default, EU servers)none beyond your keymanaged
Ollama (local)OLLAMA_BASE_URL, detected automaticallynomic-embed-text
OpenAICACHLY_EMBED_PROVIDER=openai and OPENAI_API_KEYtext-embedding-3-small
Google GeminiCACHLY_EMBED_PROVIDER=gemini and GEMINI_API_KEYtext-embedding-004
MistralCACHLY_EMBED_PROVIDER=mistral and MISTRAL_API_KEYmistral-embed
CohereCACHLY_EMBED_PROVIDER=cohere and COHERE_API_KEYembed-english-v3.0

Run npx @cachly-dev/mcp-server@latest health to see which provider is active.

Point at your own backend. Every install can talk to a private backend instead of api.cachly.dev:

bash
# One command: run the setup against your self-hosted backendnpx @cachly-dev/mcp-server@latest autopilot --api-url https://cachly.mycorp.internal
# Or without promptsnpx @cachly-dev/mcp-server@latest autosetup \  --instance-id <uuid> --api-key <cky_live_...> \  --api-url https://cachly.mycorp.internal

autosetup writes CACHLY_API_URL into the editor config only when it differs from the default cloud. Default installs stay clean, and self-hosted installs keep talking to your backend on every editor start.

Pricing

Current prices and limits are on cachly.dev/pricing.

TierStoragePriceBrains
Free25 MB€0/mo1
Dev200 MB€19/mo3
Pro900 MB€49/mo, 5 seats10
Business7 GB€199/mo25

The free tier needs no credit card.

Environment Variables

VariableDefaultDescription
CACHLY_JWTnoneAPI key. The setup wizard sets it for you
CACHLY_BRAIN_INSTANCE_IDnoneDefault Brain UUID. Optional, it is resolved automatically
CACHLY_API_URLhttps://api.cachly.devOverride for a self-hosted backend
CACHLY_EMBED_PROVIDERautomaticName an embedding provider yourself (see above)
CACHLY_ALLE_WERKZEUGEunsetSet to 1 to list all 124 tools instead of 27
CACHLY_PROFILEunsetlean lists 8 tools plus cachly_tool, recall lists the 3 read-only tools
CACHLY_UPDATE_CHECKonSet to false to stop the version check. npm is asked at most once a day, with a 2-second limit
CACHLY_NO_TELEMETRYunsetSet to 1 to disable usage pings. They include your API token and up to 80 characters of smart_recall queries
CACHLY_LERNENonLearning from use in the prompt hook. For 5 % of prompts the matching lessons are computed but not shown (control group), up to 10 % try a stricter or shorter setting. At the end of each turn the hook reports which setting ran and whether the agent named a shown lesson; topics are sent hashed, prompts never. Set to 0 (or CACHLY_NO_TELEMETRY=1) to turn it off
CACHLY_KONTROLLE_ANTEIL5%Share of prompts in the control group. 0 turns the control group off, at most 50%
CACHLY_ERKUNDUNG10%Share of prompts that may try another setting. 0 keeps the leading setting, at most 10%

Ecosystem and docs

PackageWhat it does
@cachly-dev/mcp-serverThis server, for Claude Code, Cursor, Copilot, Windsurf, Cline and Zed
Cachly Brain for VS CodeStatus bar, lessons view and ambient learning in the editor
Cachly Brain for JetBrainsThe same Brain in IntelliJ IDEA, PyCharm, GoLand, WebStorm and Rider
@cachly-dev/openclawSemantic caching for LLM calls in JS/TS apps
cachly-dev/cachly-actionGitHub Action: setup, PR risk scan, learning from merged PRs, weekly hygiene

The VS Code extension shows the same Brain in the editor:

[The Lessons view inside the Cachly Brain VS Code extension, listing six stored lessons]


Solve it once. From then on, your AI knows.

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

Source: README.md at commit ac4de15

Tools

27

cache_get

Get a value from a running cache instance by key. Returns the stored value (string or deserialized JSON object) or null if the key does not exist or has expired. Read-only — no side effects. Use cache_mget when you need multiple keys in one round-trip. Use cache_exists to check existence without retrieving the value. Use semantic_search when you need fuzzy/vector search across stored values.

Parameterskeyrequiredorg_idinstance_id

cache_set

Set a key-value pair in a running cache instance. Overwrites any existing value at the key — not idempotent for new data. Returns "OK" on success; returns an error if the instance_id is invalid or the instance is paused. Value can be a string or a JSON-serialized object. Optionally set a TTL in seconds (omit for no expiry). Use cache_mset instead for setting multiple keys in a single pipeline round-trip. Use cache_stream_set instead for caching LLM token streams (ordered string chunks).

Parameterskeyrequiredttlvaluerequiredorg_idinstance_id

index_project

Index local source files into the cachly semantic cache so AI assistants can use semantic_search to find relevant files instead of re-reading the whole codebase every time. Walks a directory recursively, reads each matching file, and stores a summary + path as a semantic cache entry (prompt = file path + content excerpt, value = relative path). Requires an embedding provider (OPENAI_API_KEY or CACHLY_EMBED_PROVIDER + key). Run once, then re-run after major refactors. TTL=86400 (24h) keeps entries fresh.

Parametersdirrequiredttlmax_filesnamespaceextensionsinstance_idsummary_chars

remember_context

Save context information to the cache so you can recall it later without re-computing. Perfect for caching: codebase overviews, file summaries, project structure, frequently-accessed data, or "thinking" results like dependency analysis. The AI assistant can use this to avoid re-reading the entire codebase every time. Overwrites any existing value stored under the same key. Returns { key, stored_at, ttl } confirming the saved context. Example: remember_context("project overview", "This is a Next.js app with...") then later: recall_context("project overview"). Use recall_context to retrieve; use list_remembered to see all stored keys.

Parameterskeyrequiredttlcontentrequiredcategoryinstance_id

recall_context

Retrieve previously saved context from the cache. Returns the saved content or null if not found. Use this at the START of any task to check if you already have relevant context cached, before doing expensive operations like reading many files. Supports glob patterns: "file:*" matches all file summaries, "arch*" matches architecture-related keys.

Parameterskeyrequiredinstance_id

list_remembered

List all cached context entries for this project. Shows what knowledge the AI assistant has already cached, so you can decide whether to recall existing context or refresh it. Returns: key, category, size, TTL remaining, and a content preview.

Parameterslimitcategoryinstance_id

forget_context

Delete one or more cached context entries. Use when context is stale or you want to force a fresh analysis. Supports glob patterns: "file:*" deletes all file summaries.

Parameterskeysrequiredinstance_id

learn_from_attempts

Store a lesson AFTER any non-trivial task (deploy, debug, fix, decision); future sessions recall it. instance_id may be omitted; the configured instance is used — never guess one. If the topic already exists, the write is an UPDATE and REQUIRES `grund` (one line: WHY the previous version was wrong) — without it the update is rejected. A conflicting outcome triggers a contradiction warning. Example: learn_from_attempts(topic="deploy:api", outcome="success", what_worked="PORT 3095 SERVES WHISPER — nohup docker compose up -d", severity="critical")

Parameterstagsgroupgrundtopicrequiredauthorcontextersetztgilt_aboutcomerequiredservicecommandsseverity+8 more

recall_best_solution

Recall the best known solution for a topic from past lessons. Call this BEFORE attempting any task that might have been done before. Returns the most recent successful lesson for the topic, with confidence indicator. ⚠️ badge = lesson is >5d old (verify before applying). 🔴 = >10d old (likely stale!). Recalling a lesson resets its confidence clock to 1.0 (marks as recently verified). A superseded lesson shows a banner naming its successor; if the successor was deleted, the banner says so and the lesson counts as the best remaining answer. Example: recall_best_solution(topic="deploy:web") → returns the working deploy command.

Parameterstopicrequiredauthorinstance_id

smart_recall

Returns the fixes, decisions and pitfalls this team already learned for the task at hand. Call it FIRST at the start of every coding task — before reading files or editing — with one line about the task, e.g. smart_recall("fix login redirect loop"). Finds lessons by meaning, not exact words. instance_id may be omitted; the configured instance is used — never guess one. Falls back to remember_context keys if no semantic match is found.

Parameterslimitqueryrequiredauthorthresholdinstance_idcontext_files

session_start

Single-call session briefing for the START of a session: last summary, recent lessons, health. It does not replace smart_recall for a concrete task. Returns: last session summary, recent lessons sorted by recency, relevant lessons for your focus area, brain health stats (counts of open failures and stale lessons), team telepathy (what teammates learned this week), predictive pre-warnings (if your focus area has known failure patterns), and memory crystals (compressed wisdom from old sessions). Also saves a session start marker so session_end can compute duration.

Parametersfocusauthorproviderinstance_idworkspace_path

session_end

Save a session summary when you finish working. Records what was accomplished, files changed, and lesson count. The next session_start will show this summary as "Last session". Call this when ending a work session, before going idle, or before summarizing. Ambient Learning: if workspace_path is provided, reads git log since session start and auto-learns from commits.

Parameterssummaryrequiredinstance_idfiles_changedworkspace_pathlessons_learned

session_handoff

Save a detailed handoff for the NEXT chat window / session. Stores: current progress, TODO list (done + remaining), changed files with descriptions, instructions for the next assistant, and any incomplete work. The next session_start automatically includes this handoff so the new window knows EXACTLY what happened and what remains. Call this BEFORE closing a chat window, especially if work is incomplete. This prevents the "continue" problem where new windows lose context, skip tasks, or produce broken code.

Parametersblocked_oninstance_idinstructionsfiles_changedcompleted_tasksrequiredcontext_summaryremaining_tasksrequired

team_learn

Store a lesson in a shared team brain so all team members benefit. Like learn_from_attempts, but REQUIRES an author name for attribution. Shows up in team_recall with "by <author>" so the team knows who learned it.

Parameterstagstopicrequiredauthorrequiredoutcomerequiredcommandsseverityfile_pathsinstance_idwhat_failedwhat_workedrequired

team_recall

Recall lessons from a shared team brain, showing who learned what. Works on any shared instance (all team members using the same instance_id). Shows author, recency, and severity for each lesson. Use this to onboard new team members or find who knows about a topic.

Parameterslimittopicauthorinstance_id

roadmap_add

Add a new item to the persistent project roadmap stored in the Brain. Items survive across sessions and editors — the roadmap is always up to date. Use for features, bugs, refactors, or any planned work. Call roadmap_list to see all open items, roadmap_next to get the next actionable item.

Parameterstagstitlerequiredprioritymilestonedescriptioninstance_id

roadmap_update

Update the status, priority, or details of a roadmap item. Use to move items through the lifecycle: planned → in-progress → done (or blocked/cancelled). Also use to add notes/findings while working on an item.

Parametersidrequirednotestitlestatusprioritydescriptioninstance_id

roadmap_list

List all roadmap items, optionally filtered by status, priority, tag, or milestone. Returns items sorted by priority then creation date. Called automatically by session_start to show open work.

Parameterstagstatusprioritymilestoneinstance_id

roadmap_next

Get the single most important next actionable roadmap item. Returns the highest-priority in-progress item first, then planned items, sorted by priority. Call at session start to immediately know what to work on next.

Parameterstaginstance_id

brain_doctor

Check the health of your AI Brain and get actionable recommendations. Reports: lesson count, context entries, last session age, open failures, quality score, effective IQ boost, stale index. Returns a prioritized list of issues with fix instructions.

Parametersinstance_idworkspace_path

causal_trace

Root Cause Analysis through memory: given a problem description, traces the causal chain from root cause through intermediate failures to the current symptom, then surfaces the exact solution that worked before. Read-only — does not modify any stored data. Requires prior learning: brain must have lessons stored via learn_from_attempts or brain_from_git. Returns an ordered chain of concepts with confidence scores plus the matching solution; returns an empty chain with a message if no causal path is found. Example: causal_trace(problem="auth breaks after restart") → "Root: k8s:namespace-terminating → keycloak:jwks-race → Solution: PollUntilContextTimeout 3min". Use recall_best_solution for direct topic lookup, syndicate_search for community patterns, and causal_trace when you have a symptom and need the full root-cause chain.

Parameterstagsproblemrequiredmax_depthinstance_id

autopilot

Generate a CLAUDE.md / copilot-instructions.md that makes any AI self-managing forever. Writes a configuration file to disk — will overwrite an existing file at the target path. No auth required beyond a valid instance_id. The generated file instructs Claude, Cursor, Copilot, Windsurf, or Gemini to automatically call session_start at window open, learn_from_attempts after every fix, and session_end before closing — without being asked. Returns the generated file content as a string and the path where it was written. Use style="minimal" for just the three hooks; style="full" for the complete ruleset with examples. One command. Every AI. Always on. Use setup_ai_memory instead if you want an interactive one-shot setup that also creates an instance.

Parametersstyleeditorinstance_idproject_name

brain_predict

READ-ONLY — no side effects, no writes, no external network calls. Predictive Pre-fetch Engine (PPE): given your current context, reads the CKG in your Redis instance to predict likely failures and return the highest-confidence fixes. "Pre-load" means results are returned inline — nothing is cached or persisted. Requires a valid instance_id (your Redis brain). No rate limits. Call at session start when working on a specific feature or debugging area. Set scope="org" to widen prediction across your whole organisation — surfaces cross-team risks ("failed 3× across 2 other teams") from the Org Knowledge Graph, so an incident in one team becomes a vaccine for yours.

Parametersscopetop_kcontextrequiredinstance_id

brain_from_git

Bootstrap brain lessons from git history. Parses commit messages and infers fix/feature/refactor lessons automatically. Great for onboarding an existing codebase — run once and the brain instantly knows your team's accumulated patterns. Incremental by default: only processes new commits since the last run, so repeated calls are fast. Emits progress updates to stderr during long scans.

Parameterslimitsincebranchrepo_pathincrementalinstance_id

cachly_tool

Run any of cachly's specialist tools by name. The most-used tools are listed separately above. This one reaches the other 98 without their schemas taking up room in every request. When: compact_recover (after a context limit); brain_predict_failures (before a risky step, with odds); brain_plan (plan a task from past lessons); brain_conflicts (lessons contradict); memory_crystalize (condense lessons). Unsure about a tool's arguments? Call it with describe:true first — that returns its input schema instead of running it. Available: list_instances, create_instance, get_instance, get_connection_string, delete_instance, cache_delete, cache_exists, cache_ttl, cache_keys, cache_stats, detect_namespace, cache_warmup, cache_mset, cache_mget, cache_lock_acquire, cache_lock_release, get_api_status, recall_feedback, lesson_verified, session_start_summary, session_ping, auto_learn_session, brain_who_knows, brain_file_map, team_expertise_map, brain_collab_pairs, brain_portability, skill_gaps, brain_coverage, brain_metrics, brain_changelog, brain_service_map, sync_file_changes, team_confirm, team_assign_role, team_whoami, team_roster, team_audit, team_grant_scope, team_scopes, team_synthesize, memory_crystalize, team_crystallize, brain_hygiene, global_learn, global_recall, publish_lesson, import_public_brain, recall_at, trace_dependency, list_orgs, create_org, invite_member, get_org_plan, setup_ai_memory, cache_stream_set, cache_stream_get, cache_org_stats, set_cost_per_call, memory_consolidate, brain_diff, knowledge_decay, syndicate, syndicate_search, syndicate_stats, syndicate_trending, brain_marketplace, brain_install, ckg_inspect, brain_plan, brain_conflicts, brain_resolve_conflict, brain_confirm_ci, brain_briefing, brain_contribute_signal, brain_import_meta, madc_deliberate, cls_ingest, cls_install_hooks, fedbrain_contribute, fedbrain_search, fedbrain_confirm, fedbrain_status, brain_federate, crystal_view, compact_recover, brain_from_ci, brain_watch, brain_predict_failure

Parameterstoolrequireddescribearguments

Version history

35
  1. v0.10.231LatestNov 5, 2026
  2. v0.10.230Nov 5, 2026
  3. v0.10.229Nov 4, 2026
  4. v0.10.228Nov 4, 2026
  5. v0.10.225Nov 3, 2026
  6. v0.10.223Nov 3, 2026
  7. v0.10.221Nov 3, 2026
  8. v0.10.219Nov 1, 2026
  9. v0.10.218Oct 30, 2026
  10. v0.10.217Oct 29, 2026
  11. v0.10.214Oct 21, 2026
  12. v0.10.213Oct 21, 2026
  13. v0.10.212Oct 21, 2026
  14. v0.10.211Oct 19, 2026
  15. v0.10.210Oct 19, 2026
  16. v0.10.209Oct 18, 2026
  17. v0.10.208Oct 16, 2026
  18. v0.10.205Oct 16, 2026
  19. v0.10.202Oct 16, 2026
  20. v0.10.201Oct 15, 2026
  21. v0.10.199Oct 14, 2026
  22. v0.10.197Oct 14, 2026
  23. v0.10.194Oct 13, 2026
  24. v0.10.193Oct 13, 2026
  25. v0.10.184Oct 12, 2026
  26. v0.10.182Oct 11, 2026
  27. v0.10.181Oct 11, 2026
  28. v0.10.179Oct 11, 2026
  29. v0.10.178Oct 11, 2026
  30. v0.10.174Oct 10, 2026
  31. v0.10.173Oct 7, 2026
  32. v0.10.172Oct 7, 2026
  33. v0.10.171Oct 7, 2026
  34. v0.10.170Oct 6, 2026
  35. v0.10.169Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts