Skip to main content
Glama
yaminbkk

NexusMem

by yaminbkk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to NexusMem

No user-submitted related servers found.

    Related Servers

    • ctxmem

      DoppiaG93
      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
    • Tramya by tramya-ai

      Tramyaofficial

      tramya-ai
      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.
      -

    • CodeLedger

      mikuare
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives coding agents a local, SQLite-backed memory of a codebase, enabling them to query symbol impact, change history, and task scope through MCP while recording what actually changed after edits.
      MIT

    • devrecall

      pavelpilyak
      A
      license
      A
      quality
      A
      maintenance
      Local-first dev memory: indexes Git commits, PRs, Jira/Linear tickets, Confluence docs, Slack threads, and Calendar events into a local SQLite/FTS5/ONNX index, and exposes them as MCP tools so Claude Code, Cursor, and Codex can search and cite your past work.
      17
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityActive
    ResponsivenessSlow

    Resources