Skip to main content
Glama
LogicLabsAI

UltraMemory

Official
by LogicLabsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to UltraMemory

No user-submitted related servers found.

    Related Servers

    • 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.
      1,351 npm
      Apache 2.0

    • KOPENG

      djy89
      F
      license
      Not graded
      quality
      B
      maintenance
      Persistent, self-curating memory for coding agents. It enables local, zero-cost context recall through MCP tools with hybrid retrieval and autonomous consolidation.
      -

    • iranti

      nfemmanuel
      A
      license
      A
      quality
      C
      maintenance
      Persistent shared memory for AI coding agents. Stores facts as entity/key/value triples with hybrid semantic search, task checkpoints, and conflict resolution — shared across Claude Code, Codex CLI, and GitHub Copilot.
      16
      235 npm
      5
      AGPL 3.0

    • Remnic

      joshuaswarren
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first memory for AI agents: one store shared by Claude Code, Codex CLI, Cursor, Pi, Hermes, OpenClaw, and any MCP client. Plain markdown with YAML frontmatter on your disk, hybrid BM25 + vector recall with per-result provenance (Recall X-ray), a correction contract, and the MemCorrect benchmark.
      218
      MIT
    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

    A4.1/5.0

    Scored across 9 tools

    Disambiguation3/5

    Multiple recall tools (memory_recall, recall_gated, recall_verified, search) overlap in retrieving information, though descriptions attempt to differentiate them by use case (e.g., policy, precision). This creates potential confusion for an agent selecting the right tool.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern with underscores (e.g., playbook_recall, memory_write), but 'search' and 'fetch' are single verbs without a noun, creating a minor inconsistency.

    Tool Count5/5

    With 9 tools covering memory storage, retrieval, and feedback, the count is well-scoped for a memory management server. Each tool serves a distinct role without feeling excessive.

    Completeness3/5

    The server lacks update and delete operations for memories, and there is no list-all tool. While core write/recall is covered, these gaps hinder full lifecycle management.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources