Skip to main content
Glama
Sign In
Nurkic4

Grok-Codex Bridge

by Nurkic4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Grok-Codex Bridge

No user-submitted related servers found.

    Related Servers

    • grok-subagent

      Walvez
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to use Grok Build CLI as a controlled subagent via MCP tools for independent investigation, review, and isolated implementation tasks.
      5
      MIT

    • Grok Build Bridge

      naplesblue
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects OpenAI Codex and Claude Code to the local Grok Build CLI for second-opinion code reviews, bounded coding tasks, web research, media generation, and TTS.
      3
      Apache 2.0

    • claude_executor

      xlong-c
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to delegate a bounded implementation task to the locally installed Claude Code CLI for scoped file edits and optional mechanical checks while keeping planning, review, and final decisions with Codex.
      Apache 2.0

    • grok

      bigu1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables OpenAI Codex to invoke the local Grok CLI as a second agent for code review, planning, design documents, PR babysitting, and media creation via MCP tools.
      Apache 2.0

    • codex

      jinxlzc
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Grok Build to orchestrate the local Codex CLI for code reviews, adversarial reviews, task rescue, session transfer, and background job management through MCP tools.
      1
      Apache 2.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.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: session creation, task start, status check, cancel, session switch, and close. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'grok_verb_noun' pattern (e.g., grok_session_ensure, grok_task_start), making it predictable.

    Tool Count5/5

    With 6 tools, the server is well-scoped, covering the full lifecycle of session and task management without unnecessary duplication.

    Completeness5/5

    The tool set covers all essential operations for managing Grok sessions and tasks: creation, starting, status, cancellation, context switching, and cleanup. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources