Skip to main content
Glama
AhmedKishki

memory-ultra-rag-mcp

by AhmedKishki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to memory-ultra-rag-mcp

No user-submitted related servers found.

    Related Servers

    • Titen

      RamaAditya49
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a drop-in MCP memory server over stdio using a local SQLite store, enabling agents to store, search, and audit memory with provenance, scoped access, and contradiction tracking without requiring API keys, LLMs, or embedding providers.
      551 npm
      16
      Apache 2.0

    • mnemo

      llipper
      F
      license
      Not graded
      quality
      C
      maintenance
      Serves local-first project memory over stdio, exposing tools to inspect project state, search and retrieve context, report memory, and create Git-aware checkpoints for coding agents.
      1
      -

    • dek-mcp

      1000bath
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server exposing the dek-memory hybrid memory engine over stdio, with optional ChatGPT tools for managing account memories via a browser profile.
      MIT

    • oliphant

      wsxiaolin
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes repo-native, self-verifying memory to coding agents over stdio MCP, letting them recall ranked past decisions, record new claims with verifiable receipts, and check the health and stats of stored memory. Keeps agent context honest by surfacing memories whose evidence no longer holds.
      127 npm
      MIT

    • Bilinc

      atakanelik34
      A
      license
      A
      quality
      B
      maintenance
      Hosted memory for coding agents, exposing commit_mem, recall, and status over stdio. Each write carries provenance, contradictions surface as inspectable state changes, and a bad run can be rolled back from a snapshot.
      8
      305 PyPI
      1
      Business Source 1.1
    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.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have largely distinct roles: record_memory creates/overwrites a statement, recall_memory searches, forget_memory removes, and record_handoff manages session handoffs. There is minor overlap because record_handoff also writes memory, but the descriptions clearly differentiate it by its replace-last semantics and session-focused purpose.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern: record_memory, recall_memory, forget_memory, record_handoff. The convention is predictable and easy to parse.

    Tool Count5/5

    Four tools is well-scoped for a memory server, covering the core lifecycle operations (record, recall, forget) plus a specialized handoff tool. No tool feels redundant or missing for the stated purpose.

    Completeness4/5

    The surface covers create, read, delete, and session handoff, but lacks a direct update operation. Agents can work around this by forgetting the old statement and recording a new one, so the gap is minor but noticeable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources