Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

Server Details

Keeps the rules, decisions and fixes you explain to your AI, for every session and tool. EU servers.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
cachly-dev/cachly-mcp
GitHub Stars
2
Server Listing
Cachly — AI Cognitive Brain
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 27 tools

Disambiguation2/5

Multiple tools retrieve stored knowledge with subtly overlapping boundaries: smart_recall, brain_search, recall_best_solution, brain_predict, causal_trace, recall_context, and team_recall. Similarly, learn_from_attempts, team_learn, global_learn, publish_lesson, and fedbrain_contribute all store lessons. Descriptions attempt to differentiate them, but an agent must choose among many near-duplicates, and cachly_tool creates a second path to roughly 98 additional tools.

Naming Consistency3/5

Several prefix families are internally consistent (cache_*, brain_*, roadmap_*, session_*, team_*), but the overall set mixes verb_noun (recall_context, remember_context, learn_from_attempts), noun_verb (session_start, brain_search), adjective_noun (smart_recall, causal_trace), and standalone names (autopilot, cachly_tool). It remains readable, but there is no single predictable convention across the server.

Tool Count2/5

27 exposed tools is already above the 25-tool threshold, and cachly_tool exposes roughly 98 more tools behind a single dispatcher. The surface is heavy for a memory/cache server, and the mix of direct tools plus a catch-all gateway increases selection cost.

Completeness4/5

Core lifecycle is well covered: cache read/write, context remember/recall/list/forget, lesson learn/recall/search/predict, session start/end/handoff, roadmap add/list/next/update, health checks, and bootstrap tools. Some gaps remain, such as direct roadmap deletion or explicit lesson deletion/update controls among the 27, but most are reachable through cachly_tool.

Available Tools

27 tools
autopilotAInspect

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.

Inputs: style, editor, instance_id, project_name.

brain_doctorAInspect

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.

Inputs: instance_id, workspace_path.

brain_from_gitAInspect

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.

Inputs: limit, since, branch, repo_path, +2 more.

brain_predictAInspect

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.

Inputs: context (required), scope, top_k, instance_id.

cache_getAInspect

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.

Inputs: key (required), org_id, instance_id.

cache_setAInspect

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

Inputs: key (required), value (required), ttl, org_id, +1 more.

cachly_toolAInspect

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_failures, brain_share, brain_import, brain_share_list, brain_unshare, brain_discover, brain_seed_starter, brain_graph, brain_set_pref, brain_get_pref

Inputs: tool (required), describe, arguments.

causal_traceAInspect

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.

Inputs: problem (required), tags, max_depth, instance_id.

forget_contextAInspect

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.

Inputs: keys (required), instance_id.

index_projectAInspect

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.

Inputs: dir (required), ttl, max_files, namespace, +3 more.

learn_from_attemptsAInspect

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

Inputs: topic (required), outcome (required), what_worked (required), tags, +16 more.

list_rememberedAInspect

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.

Inputs: limit, category, instance_id.

recall_best_solutionAInspect

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.

Inputs: topic (required), author, instance_id.

recall_contextAInspect

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.

Inputs: key (required), instance_id.

remember_contextAInspect

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.

Inputs: key (required), content (required), ttl, category, +1 more.

roadmap_addAInspect

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.

Inputs: title (required), tags, priority, milestone, +2 more.

roadmap_listBInspect

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.

Inputs: tag, status, priority, milestone, +1 more.

roadmap_nextAInspect

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.

Inputs: tag, instance_id.

roadmap_updateAInspect

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.

Inputs: id (required), notes, title, status, +3 more.

session_endAInspect

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.

Inputs: summary (required), instance_id, files_changed, workspace_path, +1 more.

session_handoffAInspect

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.

Inputs: completed_tasks (required), remaining_tasks (required), blocked_on, instance_id, +3 more.

session_startAInspect

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.

Inputs: focus, author, provider, instance_id, +1 more.

smart_recallAInspect

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.

Inputs: query (required), limit, author, threshold, +2 more.

team_learnAInspect

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 " so the team knows who learned it.

Inputs: topic (required), author (required), outcome (required), what_worked (required), +6 more.

team_recallAInspect

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.

Inputs: limit, topic, author, instance_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A persistent memory layer for AI tools that decouples personal data from AI's unstable memory, enabling you to mention information once and have it remembered forever across all conversations.
      3
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Cross-model AI memory persistence server that gives every AI tool you use access to the same persistent memory.
      7
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Persists your coding decisions, rules, bugs, to-dos and dead ends into a repo file and automatically brings the relevant ones back into later AI coding sessions. It also checks commands and file edits against those saved rules before they run, flagging anything that might break them.
      709 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent cross-session memory for Claude and other AI agents, letting users store decisions, patterns, and knowledge once and retrieve them automatically across future conversations while surviving context limits and session restarts.
      17 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.