A
licenseA
qualityF
maintenanceModel Context Protocol (MCP) server implementation that enables Claude Desktop to interact with Google's Gemini AI models.
6
16 npm
259
MIT
Grok MCP
by merterbak
Related Servers
Alternatives to Grok MCP
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for xAI Grok API with 19 tools for chat, web and X search, session management, tool chaining, image and video generation, and documentation.2MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for the xAI Grok API, providing tools for chat completions, vision analysis, web/X search, embeddings, and model listing via stdio.-
- AlicenseAqualityAmaintenanceAn MCP server for Grok (xAI) that enables chat, reasoning, vision, and video generation using the AceDataCloud API.81MIT
- AlicenseAqualityDmaintenanceMCP server for integrating xAI's Grok model into OpenAI Codex Desktop/GUI, enabling direct Grok calls via chat completions or responses with OAuth or API key authentication.9MIT
- AlicenseAqualityAmaintenanceMCP server for generating and editing images using xAI's Grok image model, supporting text prompts, batch generation, local files, and optional proxy configurations.244 npm29MIT
- AlicenseAqualityFmaintenanceProduction-grade MCP server for image and video understanding and generation across Gemini, OpenAI, and Grok.5171 PyPI4Apache 2.0
TDQS
A3.9/5.0
Scored across 22 tools
Disambiguation3/5
Most tools are distinct, but `grok_agent` explicitly subsumes vision, files, web/X search, code execution, and image generation, overlapping heavily with `chat_with_vision`, `chat_with_files`, `web_search`, `x_search`, `code_executor`, and `generate_image`. `chat`, `stateful_chat`, and `chat_with_files` also have fuzzy boundaries between simple chat and agentic chat. Descriptions do help, but an agent could easily misselect.
Naming Consistency4/5
The set is dominated by a clear verb_noun pattern (delete_file, get_file, generate_image, list_files, upload_file, web_search, extend_video). A few outliers (`chat`, `stateful_chat`, `grok_agent`, `code_executor`) are noun- or adjective-led, but overall the convention is readable and mostly predictable.
Tool Count4/5
At 22 tools this sits at the heavy end, but the breadth (chat, stateful chat, files, vision, image, video, web/X search, code, models) genuinely justifies a large surface. The only redundancy is the all-in-one `grok_agent` duplicating several specialized tools, which could arguably be folded in.
Completeness4/5
File lifecycle is fully covered (upload, list, get metadata, get content, delete), chat and stateful-chat lifecycles are covered, and media generation includes image, video, and extend. Minor gaps remain (no listing of stateful responses, no video delete), but core workflows have no dead ends.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive