Skip to main content
Glama
Sign In
Claude-codex-coop

Claude-codex-coop

by youagainchen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Claude-codex-coop

No user-submitted related servers found.

    Related Servers

    • council

      komsamoilenko
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets your AI assistant consult assistants from other vendors under your own subscriptions, track costs, and cross-examine answers across models to surface disagreements and open points.
      3 npm
      MIT

    • Amicus

      BourbonDog
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multi-model LLM council reviews and parallel sidecar conversations within Claude, allowing Claude to orchestrate structured reviews from various AI models and fold their responses back into the session.
      376 npm
      2
      MIT

    • Hegelion

      masato89994
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to perform dialectical reasoning (Thesis → Antithesis → Synthesis) and player-coach verified code synthesis through structured MCP tools. It helps catch blind spots and verify requirements by forcing models to argue with themselves before concluding.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.5/5.0

    Scored across 15 tools

    Disambiguation4/5

    The start_* tools represent distinct workflows (workflow, consultation, debate, implementation), and the setup/status tools are mostly distinct. However, set_collaboration_mode and start_workflow both concern handing off work to the partner AI, and start_consultation vs start_model_debate could be confused without reading descriptions carefully.

    Naming Consistency4/5

    Tool names are consistently snake_case and mostly follow a verb_noun pattern such as get_model_catalog, set_partner_preferences, and start_workflow. A few names break the pattern (health_check, project_status) but overall the convention is predictable.

    Tool Count5/5

    At 15 tools, the set is within the expected range for a collaboration-orchestration server and each tool appears to serve a distinct role in setup, execution, or monitoring. No obvious redundant or filler tools are present.

    Completeness4/5

    The surface covers setup, model selection, workflow starts, status polling, run listing, usage summaries, and implementation runs. A notable gap is the lack of an explicit cancel/stop tool for background collaboration runs, which could leave agents unable to abort a running task.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources