Skip to main content
Glama
SoulFireMage

OpenMemory MCP Server

by SoulFireMage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to OpenMemory MCP Server

No user-submitted related servers found.

    Related Servers

    • Spomory

      yliuai
      A
      license
      A
      quality
      A
      maintenance
      Enables personal AI memory management through MCP tools for adding, searching, exporting, and deleting memories, with knowledge-graph retrieval and multi-hop association for clients like Claude Desktop and Cursor.
      6
      Apache 2.0

    • loom-memory

      denislamard
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Desktop and compatible agents to search, read, add, update, and delete a locally stored, user-curated memory using hybrid retrieval with reranking and Qdrant. All processing runs locally without cloud services or API keys.
      9
      Apache 2.0

    • Claude Memory MCP Server

      towan912
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a tiered, persistent memory architecture for Claude to automatically capture and retrieve user preferences, facts, and conversation history across sessions. It supports semantic search and seamless integration with the Claude desktop application using the Model Context Protocol.
      MIT

    • MemoryAI Local

      cenkierpiotr
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent long-term memory and local RAG document search for Claude Desktop, fully offline. Enables memory save/search and document retrieval via MCP.
      MIT

    • novara-context

      ellingtonsp
      F
      license
      A
      quality
      D
      maintenance
      Provides persistent memory, identity, and context for Claude sessions through a memory graph, enabling recall, storage, and relationship management of entities and decisions.
      8
      -
    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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    search_memories and semantic_search are clearly differentiated by keyword vs. meaning-based, though reinforce_memory overlaps with semantic_search's side effect of marking memories as seen and raising salience. The other tools (add, list, get, delete, health_check) are distinct.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (search_memories, add_memory, list_memories, get_memory, delete_memory, reinforce_memory, health_check). health_check is a minor deviation but still clearly named.

    Tool Count5/5

    Eight tools form a well-scoped set for a memory management server, covering search, CRUD, and health checks without bloat.

    Completeness4/5

    Core lifecycle (create, read, list, delete, search) and utility (health_check, reinforce) are covered. Missing an explicit update_memory tool, though the description suggests adding a corrected memory as a workaround.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources