Skip to main content
Glama
varadfromeast

codex-agy-bridge

by varadfromeast
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to codex-agy-bridge

No user-submitted related servers found.

    Related Servers

    • agy-bridge

      Heiheiaoo
      A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server bridges Codex to Antigravity CLI, allowing Codex to delegate coding tasks (e.g., code modification, testing, and fixing) to Antigravity within specified project directories.
      MIT

    • chatgpt-with-codex

      yuumiqwq
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP bridge that lets ChatGPT chat mode operate the user's own computer, running project, file, and shell tasks through a local executor and returning progress and results to the conversation. It also coordinates Codex sessions (persistent or one-off) and other agent CLIs as sub-agents.
      MIT

    • codex-mcp-opencode

      Ichikawashadow
      A
      license
      A
      quality
      B
      maintenance
      A project-local MCP bridge that allows Codex Desktop to plan tasks and OpenCode to execute them within the current project directory, with session reuse and native OpenCode background subagents.
      4
      1
      MIT

    • subway-mcp-server

      MauricioPerera
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server that exposes delegation tools for Codex, Claude, and Antigravity CLI, enabling an orchestrator agent to assign tasks to these sub-agents via non-interactive CLI commands.
      3
      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.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools cleanly separate run lifecycle, review workflows, and bridge administration. The main ambiguity is that agy_run_start, agy_start_with_expected_file, agy_review_commit, agy_review_files, and agy_review_branch are all ways to start a run, and agy_run_result versus agy_review_result require careful reading.

    Naming Consistency4/5

    The shared agy_ prefix and snake_case convention make the set readable, and most tools follow a verb_noun style. Deviations like agy_start_with_expected_file, agy_admin, and agy_goal break the pattern slightly, but not enough to cause real confusion.

    Tool Count5/5

    Fourteen tools is a well-scoped surface for a bridge that manages run execution, review workflows, goals, login, and diagnostics. Each tool covers a distinct operation without feeling bloated or redundant.

    Completeness4/5

    The surface covers the full run lifecycle (start, wait, observe, input, cancel, result) and the main review workflows for commits, branches, and files. There are minor gaps such as no obvious way to enumerate all active runs without prior run IDs and limited goal mutation beyond status actions.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources