Fagan
Related Servers
Alternatives to Fagan
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that splits coding work between ChatGPT web (planning, review) and Codex CLI (implementation), enabling agentic workflows over a local repo with risk-gated execution and safety rails.23MIT
- AlicenseAqualityDmaintenanceAn 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
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.24 npmMIT
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.4729 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA stdio MCP server that lets coding agents of different model families hand work to each other — asking questions, delegating tasks, arguing out designs, and getting independent cross-family reviews. Write jobs run in their own git worktrees on separate branches for review and merge, with launched agents confined by default in vendor or per-turn sandboxes.MIT
- AlicenseNot gradedqualityBmaintenanceExposes a governed, provenance-grounded autonomous delivery pipeline as an MCP server, enabling AI coding assistants like Claude Code or Codex to initiate requirements-to-PR workflows with human approval gates and full audit.549 PyPI13MIT
TDQS
Scored across 40 tools
Most tools target a distinct resource+action, but several pairs overlap: `checkpoint` is an exact deprecated alias of `checkpoint_story`, `mark_story_in_progress` vs `set_story_status` both mutate status, and `record_decision` vs `request_decision` differ only by one verb despite very different semantics. The long descriptions do resolve most of these, but an agent has to read carefully to avoid picking the wrong one.
The set follows a near-uniform snake_case verb_noun convention (dispatch_story, patch_plan, get_story_log, approve_merge, list_plans...). The only real deviation is the bare verb `checkpoint` kept as a deprecated alias, plus minor singular/plural drift in set_setting vs get_settings/list_settings.
40 tools is well past the point where a single server's surface stays legible, even for a broad pipeline-orchestration domain spanning plan lifecycle, story lifecycle, settings, audit, decisions, and config. The count is inflated by redundant entries like the deprecated `checkpoint` alias and the advance_pipeline/advance_all_plans split.
Coverage is strong: full plan lifecycle (save/ingest/export/approve/reject/pause/resume/patch/advance), full story lifecycle (dispatch/interrupt/checkpoint/status/review/merge/unblock plus logs, journal, diff, worktree), settings, audit verification, and decision escalation. Gaps are minor — no plan deletion or story removal, and no single plan-overview/status tool, but nothing that blocks core workflows.