A
licenseA
qualityD
maintenanceMCP server that wraps the Grok CLI to enable code review, adversarial testing, and chat with xAI's Grok model, integrating into any MCP host as a peer reviewer, adversary, and consultant.
4
64 npm
11
MIT
grok-mcp
by Dragonshock
Related Servers
Alternatives to grok-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that wraps the xAI Grok API, allowing Claude and other AI agents to delegate thinking, planning, and real-time search tasks to Grok. It provides a single tool with options for different use cases including web search, Twitter/X search, and multi-agent reasoning.210 npmMIT
- AlicenseAqualityAmaintenanceA minimal local MCP server that lets Claude Desktop or Claude Code delegate coding tasks to Grok Build running headless as a subagent.540 npm1MIT
- AlicenseAqualityBmaintenanceAn MCP server that turns Grok CLI into the execution agent for Claude Code, implementing an orchestrated execute-verify-autofix loop for autonomous development tasks.7MIT
- AlicenseAqualityFmaintenanceMCP server for running external coding agents as background tasks inside Claude Code. Supports multiple backends including Codex, Grok, GLM, DeepSeek, and more.7MIT
- AlicenseBqualityBmaintenanceAn MCP server that exposes the local Grok CLI to Codex for bounded repo work, reviews, rescue analysis, adversarial checks, session listing/export, and background job management while keeping Codex hidden context out of scope.12MIT
TDQS
A4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: grok_ask handles direct Q&A or worker execution, grok_workflow runs a named workflow, and grok_workflows lists available workflows. There is no overlap or ambiguity among them.
Naming Consistency4/5
All tools share the 'grok_' prefix, but the second part mixes a verb (ask) with nouns (workflow/workflows). This is a minor inconsistency; the pattern is still predictable and readable.
Tool Count4/5
The server has only 3 tools, which is slightly thin but appropriate for a focused Grok interaction server. The tools cover the core needs without unnecessary bloat.
Completeness4/5
The domain is Grok interaction, and the surface covers asking, running workflows, and listing workflows. Minor gaps could include viewing workflow details or cancelling runs, but these are not critical for the apparent purpose.
Maintenance
ActivitySlowing
ResponsivenessNo issues