Skip to main content
Glama
motock

Fagan

by motock
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Fagan

No user-submitted related servers found.

    Related Servers

    • agent-bridge-mcp

      yukinuma-cpu
      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

    • claude-bridge-mcp

      millanrp25-dot
      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.
      5 npm
      MIT

    • cc-agent

      Gonzih
      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
      187 npm
      2
      Apache 2.0

    • Vibecoders MCP

      RaedBerjaoui
      A
      license
      A
      quality
      B
      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
      3
      MIT

    • frontier-orchestrator

      luckeyfaraday
      A
      license
      A
      quality
      C
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 23 tools

    Disambiguation3/5

    The tool set is mostly well-separated, but there are overlapping clusters: set_story_status overlaps with both mark_story_done and mark_story_in_progress, and get_role_config is largely a subset of get_effective_config. Descriptions help disambiguate, but an agent could reasonably select the wrong tool in these cases.

    Naming Consistency4/5

    Nearly all tools follow a clear verb_noun snake_case pattern (dispatch_story, pause_plan, list_decisions). The only notable deviation is the single-word 'checkpoint', which is still understandable but breaks the otherwise consistent convention.

    Tool Count4/5

    23 tools is on the heavier side, but the server covers a complex orchestration pipeline: plan management, story dispatch, status transitions, review/merge, decisions, and configuration inspection. Each major workflow area needs multiple tools, so the count feels justified rather than bloated.

    Completeness4/5

    The pipeline lifecycle is well covered: plan creation/ingestion, story dispatch/checkpoint/interrupt, status transitions, review, merge, decisions, and config diagnostics. Minor gaps exist, such as no plan deletion/update tool, no detailed plan/story read-back tool beyond list_plans and list_ready_stories, and no merge rejection or PR close path, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources