Skip to main content
Glama
conrad85

grok-bridge

by conrad85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to grok-bridge

No user-submitted related servers found.

    Related Servers

    • TaskQuay

      lxjmaster
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT conversations to directly inspect local workspaces and delegate coding tasks to a local Codex agent, with controlled concurrency, reusable sessions, and task/usage tracking.
      755 npm
      MIT

    • 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

    • 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

    • grokbot-mcp

      Kenzim
      A
      license
      C
      quality
      C
      maintenance
      Enables IDEs and MCP hosts to drive a user's Grok Bot cloud agents, including sending messages, waiting for replies, reading history, and managing agents, secrets, widgets, handoffs, and desktop access. It acts as an outbound bridge from Cursor, Claude, and VS Code to those cloud agents.
      21
      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

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: health check, synchronous consult, async job lifecycle (start/poll/cancel), listing, and session export. No two tools could be confused for one another.

    Naming Consistency5/5

    All tools share the consistent grok_ prefix and use clear, action-oriented snake_case names. While some are simple verbs (grok_start) and others verb-noun (grok_export_session), the pattern is uniform and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a bridge server dedicated to Grok integration. Each tool covers a necessary operation without bloat or redundancy.

    Completeness5/5

    The tool set covers the full lifecycle: readiness check, synchronous consultation, background job management (start, poll, cancel), history listing, and session export. No obvious gaps for the domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources