Skip to main content
Glama
GhadiSaab

ctx-memory

by GhadiSaab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ctx-memory

No user-submitted related servers found.

    Related Servers

    • remem

      majiayu000
      A
      license
      A
      quality
      A
      maintenance
      Local-first persistent memory for Claude Code and OpenAI Codex CLI. A single Rust binary captures, distills, searches, and injects project memory across sessions via hooks, MCP, CLI, and localhost REST.
      15
      34
      MIT
    • Memcell by memcell-ai

      Memcellofficial

      memcell-ai
      A
      license
      Not graded
      quality
      F
      maintenance
      Living memory for AI coding agents (Claude Code, Cursor, Copilot, Codex). Cross-vendor persistent memory, decision recall, and outcome calibration via MCP and hooks.
      301 npm
      Apache 2.0

    • mnemolith

      anishchugh05
      A
      license
      A
      quality
      A
      maintenance
      Shared, local memory for AI coding tools that stays true to your code. Claude Code, Cursor, and Codex share one memory per project; memories are linked to the files they depend on and retired automatically when those files change. Includes a local dashboard, import from CLAUDE.md/AGENTS.md, and export. Runs entirely on your machine.
      10
      163 PyPI
      3
      MIT

    • KOPENG

      djy89
      F
      license
      Not graded
      quality
      C
      maintenance
      Persistent, self-curating memory for coding agents. It enables local, zero-cost context recall through MCP tools with hybrid retrieval and autonomous consolidation.
      -
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: session lifecycle (end_session), memory retrieval (get_project_memory, list_sessions, search_context), and data recording (store_event, store_message). No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, e.g., end_session, get_project_memory, store_event. The naming is predictable and uniform.

    Tool Count5/5

    With 6 tools, the server covers core memory management operations without bloat. The count is well-scoped for the domain of session context and project memory.

    Completeness5/5

    The tool surface covers the full typical lifecycle: recording events/messages, searching and retrieving context, listing sessions, and finalizing sessions with memory updates. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources