dev-mcp
Related Servers
Alternatives to dev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceGives AI coding assistants persistent memory, safety controls, and project awareness by tracking coding sessions, protecting critical files from modifications, and managing approval workflows with automatic changelog generation.19MIT
- FlicenseNot gradedqualityDmaintenanceTransforms AI coding assistants into context-aware developers by auto-detecting project context, remembering conversations, and executing commands safely with a multi-layer security model.-
- AlicenseNot gradedqualityAmaintenanceExtends AI assistants with software development capabilities such as deep research, codebase analysis, requirements and user-story generation, project scaffolding, context curation, task management, and multi-step workflow execution.42 npmMIT
- 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 gradedqualityAmaintenanceEnables AI coding assistants to persistently save, search, checkpoint, and restore project context across sessions, including decisions, progress, and file state. It supports shared channels, git-aware organization, and batch operations for long-running or parallel development workflows.243 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to research, plan, generate requirements and user stories, create starter projects, analyze codebases, curate context, manage tasks, and execute multi-step development workflows.42 npmMIT
TDQS
Scored across 91 tools
Several clusters of tools are hard to tell apart: git_commit vs commit_changes vs prepare_commit, add_task vs create_task vs update_task, next_task vs next_best_action, generate_project_brain vs project_dashboard, and generate_handoff vs end_session. delete_path vs delete_recursive and desktop_action vs the specific desktop_* verbs also overlap, forcing agents to guess which variant to use. Descriptions help somewhat, but there are too many near-duplicates across domains.
Mostly consistent snake_case, but conventions vary by module: git_* and desktop_* are prefixed, while file operations (read_file, search_code, batch_replace) and brain tools (doctor, next_best_action, next_task) are not. Some names are vague or unprefixed in a way that makes module boundaries unclear, though the overall style remains readable.
91 tools covering file I/O, git, desktop GUI automation, PRD management, phases, tasks, handoffs, architecture analysis, and project bootstrapping is far beyond what can be coherently scoped as one server. Individual capabilities may earn their place, but the aggregate is extreme and should be split into multiple servers.
The surface is effectively over-complete for development workflows, covering file editing, search, git flows, PRD/phase/task lifecycle, handoffs, and verification. Minor gaps exist (e.g. git push/pull/tag/stash, richer git log filtering) but run_command can compensate.