Project Context MCP
Related Servers
Alternatives to Project Context MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP agents to maintain durable, evidence-aware project knowledge, retrieve precise excerpts on demand, and track decisions, conflicts, and revisions across sessions.1Apache 2.0
- AlicenseNot gradedqualityBmaintenancePersistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI agents with persistent, local, and shareable project memory by storing decisions and code context in a searchable SQLite index, supporting keyword and semantic search via MCP.3MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to persistently store, semantically search, and recall project-specific and cross-project knowledge across sessions, with everything kept local in SQLite. It also exposes project context, guidelines, and preferences as MCP resources for agents to read and write directly.-
- 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.3MIT
- AlicenseBqualityAmaintenanceEnables AI coding agents to maintain persistent project context, including rules, decisions, environment intelligence, and Git history, using a local-first MCP server with automatic project detection and token-efficient retrieval.13MIT
TDQS
Scored across 34 tools
Tools are grouped by domain (project, memory, task, etc.) with distinct actions. Even within groups, each tool has a clear, non-overlapping purpose, e.g., memory_candidate_accept vs. memory_remember serve different lifecycles.
All tools use a consistent verb_noun pattern with underscore_case, such as project_list, project_open, memory_remember, and task_checkpoint. The naming convention is uniform across all 34 tools.
34 tools is well above the typical 3-15 range for a well-scoped server. While the domain coverage is broad, the sheer number may hinder agent navigation and selection.
The tool set covers most lifecycle operations for projects, memories, tasks, and user memories, including backups, indexing, health checks, and search. Minor gaps like in-memory candidate updates exist, but overall it's thorough.