What can you do with this server?

The cachly-mcp-server provides persistent AI memory and managed Redis/Valkey caching for AI coding assistants, enabling long-term context retention across sessions while offering full cache management capabilities. 🧠 Session & Memory * Start/end sessions with full briefings and summaries (session_start, session_end, session_handoff) * Store and retrieve lessons from attempts (learn_from_attempts, recall_best_solution) * Cache and recall project context, architecture, and file summaries (remember_context, recall_context, list_remembered, forget_context) * Natural-language semantic search across all brain data (smart_recall) * Auto-classify session observations into lessons (auto_learn_session) * AI brain health check with recommendations (brain_doctor) * Associate git file changes with brain knowledge (sync_file_changes) ⚙️ Instance Management * Create, list, inspect, and delete managed Valkey/Redis instances across pricing tiers * Retrieve connection strings and check API/auth status 🗄️ Cache Operations * Standard key-value operations with TTL (cache_get, cache_set, cache_delete) * Bulk pipeline operations (cache_mget, cache_mset), key listing, TTL inspection, existence checks * Real-time stats: memory, hit/miss rate, ops/sec (cache_stats) * Distributed locking via Redlock-lite (cache_lock_acquire, cache_lock_release) * LLM token stream caching and replay (cache_stream_set, cache_stream_get) 🔍 Semantic Cache * Find cached entries by meaning using pgvector HNSW with hybrid BM25+vector search (semantic_search) * Auto-classify prompts into namespaces (detect_namespace) * Pre-warm semantic cache and index local source files for AI codebase navigation (cache_warmup, index_project) 👥 Team & Global Knowledge * Share lessons across team members with attribution (team_learn, team_recall) * Store cross-project universal lessons (global_learn, global_recall) * Publish anonymized lessons to and import from the Cachly Public Brain community knowledge base 🚀 Setup & Automation * One-command setup of a 3-layer AI memory system with auto-generated copilot instructions and MCP config (setup_ai_memory)

Which integrations are available for this server?

Provides tools for managing cachly cache instances, enabling AI assistants to create, list, monitor, and delete cache instances, perform cache operations, and utilize semantic search capabilities. Integrates with Keycloak for JWT-based authentication to cachly services, allowing AI assistants to securely manage cache instances and operations. Enables caching and semantic search capabilities for OpenAI projects through cachly instances, reducing LLM API calls and improving response times. Provides Redis-compatible cache operations including get/set/delete, key inspection, distributed locks, and streaming cache for LLM tokens through cachly instances.

de en es ja ko ru zh

Cachly — AI Cognitive Brain

by cachly-dev

Overview Schema Related Servers Score Discussions

TypeScript

Remote

The cachly-mcp-server provides persistent AI memory and managed Redis/Valkey caching for AI coding assistants, enabling long-term context retention across sessions while offering full cache management capabilities.

🧠 Session & Memory

Start/end sessions with full briefings and summaries (session_start, session_end, session_handoff)
Store and retrieve lessons from attempts (learn_from_attempts, recall_best_solution)
Cache and recall project context, architecture, and file summaries (remember_context, recall_context, list_remembered, forget_context)
Natural-language semantic search across all brain data (smart_recall)
Auto-classify session observations into lessons (auto_learn_session)
AI brain health check with recommendations (brain_doctor)
Associate git file changes with brain knowledge (sync_file_changes)

⚙️ Instance Management

Create, list, inspect, and delete managed Valkey/Redis instances across pricing tiers
Retrieve connection strings and check API/auth status

🗄️ Cache Operations

Standard key-value operations with TTL (cache_get, cache_set, cache_delete)
Bulk pipeline operations (cache_mget, cache_mset), key listing, TTL inspection, existence checks
Real-time stats: memory, hit/miss rate, ops/sec (cache_stats)
Distributed locking via Redlock-lite (cache_lock_acquire, cache_lock_release)
LLM token stream caching and replay (cache_stream_set, cache_stream_get)

🔍 Semantic Cache

Find cached entries by meaning using pgvector HNSW with hybrid BM25+vector search (semantic_search)
Auto-classify prompts into namespaces (detect_namespace)
Pre-warm semantic cache and index local source files for AI codebase navigation (cache_warmup, index_project)

👥 Team & Global Knowledge

Share lessons across team members with attribution (team_learn, team_recall)
Store cross-project universal lessons (global_learn, global_recall)
Publish anonymized lessons to and import from the Cachly Public Brain community knowledge base

🚀 Setup & Automation

One-command setup of a 3-layer AI memory system with auto-generated copilot instructions and MCP config (setup_ai_memory)

🧠 cachly AI Brain — MCP Server

You're a senior developer. Your AI should act like one.
Stop re-teaching your AI every morning. cachly gives it a permanent brain — pre-briefed every session, learns from every commit, never makes the same mistake twice.

Try it right now — no account needed

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

Run this in any project directory. It reads your git history and shows exactly what your AI would know:

┌─────────────────────────────────────────────────────────────┐
│  🧠 Brain Preview — What your AI would know                 │
├─────────────────────────────────────────────────────────────┤
│  Commits analysed : 847     Date range: 2024-01-12 → 2026-05-14  │
│  Lessons extracted: 634     Contributors: 7                  │
├─────────────────────────────────────────────────────────────┤
│  Category breakdown:                                         │
│  🔧 fix        ████████████████████ 312                     │
│  ✨ feat        ███████████████     189                     │
│  🔒 security    ██                   18                     │
│  🚀 deploy      ██                   15                     │
├─────────────────────────────────────────────────────────────┤
│  🔒 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         │
│  • fix: tRPC context not forwarded to background jobs        │
├─────────────────────────────────────────────────────────────┤
│  💡 With cachly, your AI arrives pre-briefed every session. │
│     No more re-explaining. No more repeated mistakes.        │
└─────────────────────────────────────────────────────────────┘

  Make this permanent (free, 1–5 minutes):
  $ npx @cachly-dev/mcp-server@latest setup

  Works with: Claude Code · Cursor · Windsurf · Copilot · Cline · Zed
  Free forever · GDPR · German servers · No credit card

The Problem

Every morning, you open your AI coding assistant. It doesn't remember yesterday.
You explain your architecture. You explain the deployment process. You explain the bug you fixed last week.

The average developer wastes 45 minutes/day re-establishing context.

One Command. Fully Automatic.

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

Run it once. It handles everything:

Signs you in — one click in your browser, no password, no credit card
Detects your editors — Claude Code, Cursor, Windsurf, VS Code, Copilot, Cline & Zed
Writes the MCP config for every detected editor automatically
Creates CLAUDE.md with Brain rules so your AI acts autonomously
Reads your git history — extracts lessons from years of commits before your first session
Installs a git hook — learns from every future commit automatically

Restart your editor. From now on your AI arrives pre-briefed — every session.

What happens after setup — everything is automatic

Trigger	What the Brain does automatically
First tool call	Session starts, project gets indexed in background
Before every task	AI recalls relevant past lessons
During debugging	AI traces root causes through causal memory
Before deploys	AI predicts failure risks from past patterns
After every fix	AI stores the lesson with commands and file paths
Every git commit	Hook extracts lessons from commit message
Editor closes	Session summary saved for next time

With vs. Without cachly

Situation	Without cachly	With cachly
Session start	"What's your architecture?"	"Ready. 23 lessons, last session: deployed API."
Known bug hits again	Re-researches from scratch	"You fixed this March 12, here's the exact command"
After holiday / handoff	Context dead	Fully briefed in < 10 seconds
New team member	Weeks to onboard	`setup` gives full context instantly
Pre-deploy check	Hope nothing breaks	Brain predicts failures before they happen

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

Brain Badge — show your lessons live

Add a live lesson-count badge to any README — updates every hour, no auth required:

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

Outputs your personal Markdown snippet:

