Skip to main content
Glama

Related Servers

Alternatives to Fagan

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An 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.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      15 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
      47
      109 npm
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      One MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.
      23
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Multi-agent orchestration MCP server that lets Claude Code delegate backend, frontend, and tooling tasks to specialized AI agents (Codex, Kimi, Grok) with contract-first sequencing and workspace mutation guards.
      4
      7
      MIT

    TDQS

    A4.1/5.0

    Scored across 26 tools

    Disambiguation3/5

    Several tools overlap in purpose: checkpoint is a deprecated alias of checkpoint_story, and mark_story_in_progress/mark_story_done/set_story_status all mutate story status while dispatch_story also transitions to In Progress. Detailed descriptions mitigate confusion, but an agent could still misselect among the status-transition tools.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern (e.g. list_plans, dispatch_story, approve_merge). The main deviation is the deprecated 'checkpoint' alias, which drops the object noun and breaks the pattern slightly.

    Tool Count4/5

    26 tools is on the heavy side, but the server covers a broad multi-agent pipeline domain (planning, dispatch, review, merge, decisions, config, usage, audit). The count is justified though a few redundant tools (deprecated alias, overlapping status setters) inflate it.

    Completeness4/5

    The surface covers the full plan-to-merge lifecycle including planning, ingestion, dispatch, checkpointing, review, merge, decisions, and operational diagnostics. Some gaps remain, such as listing all stories in a plan or managing plan/story deletion, but core workflows are complete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues