coding-agent-mcp
Related Servers
Alternatives to coding-agent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server for orchestrating a fleet of CLI coding agents in isolated git worktrees. It exposes tools for spawning workers, sending instructions, reviewing diffs, and merging changes, with full terminal visibility.6 npm4MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.16 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server that enables a supervising OpenAI Codex agent to delegate bounded implementation tasks to isolated worker threads with enforced file scopes and verification, optionally running in parallel git worktrees.524 npm6MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for local AGY worker runtime, enabling controlled task execution with permission checks, evidence collection, and status tracking for build, browser, and image workflows.-
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables Codex and other MCP clients to orchestrate native external coding-agent harnesses through a normalized lifecycle, with guarded execution and deterministic testing.260 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceGives any MCP-compatible AI chat or agent a safe, model-neutral coding runtime with file read/search, structured multi-file patches, command execution, interactive sessions, and git operations, all confined to a single workspace and gated by permission modes.Apache 2.0
TDQS
Scored across 10 tools
Each tool addresses a distinct resource or action: agent discovery, repository discovery, task lifecycle management, output retrieval, git inspection, and verification. There is no meaningful overlap between get_task and get_task_output, or between get_repo_status and get_diff.
All tools follow a consistent snake_case verb_noun pattern (list_*, start_*, cancel_*, continue_*, get_*, run_*). The naming is predictable and makes the action-resource relationship clear across the entire set.
Ten tools is well-scoped for a coding-agent orchestration server. Each tool covers a necessary operation without redundancy, and the count is within the ideal range for maintainability and agent usability.
The tool surface covers the full task lifecycle: create (start_task), read (get_task, get_task_output), update (continue_task), and cancel (cancel_task). It also provides discovery (list_agents, list_repositories), repository inspection (get_repo_status, get_diff), and verification (run_verification), leaving no obvious dead ends for the stated purpose.