Skip to main content
Glama
WebisityStudio

claude-codex-mcp-bridge

by WebisityStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claude-codex-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • harness-bridge

      rbutera
      A
      license
      A
      quality
      A
      maintenance
      Bridges Claude Code and OpenAI Codex through MCP, allowing cross-harness querying, code review, explanation, and implementation delegation.
      6
      6 npm
      1
      MIT

    • Claude Codex Computer Use

      songkeys
      A
      license
      Not graded
      quality
      A
      maintenance
      An unofficial bridge that lets Claude Code control local macOS applications through an existing OpenAI Computer Use installation by launching the signed Codex client and translating MCP compatibility.
      13 npm
      1
      MIT

    • Herald

      kOlapsis
      A
      license
      Not graded
      quality
      F
      maintenance
      The self-hosted MCP bridge between Claude Chat and Claude Code.
      46
      AGPL 3.0
    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.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: messaging tools (send, inbox, ack, wait, thread) are clearly separated from orchestration tools (orchestrate_codex, continue_codex, orchestration_status) and discovery/registration (register, agents). Despite some semantic overlap between inbox and thread, their descriptions make the boundary clear.

    Naming Consistency3/5

    All tools share the 'bridge_' prefix, which provides a strong visual pattern, but the suffix style is mixed: some are bare verbs (send, wait, ack), some are nouns (inbox, agents, thread), and some are verb_noun (continue_codex, orchestrate_codex). This is readable but not a consistent verb_noun convention.

    Tool Count5/5

    10 tools is well within the ideal 3-15 range for a server of this scope. Each tool addresses a clear aspect of agent messaging or Codex orchestration without redundancy or bloat.

    Completeness4/5

    The tool surface covers the full coordination lifecycle: registration, discovery, messaging, blocking waits, acknowledgments, thread history, and orchestration state recovery. Minor gaps like an explicit cancel/abort for Codex sessions and a way to list saved sessions are absent but can be worked around with the provided status and continue tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources