Skip to main content
Glama
saidelike

codex-thread-bridge

by saidelike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to codex-thread-bridge

No user-submitted related servers found.

    Related Servers

    • agentchan

      damejeras
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to communicate with each other by sending messages and waiting for replies across sessions, supporting agents like Claude Code, Codex, and Grok.
      MIT

    • wingman

      juangurdian
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts to connect to local Codex sessions for listing, reading, messaging, and interrupting them without hijacking the terminal.
      MIT

    • Agent Link

      Brandon-Gottshall
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables one AI coding agent to discover, read, message, and wait on other agent sessions across Codex threads and Claude Code or Claude Desktop sessions, while logging every send as a local receipt that can be audited later.
      1 npm
      MIT

    • hato

      severzemlya
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables inter-session messaging for Claude Code, allowing sessions on different machines to send messages to each other, with delivery as user turns and support for offline queuing.
      66 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action: capabilities, thread creation variants, listing/reading/waiting, goal inspection, and operation receipt inspection. Even the two creation tools are sharply separated by the worktree behavior, and send_message_to_thread has no overlap with the create or read tools.

    Naming Consistency5/5

    All tool names are lowercase snake_case and verb-led, following a consistent verb_noun structure such as create_thread, list_threads, read_thread, get_goal, and get_operation. The one compound name, send_message_to_thread, is still semantically aligned and does not introduce a different convention.

    Tool Count5/5

    Nine tools is well within the ideal range for a bridge server. Each tool covers a distinct lifecycle or inspection concern without redundancy, and the count feels proportionate to the domain.

    Completeness4/5

    The core workflow is well covered: create threads, send messages, read/wait on turns, and inspect goals or operation receipts. Minor gaps exist around thread lifecycle management (no archive/delete) and goal mutation, but these appear intentionally left to external ownership and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources