x.ai Grok MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | Yes | Your x.ai API key |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chat_completionC | Send a chat completion request to x.ai Grok API. Supports system messages, user messages, and various models (grok-beta, grok-2-latest, grok-4-latest). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as sending chat completion requests to the x.ai Grok API, making it distinct by default.
The single tool name 'chat_completion' follows a clear and consistent verb_noun pattern. Since there are no other tools to compare against, there is no inconsistency in naming conventions.
A single tool is too few for a server named 'x.ai Grok MCP Server', which suggests a broader scope for interacting with the Grok API. This minimal toolset feels thin and limits functionality, as it only covers chat completions without obvious support for other potential operations like model listing or configuration.
The tool surface is severely incomplete for the inferred domain of an AI chat API. While chat completions are a core function, there are significant gaps such as missing tools for managing models, handling conversations, or performing other API interactions, which could lead to agent failures in broader tasks.