Skip to main content
Glama
Sign In
Spomory

Spomory

by yliuai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Spomory

No user-submitted related servers found.

    Related Servers

    • engram

      199-biotechnologies
      A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI persistent personal memory with hybrid search, temporal decay, and knowledge graph. Works with Claude and any MCP client.
      7 npm
      10
      MIT

    • ContextForge

      vikas-1rai
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents and IDEs to capture conversations, extract structured knowledge into a queryable graph database, and recall past decisions, patterns, files, and errors across all projects and workspaces. Provides persistent memory tools for saving, searching, and cleaning up knowledge via MCP.
      2
      -

    • mem0-mcp-selfhosted

      jRicci06
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to maintain persistent cross-session memory using self-hosted Qdrant, Neo4j, and Ollama, with optional Anthropic or local LLM backends, and exposes MCP tools for adding, searching, updating, deleting, and graphing memories.
      -

    • mem0-mcp-selfhosted

      Sompong33136
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to run a self-hosted persistent memory server backed by Qdrant, Neo4j, and Ollama, exposing 11 MCP tools for adding, searching, updating, deleting, and organizing memories and knowledge-graph entities. Supports Anthropic or local Ollama LLMs, automatic session hooks, and cross-session memory management.
      -
    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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clear, distinct operation: add, graph lookup, semantic search, single-fact delete, full wipe, and export. The two delete tools are explicitly differentiated by scope, and get_graph vs search_memory are distinguished by input type (entity vs natural-language query) and output format.

    Naming Consistency5/5

    All tool names follow the same lower_snake_case verb_noun pattern: add_, get_, search_, forget_, forget_all_, export_. The shared 'memory' base and the obvious 'forget_memory' / 'forget_all_memory' pair make the naming highly predictable.

    Tool Count5/5

    Six tools is a well-scoped size for a memory-graph server, covering creation, retrieval, deletion, and export without redundancy or bloat. Each tool earns its place and the count sits comfortably in the ideal 3–15 range.

    Completeness4/5

    The core memory lifecycle is covered: add, retrieve (graph and semantic), delete single, delete all, and export. Minor gaps exist—there is no explicit update operation and no import counterpart to the export—but agents can work around these via add_memory and re-adding facts.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Resources