Skip to main content
Glama

Related Servers

Alternatives to NexusMem

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to query a locally indexed structural code graph — source entities, callers/callees, Git relationships and recorded mistakes — so they retrieve focused, token-bounded context instead of reading entire files. It runs over local SQLite and can be served through a CLI, agent hooks, an MCP executable and an authenticated local dashboard.
      67 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable coding agents to semantically search, store, and inspect a single local, cross-tool index of session histories and project docs. Agents can retrieve what other tools and prior sessions already discovered.
      3
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to persistently store, semantically search, and recall project-specific and cross-project knowledge across sessions, with everything kept local in SQLite. It also exposes project context, guidelines, and preferences as MCP resources for agents to read and write directly.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with persistent, local, and shareable project memory by storing decisions and code context in a searchable SQLite index, supporting keyword and semantic search via MCP.
      3
      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.
      -

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: syncing, status, searching, chronological listing, stale suggestion listing, and resolving stale suggestions. Even the two listing tools are clearly separated by purpose (relevance vs. chronological, suggestions vs. memory). No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list, search, sync, get, resolve. The naming style is uniform and predictable, making it easy to guess tool behavior from the name.

    Tool Count5/5

    Six tools is well-scoped for the server's purpose: ingestion, retrieval, status, and stale-suggestion management. Each tool serves a distinct need without redundancy or unnecessary bloat.

    Completeness4/5

    The core lifecycle is covered: sync to ingest, search/recent to retrieve, status to monitor, and stale suggestion listing/resolution to manage contradictions. Minor gaps exist, such as no per-node manual deletion tool, though sync_project's prune options partially address source-level deletion.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow