Skip to main content
Glama
yonro

XMemo

by yonro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to XMemo

  • mem0-mcp by tensakulabs

    mem0-mcpofficial

    tensakulabs
    A
    license
    A
    quality
    C
    maintenance
    Self-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.
    6
    4
    MIT

Related Servers

  • agents-memory

    Lolaplex
    A
    license
    Not graded
    quality
    A
    maintenance
    A local markdown memory and cross-agent context engine for AI coding assistants. It provides an MCP server with tools to search, add, retrieve, and distill persistent memory across tools like Claude Code, Cursor, and Zed.
    38 PyPI
    5
    MIT

  • mesh-memory

    dklymentiev
    A
    license
    Not graded
    quality
    D
    maintenance
    Self-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).
    1
    MIT

  • mnemos

    s60yucca
    A
    license
    B
    quality
    B
    maintenance
    Persistent memory engine for AI coding agents. Single Go binary, zero runtime dependencies, MCP-native. Stores, searches, and deduplicates memories across sessions using embedded SQLite with hybrid FTS + semantic search, memory decay, relation graph, and token-budget context assembly.
    10
    22
    MIT

  • Local Context MCP

    zwinglio
    F
    license
    Not graded
    quality
    B
    maintenance
    A self-hosted AI memory service that shares durable project context between MCP-compatible clients such as Claude Code and Devin, via a REST API and a Streamable HTTP MCP server with tools to remember, recall, list, and forget memories.
    -

  • flux7-memory

    KTCrisis
    A
    license
    Not graded
    quality
    A
    maintenance
    Governed multi-agent memory for AI agents. Hybrid markdown + SQLite store with full-text search, vector retrieval, and LLM reranking. Three transports: MCP stdio, HTTP JSON-RPC, and MCP SSE. One Go binary
    1
    Apache 2.0
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

A3.6/5.0

Scored across 31 tools

Disambiguation3/5

Most tools target distinct resources, but retrieval is spread across recall, recall_context, search_knowledge, and get_project_context with fuzzy boundaries, and propose_write overlaps with the specialized propose_*_mutation tools. The detailed descriptions help, but references to absent tools like add_expense and memory_activity add confusion.

Naming Consistency4/5

The set mostly follows a clear verb_noun snake_case pattern (create_memory_todo, update_project_decision, restore_restart_snapshot). Exceptions include memory_stats (noun-first), bare verbs like remember/forget/recall, and generic names like update_state and propose_write.

Tool Count2/5

31 tools is above the threshold for a coherent set, and several are narrow variants: three propose_* tools, multiple overlapping recall/search tools, and separate restart snapshot create/restore tools. The broad domain justifies some size, but consolidation would make the surface significantly clearer.

Completeness3/5

Core memory lifecycle is covered (remember, read_memory, update_memory, forget, restore_memory), alongside todos, projects, audit, cloud skills, and snapshots. However, descriptions direct agents to missing tools like add_expense and memory_activity, and there are no obvious project creation/listing or cloud skill update/delete operations.

Maintenance

ActivityNo data
ResponsivenessWithin a week

Resources