[![cachly Brain](https://api.cachly.dev/api/v1/badge/YOUR_INSTANCE_ID)](https://cachly.dev)

Drop it in your repo's README and anyone visiting sees how many lessons your AI has accumulated. The badge endpoint is public, rate-limited, and only exposes the lesson count — no topic names, no content.

What makes cachly different

Feature	What it does
`causal_trace`	Root Cause Analysis through memory: problem → chain → solution. No other system does this.
`brain_from_git`	Reads your entire git history and loads every lesson before your first session. Incremental on repeat runs.
`brain_predict`	Predicts failures before they happen based on past incident patterns
`memory_consolidate`	Weekly garbage collector — detects contradictions, merges duplicates, expires stale lessons
Team Brain	Shared lessons across your whole team with author attribution
Ambient Git	git hook auto-extracts lessons from every commit. Zero extra calls.
Memory Crystals	Distills all lessons into a compact snapshot for instant session briefing
11 languages	BM25+ search in EN, DE, FR, ES, IT, PT, ZH, JA, KO, AR, HE — no config

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.

cachly vs. alternatives

	cachly	mem0	MemGPT / Letta	Plain CLAUDE.md
Persistent memory	✅	✅	✅	Manual
MCP server (no code changes)	✅	✅	❌	✅
Causal root cause analysis	✅	❌	❌	❌
Fully automatic (no explicit calls)	✅	❌	❌	❌
Failure prediction	✅	❌	❌	❌
Team knowledge sharing	✅	Paid	❌	❌
Git-ambient learning	✅	❌	❌	❌
11-language search	✅	❌	❌	❌
GDPR / EU servers	✅	❌	❌	✅
Free tier forever	✅	Limited	❌	✅

MCP Tools (89 total)

🧠 Session & Memory (most used)

Tool	What it does
`session_start`	Full briefing: last session summary, open failures, recent lessons, brain health
`session_end`	Save what you built, auto-extract lessons from summary + git log
`learn_from_attempts`	Store structured lessons after any fix, deploy, or discovery
`recall_best_solution`	Best known solution for a topic — with success/failure history
`remember_context`	Cache architecture findings, decisions, file summaries
`smart_recall`	BM25+ full-text search across all brain data — 11 languages
`causal_trace`	Root cause analysis through memory
`brain_predict`	Predict likely failures before they happen
`brain_from_git`	Bootstrap from git history — incremental, only new commits each run
`memory_consolidate`	Deduplicate and expire stale lessons
`compact_recover`	Full context recovery after hitting context window limit

👥 Team Brain

Tool	What it does
`team_learn` / `team_recall`	Share lessons across the team with author attribution
`team_synthesize`	Merge conflicting lessons into one canonical version
`madc_deliberate`	6 specialist AI agents vote to resolve contradictory lessons
`memory_crystalize`	Distill all lessons into a Crystal for instant team context
`brain_doctor`	Health check: lesson count, IQ boost %, open failures
`autopilot`	Generate a self-managing `CLAUDE.md` from Brain content
`global_learn` / `global_recall`	Cross-project universal lessons

🌍 Knowledge Commons

Tool	What it does
`syndicate`	Contribute verified lesson to global Knowledge Commons
`fedbrain_search`	Context-weighted global search

⚙️ Infrastructure

Tool	What it does
`list_instances` / `create_instance` / `delete_instance`	Manage Brain instances
`cache_get` / `cache_set` / `cache_delete`	Standard cache operations
`semantic_search`	Find cached entries by meaning
`index_project`	Index source files for semantic retrieval

📋 Roadmap & Planning

Tool	What it does
`roadmap_add` / `roadmap_update`	Persistent project roadmap stored in Brain
`roadmap_list` / `roadmap_next`	List items or get the single most important next action

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.

What is incremental brain_from_git?
After the first run, only new commits since the last scan are processed. Repeated calls are instant.

Can my whole team share the same Brain?
Yes. Use team_learn / team_recall or run npx @cachly-dev/mcp-server@latest invite teammate@example.com.

What is a Memory Crystal?
A compressed snapshot of all lessons injected at every session start. The AI arrives pre-briefed even with a cold context window.

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

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

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"]
    }
  }
}

On the first tool call your AI will prompt you to sign in — takes 10 seconds.

{
  "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

Tier	RAM	Price	Best for
Free	25 MB	€0/mo forever	Dev & side projects
Dev	200 MB	€19/mo	Individual developers
Pro	900 MB	€49/mo	Teams
Speed	900 MB + Dragonfly	€79/mo	AI-heavy workloads
Business	7 GB	€199/mo	Scale-ups

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

Environment Variables

Variable	Default	Description
`CACHLY_JWT`	—	API token (set by wizard automatically)
`CACHLY_BRAIN_INSTANCE_ID`	—	Default instance UUID (optional — auto-resolved)
`CACHLY_API_URL`	`https://api.cachly.dev`	Override for self-hosted
`CACHLY_NO_TELEMETRY`	unset	Set to `1` to disable anonymous usage pings

🛠️ Ecosystem

Package	What it does
`@cachly-dev/mcp-server`	← you are here
`@cachly-dev/openclaw`	Cut LLM costs 60–90% in JS/TS apps

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cachly-dev/cachly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server