Skip to main content
Glama
asd-noor

Memory Engine MCP Server

by asd-noor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Memory Engine MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-memory-libsql

      spences10
      A
      license
      B
      quality
      B
      maintenance
      A high-performance MCP server utilizing libSQL for persistent memory and vector search capabilities, enabling efficient entity management and semantic knowledge storage.
      6
      93 npm
      88
      MIT

    • Synapse Memory

      RaffaelFerro
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server that provides long-term memory for LLMs by storing and retrieving important facts, decisions, and preferences through smart semantic search and automatic organization.
      12
      MIT

    • Memento

      iAchilles
      A
      license
      A
      quality
      C
      maintenance
      A local, fully-offline MCP memory server that enables persistent storage and retrieval of information using SQLite with both keyword and semantic vector search capabilities.
      10
      19 npm
      13
      MIT

    • fuga-memory

      densuke
      A
      license
      A
      quality
      D
      maintenance
      An MCP server providing long-term memory for LLMs via hybrid search (FTS5 + vector) stored in SQLite, with time-decay scoring and support for multiple AI assistants.
      4
      2
      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 5 tools

    Disambiguation5/5

    Each tool targets a distinct memory operation: save (create), delete, update, verify, and query (search). There is no overlap in purpose, so an agent can easily select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., save_memory, delete_memory, update_memory), making the API predictable and easy to navigate.

    Tool Count5/5

    With exactly 5 tools, the server is well-scoped for a memory management domain, covering essential operations without unnecessary complexity.

    Completeness5/5

    The server provides full CRUD coverage (save, query, update, delete) plus a verify operation for freshness. No critical lifecycle steps are missing for long-term memory storage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources