Skip to main content
Glama
naldomadeira

agents-bridge-mcp

by naldomadeira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to agents-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • codex-delegate

      aashahin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to hand off implementation tasks to OpenAI Codex models running through the Codex CLI, with tools for listing models, delegating work synchronously or in the background, collecting results, and continuing past sessions, while Claude stays the orchestrator that reviews diffs and runs tests.
      2
      MIT

    • codex-bridge-mcp

      WeiqiZhou2002
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables two-way collaboration between Claude Code and the Codex CLI: Claude can hand off plans for execution or adversarial review, while the working agent can block to ask Claude questions, report progress or findings, and receive mid-run corrections. Supports multiple named, resumable sessions per project with configurable model, effort, and sandbox settings.
      46 npm
      MIT

    • Claude Code Bridge

      Cyruskraad
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose, but codex_query is a generic catch-all that could overlap with the specialized tools. codex_review_plan and codex_plan_perf also have some conceptual overlap around planning, though their descriptions differentiate them.

    Naming Consistency4/5

    All names use a consistent codex_ prefix and snake_case, following a clear verb or verb_noun pattern. Minor deviation: codex_query and codex_implement are single verbs, while others are compound.

    Tool Count5/5

    Six tools is well-scoped for a Codex bridge, covering query, review, explanation, performance planning, implementation, and code review. Each tool appears to earn its place without excessive fragmentation.

    Completeness4/5

    The surface covers core Codex use cases: asking questions, reviewing plans/code, explaining code, performance analysis, and implementing changes. Minor gaps exist for specialized tasks like test generation or refactoring, but these can be handled via codex_query or codex_implement.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources