membridge
Related Servers
Alternatives to membridge
- FlicenseAqualityBmaintenanceA basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.9340,089 npm92,139-

mem0-mcpofficial
AlicenseAqualityDmaintenanceSelf-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.64MIT- AlicenseAqualityBmaintenanceEnables MCP-capable coding agents to semantically search, store, and inspect a single local, cross-tool index of session histories and project docs. Agents can retrieve what other tools and prior sessions already discovered.31MIT
Related Servers
- AlicenseAqualityDmaintenanceA zero-dependency MCP server for cross-session memory recall in Claude Code. Provides lexical search, listing, and retrieval of past session memories to avoid re-explaining context.38 npmMIT
- AlicenseAqualityDmaintenanceSelf-hosted remote MCP memory server for ChatGPT and AI agents.342MIT
- FlicenseNot gradedqualityBmaintenanceEnables long-horizon conversational memory compaction and episodic anchor extraction for AI agents, providing deterministic memory management through a zero-dependency MCP server.8-
- AlicenseNot gradedqualityBmaintenanceA personal memory MCP server for Obsidian/markdown vaults that provides hybrid retrieval (semantic, keyword, tag, time-aware co-occurrence) and is shared across multiple AI clients.175 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP Memory Server for Claude Code that provides persistent context across sessions using semantic search (RAG).Apache 2.0
- AlicenseAqualityBmaintenanceSelf-hosted MCP memory server for personal use and teams1130AGPL 3.0
TDQS
Scored across 5 tools
recall vs remember are clearly read/write opposites, and redact is distinct. However, recall's optional 'target' formatting parameter substantially duplicates membridge_format (both produce a destination-specific memory pack), and extract vs remember have fuzzy boundaries (parse text into memories vs save a fact). An agent could reasonably pick the wrong one for 'give me a Claude-ready pack'.
All five tools use the identical membridge_ prefix with a single lowercase verb (recall, extract, redact, format, remember). No casing or convention mixing.
Five tools is well within the ideal 3-15 range and matches the narrow scope of a portable memory bridge. Each tool maps to a recognizable step: capture, parse, store, retrieve, sanitize, export.
The lifecycle covers create (remember), read/search (recall), import (extract), and export (format/redact). But there is no way to update, delete/forget, or list/clear memories — agents cannot correct a wrong memory or remove stale ones, which is a notable gap for a persistence tool.