Skip to main content
Glama
Nuruvala

grok-build-mcp-server

by Nuruvala
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to grok-build-mcp-server

No user-submitted related servers found.

    Related Servers

    • grok-subagent

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

    • Grok Build Bridge

      naplesblue
      A
      license
      Not graded
      quality
      B
      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

    • Next-Generation MCP Server

      TanvirIslam-BD
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables sandboxed file operations via MCP tools, resources, and prompts, with a Claude CLI client and Groq-powered web UI for file CRUD, search, code review, and documentation generation.
      MIT

    • grok

      bigu1
      A
      license
      Not graded
      quality
      B
      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
    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/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct operation: general agent run, specialized read-only review, web research, background run status, background run termination, session lookup, environment check, and CLI help. The only potential overlap is between grok, review, and websearch, but their descriptions sharply differentiate the general execution mode from the two read-only specialized modes.

    Naming Consistency4/5

    All tool names are short, lowercase, single words, so there are no case or separator inconsistencies. However, the set mixes action verbs (check, help, review, stop), resource-like nouns (status, sessions), and a product name (grok), so it follows a loose CLI-subcommand style rather than a strict verb_noun naming convention.

    Tool Count5/5

    Eight tools is well-scoped for a CLI wrapper server: core execution, two specialized read-only operations, background run lifecycle management, session inspection, diagnostics, and help. Each tool earns its place and none feels redundant.

    Completeness5/5

    The toolset covers the full workflow of running Grok Build headlessly, including general runs, diff reviews, web searches, background polling, cancellation, session discovery, and environment readiness checks. While session deletion/export is not exposed, session resumption is supported via the grok tool and sessions tool, so there are no dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources