Context-MCP
Related Servers
Alternatives to Context-MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceProvides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.1661 npm2MIT
- AlicenseAqualityDmaintenanceLong-term memory for AI coding assistants. Remembers context once and recalls it across sessions.723MIT
- AlicenseNot gradedqualityCmaintenanceIntelligent context-aware memory system for AI assistants that enables persistent memory, automatic development activity tracking, and intelligent information retrieval across conversations.72 npm18MIT
- AlicenseNot gradedqualityBmaintenancePersistent memory for AI coding tools that captures conversations, builds a searchable knowledge graph, and automatically injects relevant context into new prompts.8 npm248MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent, context-rich memory of a codebase, including documentation and git history, enabling recall across sessions.105Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persistently save, search, and restore project context across sessions, including decisions, progress, file caches, checkpoints, and channel-based memory. It supports git-aware organization, batch operations, and shared memory across parallel sessions.250 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct action on the context knowledge base: add, get, search, update, delete, relate, stats, focus, and summarize. There is no meaningful overlap; even get and search serve clearly separate purposes (broad optimized view vs. targeted query).
All tool names follow a uniform 'context_' prefix followed by a simple verb (add, get, search, update, delete, relate, stats, focus, summarize). This is a perfect example of consistent verb_noun convention.
With 9 tools, the server is well-scoped. Each tool is meaningful and contributes to the overall context management workflow without redundancy or bloat. This is an ideal size for the stated purpose.
The tool set covers the full lifecycle of context entries: create (add), read (get), update, delete, search, linking (relate), statistics, focus management, and summarization. There are no obvious dead ends or missing core operations.