mcp-project-m
Related Servers
Alternatives to mcp-project-m
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceOne local memory every coding agent on your machine shares — Claude Code, Cursor, Claude Desktop, OpenCode. Answers from past sessions, commits, CLAUDE.md/AGENTS.md and ADRs with the exact source, and withholds work another agent has claimed so two agents don't rewrite the same thing.34,718 PyPI2MIT
- AlicenseAqualityBmaintenanceA local-first shared memory layer for MCP-aware agents like Claude, Codex, and Hermes, enabling persistent memory across chats and clients via Markdown files and SQLite FTS.62MIT
- AlicenseAqualityBmaintenancePersistent, shared memory for Claude across sessions and clients (Code, Desktop, Cowork) — deterministic diff reads, checkpoints, cross-client task handoff, and project-wide search. 100% local and deterministic, no API keys, no LLM summarization.64MIT
- AlicenseBqualityDmaintenanceA shared memory layer for AI agents — one memory.md synced across Claude Desktop, Cursor, Claude Code, OpenAI Codex, and any MCP client.42MIT
- AlicenseNot gradedqualityDmaintenanceA shared operational layer that synchronizes tasks and project contexts across Claude Chat, Cowork, and Code surfaces using local markdown files. It enables persistent state management and cross-session knowledge sharing without the need for a database.34MIT
- AlicenseAqualityCmaintenanceLocal-first shared memory and coordination layer for AI coding agents, with repository evidence, reservations, handoffs, code graph context, and dashboard review backed by PostgreSQL/pgvector.303Apache 2.0
TDQS
Scored across 8 tools
Most tools target distinct resources (board, decisions, tasks, context turns). The main soft overlap is get_project_board vs get_project_summary, both returning project state (markdown card vs structured counts), and the three context tools (get_recent_context, get_turn, search_historical_context) which are clearly differentiated by mode (recent list, exact ID, keyword search). Descriptions help resolve these.
All names are snake_case verb_noun (get_project_board, record_decision, publish_context, update_task, search_historical_context, etc.). Predictable verb-first pattern with distinct nouns, no mixed conventions.
Eight tools is well-scoped for a project state/provenance server, mapping cleanly onto its tiers (board, ADRs, tasks, context, search). No redundant or filler tools.
Core lifecycle is covered: read board, record decisions, publish metadata, update tasks, retrieve and search context. Minor gaps remain—there is no dedicated tool to list or fetch an individual ADR (proposed/superseded ones are only reflected indirectly), and no explicit task-creation or deletion operations—but agents can work around these via the board card and summary.