Skip to main content
Glama

Related Servers

Alternatives to SWE2 Bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.
      9
      5 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Codex to orchestrate persistent Pi RPC workers over a local MCP server, spawning dev, explore and review agents in isolated git worktrees or in place. Codex can inspect status, activity, token/cost metrics and real diffs, then merge only the accepted work and clean up idle workers.
      13
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Codex to supervise one or more local Pi coding-agent workers through bounded task execution, state polling, steering, aborting, and listing. Tasks can run in a direct working directory or isolated Git worktree while Codex remains the planner and reviewer.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Launches the official Codex CLI as a persistent MCP server so DeepSeek Harness can invoke Codex models without storing or transmitting ChatGPT credentials to third parties.
      MIT

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a distinct job lifecycle stage: run (start), wait (poll/collect), cancel (stop). Descriptions explicitly distinguish devin_run from devin_wait and mention job_id handoff, so there is no realistic overlap.

    Naming Consistency5/5

    All three tools use the same devin_<verb> snake_case pattern with parallel imperative verbs (run, wait, cancel). Fully predictable and readable.

    Tool Count5/5

    Three tools precisely cover the async start/poll/cancel lifecycle for a single-job bridge. Nothing is redundant; adding more would be overengineering.

    Completeness4/5

    Start, wait, and cancel cover the core lifecycle, and cancellation notes that changes are preserved. Minor gaps could be listing/inspecting active jobs or cleaning up terminal job state, but these are workable around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues