memcp
Related Servers
Alternatives to memcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenancePersistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.1,117 npm1MIT
- FlicenseNot gradedqualityBmaintenanceA remote MCP server that gives Claude (and ChatGPT/Gemini) persistent read/write access to your own memory: books, games, projects, notes, and freeform facts.-
- AlicenseNot gradedqualityCmaintenancePersistent memory MCP server for Claude Code that stores decisions and summaries locally, enabling Claude to recall past context across chats.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides persistent long-term memory for Claude Code, enabling storage, search, and retrieval of project knowledge across sessions.-
- AlicenseNot gradedqualityCmaintenanceA persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.32 npm1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server providing persistent, searchable memory management for AI workflows, enabling Claude Code to store, retrieve, and organize context through CRUD operations and knowledge tools.MIT
TDQS
Scored across 24 tools
Most tools have clearly distinct purposes (e.g., memcp_remember vs memcp_load_context, memcp_recall vs memcp_search), but some overlap exists between recall and search, and between consolidate and retention. Overall, an agent can distinguish them with moderate effort.
All tools follow a consistent memcp_ prefix with snake_case naming. Verbs are uniform (e.g., remember, recall, search, forget, consolidate) and the pattern is predictable, aiding agent comprehension.
24 tools is slightly high but appropriate for a comprehensive memory server covering storing, retrieving, managing, consolidating, and cleaning up knowledge. Each tool earns its place, though some like memcp_ping are minimal.
The tool surface covers the full lifecycle: create (remember, load_context), read (recall, search, get_context, inspect_context, peek_chunk), update (reinforce, consolidate), delete (forget, clear_context), and maintenance (retention, restore, list, stats). No obvious gaps.