misterdev
Related Servers
Alternatives to misterdev
- AlicenseAqualityCmaintenanceProvides per-Subagent MCP controls to any coding agent or client across all your MCPs and prevents context window waste. Loads only 3 tools instead of all your MCP Server's tool definitions. Agents discover tools on-demand, only when needed and only the servers and tools they are allowed.446 PyPI41MIT
- 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
- FlicenseCqualityFmaintenanceAllows Claude Code to offload AI coding tasks to Aider, reducing costs and enabling more control over which models handle specific coding tasks.2308-
- AlicenseAqualityAmaintenanceA fully featured coding agent that uses symbolic operations (enabled by language servers) and works well even in large code bases. Essentially a free to use alternative to Cursor and Windsurf Agents, Cline, Roo Code and others.2931,017 PyPI29,768MIT
- AlicenseAqualityAmaintenanceMCP-native, local-first memory for coding agents that turns real sessions into reusable decisions, gotchas, and domain knowledge.1741 PyPI6MIT
- AlicenseNot gradedqualityCmaintenanceEnables running aider as a detached background process with git and file tools, allowing LLMs to start code editing processes and check progress asynchronously for agentic swarm behavior.34 npmMIT
Related Servers
- AlicenseAqualityCmaintenanceA task-based AI orchestrator that bridges AI models (Gemini, Claude, OpenAI) with local environments, operating as an interactive CLI and an MCP server for structured autonomous development.25 npmMIT
- AlicenseNot gradedqualityAmaintenanceAutonomous spec-to-product coding-agent CLI. Its MCP server exposes 34 tools over stdio: project state and task-queue ops, memory retrieve/store, code search, quality and verification reports, repo hotspots/co-changes, and structured findings/learnings.903 npm1,072Business Source 1.1
- AlicenseAqualityAmaintenanceAutonomous coding pipeline exposed as an MCP server: plan, dispatch, review, and merge software stories through worktree-isolated agents. A frontier model (Claude) handles judgment — planning, review, risk adjudication — while a local model does the implementation, gated by TDD and a merge-time test rerun on the rebased branch.255Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server and HTTP gateway that dispatches coding tasks to Claude Code, Codex, and Antigravity CLI sessions, keeps track of those sessions, and optionally runs an implement → review → verify loop against a real repository.6MIT
- FlicenseNot gradedqualityDmaintenanceSpecForge is a Model Context Protocol (MCP) server that connects an LLM client to a fully autonomous code-fixing pipeline. Point it at a GitHub issue, and it reads the repo, plans a fix, writes the code, tests it, and opens a pull request.-
- AlicenseBqualityCmaintenanceProduction-grade, autonomous Model Context Protocol (MCP) server that elevates AI models from stateless code generators into persistent, self-verifying software engineers.211MIT
TDQS
Scored across 15 tools
The tools split into clear families — project discovery, status/reporting, sync/async execution, job management, and plan approval — and each description explicitly points at when not to use it. The only mild ambiguity is between build/run/execute_plan and get_plan/status, but the descriptions are detailed enough that an agent can usually select correctly.
Most tools follow verb_noun conventions (list_projects, propose_plan, approve_plan, stop_job, list_jobs), and the _async suffix is used consistently. A few bare-noun/verb names (status, report, scan, build, run) and job_status (noun_noun) deviate slightly, but the overall pattern is still predictable.
At 15 tools, the set sits at the high end of well-scoped, but every tool supports a distinct workflow: discovery, status, synchronous execution, background execution, job control, and the proposed-plan review gate. The sync/async pairs and plan-management tools all add real capabilities rather than redundant alternatives.
The core lifecycle is well covered: discover projects, inspect tasks/reports, plan with approval, execute synchronously or in the background, and stop/monitor jobs. Minor gaps remain — no way to unregister a project and no resume/pause for background jobs — but these can be worked around and do not break the main workflows.