grok-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | Yes | Your xAI API key from https://console.x.ai |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_xA | Search X (Twitter) posts using Grok and return a summarised answer with citations. The xAI server autonomously searches X, analyses results, and synthesises an answer grounded in real posts. |
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 confusing it with another. The tool's purpose is clearly distinct by default.
The tool name 'search_x' follows a clear verb_noun pattern and is a single, coherent naming choice. No inconsistency exists with only one tool.
A single tool is borderline for a server named 'grok-mcp'. While the narrow search-and-summarize scope justifies a single tool, the surface feels thin and could benefit from additional related tools.
The tool covers the core search-and-summarize function well, but lacks complementary operations like retrieving raw posts, user timelines, or trending topics. Minor gaps agents can work around, but not a dead end.