Skip to main content
Glama
shotaro311

Codex Peer

by shotaro311
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Codex Peer

No user-submitted related servers found.

    Related Servers

    • codex-cursor-bridge

      surveyspark
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables two-way delegation between Codex and Cursor agents with background jobs, handoff plans, and isolated worktrees, allowing either editor to offload investigation, review, planning, or implementation to the other and continue the same native session later.
      7 npm
      Apache 2.0

    • MiMo Bridge MCP

      Ichliebedich1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to delegate bounded coding tasks to MiMo Code through a shared local daemon, supporting task boundaries, Git Worktrees, and a collaborative review workflow.
      3
      MIT

    • interclaude

      alexgoodell
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables peer-to-peer communication between Claude Code sessions, allowing them to send messages, hand off tasks, and coordinate across worktrees without manual intervention.
      MIT

    • ClawBridge

      lxivlog64
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Codex to dispatch well-scoped development tasks to a remote CodeBuddy Code instance, specify model and reasoning effort, monitor progress, retrieve results, and review Git changes without auto-merging.
      4 npm
      MIT

    • Codex Peers MCP

      jscianna
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables peer discovery and direct messaging between multiple Codex sessions running on a single machine. It allows AI sessions to coordinate, find other active peers by repository or context, and exchange messages via a local broker.
      1
      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

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health check, sending messages, reading threads, listing threads, and two distinct waiting behaviors (non-blocking check vs. blocking wait). No confusion between tools.

    Naming Consistency5/5

    All tools follow the consistent peer_<verb> or peer_<verb_phrase> pattern in snake_case, making naming predictable and readable.

    Tool Count5/5

    With 6 tools, the set is well-scoped for interacting with peer Codex threads. Each tool fulfills a necessary function without redundancy or sprawl.

    Completeness4/5

    The tool surface covers essential operations: health check, message send, read, list, and wait. Minor missing functionality (e.g., explicit turn initiation) but not severely incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources