Skip to main content
Glama

Related Servers

Alternatives to Memwyre

  • A
    license
    D
    quality
    C
    maintenance
    SuperMemory is an MCP-first learning memory layer for agents. It helps Claude, Cursor, and other MCP clients reuse validated lessons from prior failures, corrections, and outcomes without saving full transcripts.
    29
    2
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables remote MCP clients to securely access AgentMemory tools like memory_recall, memory_smart_search, and memory_save through OAuth 2.1 and Streamable HTTP, while keeping the AgentMemory backend secret private.
    -

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP-native memory layer for Claude Code, Cursor, Cline, Continue, and 16 other AI tools. Hybrid search (BM25 + pgvector + graph), self-hosted on Supabase + Vercel, 100% MIT, no paywall.
    3
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Persistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB.
    30
    30 npm
    15
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Local-first memory for AI agents: one store shared by Claude Code, Codex CLI, Cursor, Pi, Hermes, OpenClaw, and any MCP client. Plain markdown with YAML frontmatter on your disk, hybrid BM25 + vector recall with per-result provenance (Recall X-ray), a correction contract, and the MemCorrect benchmark.
    206
    MIT

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a fairly clear role: search finds relevant memories, list shows recent ones, get retrieves by ID, and save creates new content. Some minor overlap exists between search and list for locating memories, but the descriptions make the distinction workable.

Naming Consistency3/5

Most tools follow a verb_noun pattern (save_memory, list_memories, get_document), but search_memwyre breaks the pattern by using the product name instead of a noun like 'memories'. There is also mild inconsistency between 'memory' and 'document' as the noun for the same underlying resource.

Tool Count5/5

Four tools is a well-scoped size for a personal knowledge vault server. Each tool covers a distinct core operation—save, search, list, and get—without unnecessary bloat.

Completeness3/5

The server covers create and read workflows well, including semantic search, but it lacks update and delete operations for memories or documents. This is a noticeable gap in lifecycle coverage, though simple note-taking use cases can still succeed.

Maintenance

ActivityMaintained
ResponsivenessNo issues