Skip to main content
Glama
TuTouPower

grok-mcp

by TuTouPower
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
grok_checkA

Probe whether Grok Build bridge + CLI are ready (node, grok binary, auth). Returns {rows: [{label, ok, detail}]} envelope; the raw bridge JSON is preserved in the 'bridge output' row's detail for callers that parsed the old shape.

grok_runA

Run a Grok Build task via bridge (run). background=true: bridge enqueues detached worker and exits; this tool only waits for that enqueue JSON (jobId), default max 60s — not the full agent run. Poll grok_show / report files for completion. write=false default (read-only). Prompt via --prompt-file under tmpdir. Foreground default timeout 900000ms (15 min). Pass cwd for project paths.

grok_runsC

List tracked Grok bridge runs, or one run by id (runs).

grok_showC

Show status/result of a Grok bridge run (show).

grok_stopC

Stop a running Grok bridge job (stop).

grok_bridge_pathA

Resolve which grok-bridge.mjs path this MCP server will use.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: check readiness, run a task, list runs, show status, stop a job, and resolve bridge path. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'grok_' prefix with descriptive verb/noun names (check, run, runs, show, stop, bridge_path). No mixing of conventions.

Tool Count5/5

Six tools is ideal for the domain, covering readiness, execution, listing, status, stopping, and configuration. Each tool earns its place without excess.

Completeness5/5

The tool surface covers the full lifecycle of Grok build runs: check (readiness), run (create), runs (list), show (read), stop (delete/stop), plus configuration (bridge_path). No obvious gaps.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources