CueMap MCP Server
OfficialRelated Servers
Alternatives to CueMap MCP Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseCqualityAmaintenanceEnables AI coding agents to build and query local repository memory, returning ranked files, context packs, relationship maps, semantic recall, and feedback-tuned search without uploading code.22153 PyPI1MIT
- 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
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to retrieve and manage code context with hybrid search, project memory, and observability via MCP tools.29MIT

Doclea MCPofficial
AlicenseNot gradedqualityCmaintenanceProvides persistent memory for AI coding assistants, storing and retrieving architectural decisions, patterns, and solutions across sessions using semantic search, while also offering git integration for commit messages and code expertise mapping.MIT- AlicenseAqualityDmaintenanceEnables AI coding assistants to store and retrieve persistent long-term memory across sessions, remembering project preferences, build steps, and architecture decisions.4MIT
TDQS
Scored across 31 tools
Most tools are clearly separated by resource type (project, memory, alias, lexicon, ingest) and action (init, add, get, delete, list, etc.). Some potential confusion exists between cuemap_project_artifacts and cuemap_project_export, and between cuemap_project_pack/package_load/push/pull/sync, but descriptions clarify their distinct purposes.
Tool names consistently use the cuemap_ prefix with a resource domain (project, memory, alias, lexicon, ingest) followed by an action verb. Minor inconsistency: cuemap_project_package_load breaks the verb_noun pattern compared to cuemap_project_load, and cuemap_init_preview/cuemap_init are not resource-scoped like the others.
31 tools is on the heavy side for a single MCP server, though the domain is broad (project lifecycle, memory operations, aliases, lexicon graph, ingestion, recall). The count is justified by the feature set but exceeds the typical well-scoped range.
The tool surface covers project lifecycle (init, load, unload, save, pack, push, pull, sync), memory CRUD (add, get, delete, reinforce), alias management, lexicon management, ingestion, and recall. Minor gaps: no explicit memory update tool and no project deletion tool, but the core workflows are well covered.