Skip to main content
Glama
Sign In
CoAgent8

CoAgent8

by oktawianwybieralski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to CoAgent8

No user-submitted related servers found.

    Related Servers

    • personal-mcp

      buYoung
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that bridges coding agents (Claude Code, Codex, Gemini CLI) via ACP for pair programming, enabling agents to consult each other as tools.
      3
      -

    • agent-rack

      lakpriya1s
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.
      75 npm
      2
      MIT

    • codex-fusion-mcp

      Tritlo
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling Claude to consult Codex (GPT-5.x) mid-task for second opinions, plan/diff review, brainstorming, and codebase exploration via structured debates and permission-controlled interactions.
      2
      MIT

    • consult

      neelsatyavolu
      A
      license
      A
      quality
      B
      maintenance
      Get a second opinion on your code from every coding agent you have. Claude Code, Codex and Grok review each other's diffs and answer each other's questions, even inside a session that's already running. Uses the CLIs you're signed in to, no API keys.
      4
      338 npm
      1
      MIT
    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

    B3.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: diagnostics, second-opinion consultation, Git review, session management, cancellation, and bug reporting. Consult vs. review is the closest overlap, but the descriptions sharply scope review to Git changes with a verdict while consult is for general questions, designs, bugs, or plans.

    Naming Consistency3/5

    All names are lowercase single words, which is readable, but there is no consistent verb_noun or category pattern. The set mixes nouns and verbs (session, issue, doctor vs. consult, review, cancel), making the naming convention only partially predictable.

    Tool Count5/5

    Six tools is well within a sensible range for this server's apparent consultation/review/session-management purpose. Each tool appears to earn its place without excessive fragmentation.

    Completeness4/5

    The surface covers diagnostics, consultation, review, session listing/history/closing, cancellation, and issue reporting, which is strong lifecycle coverage for the apparent domain. Minor gaps remain around explicitly starting/resuming sessions or follow-up interactions, but agents can likely work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources