Skip to main content
Glama

Related Servers

Alternatives to EGC

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Provides AI coding tools with one local SQLite memory and rules store they can read over MCP, REST or the CLI, so facts, sessions and goals persist across sessions and shared rules are written into each tool's own instruction file. Runs entirely on your machine with no account, telemetry or network calls by default.
      4
      13
      2,159 npm
      9
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.
      2
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Persistent memory for AI coding agents, storing decisions, bug fixes, conventions, and discoveries in a local SQLite database and automatically recalling them when relevant. Works with Claude Code, Codex, Cursor, Gemini CLI, and other MCP-compatible agents.
      22
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Local-first memory for AI coding agents. Indexes your Claude Code, Codex, Cursor, Cline and Gemini CLI history by repo/branch/worktree and hands a context capsule (decisions, touched files, next steps) to the next agent over MCP.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
      51
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Local-first cross-agent memory for AI coding agents. Persistent, shared memory over MCP — what you tell one agent can be recalled by another — with all data stored in a single local SQLite file, no cloud and no API keys.
      -

    TDQS

    A4.4/5.0

    Scored across 24 tools

    Disambiguation5/5

    The toolset is highly sophisticated, segmenting functionalities into distinct domains like session management, memory persistence, and learning reinforcement. Each function, such as get_state versus query_history or lesson_save versus lesson_reinforce, serves a clear, non-overlapping purpose.

    Naming Consistency5/5

    The naming convention is highly consistent, predominantly using the verb_noun pattern (e.g., get_project_state, session_send, update_state). While the terms are complex, the structural predictability makes them easy to parse.

    Tool Count5/5

    The domain of maintaining autonomous, distributed, learning memory is extremely complex. Twenty-four tools are highly appropriate for covering the necessary surfaces of state management, session communication, and team synchronization.

    Completeness5/5

    The tool surface is exceptionally thorough. It provides robust mechanisms for everything from transient working memory and long-term state persistence to distributed session locking and team-level synchronization.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week