Enhanced Grok Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | Yes | Your xAI API key obtained from the xAI Developer Portal. | |
| GROK_TIMEOUT | No | Request timeout in milliseconds (default: 30000). | 30000 |
| GROK_MAX_RETRIES | No | Maximum retry attempts (default: 3). | 3 |
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 |
|---|---|
| grok_searchB | Search the web using Grok's AI-powered search capabilities. Supports both basic search results and comprehensive analysis with timelines, quotes, and multiple perspectives. |
| grok_web_searchC | Search general web content using Grok. Supports comprehensive analysis mode for detailed insights. |
| grok_news_searchB | Search for recent news using Grok. Comprehensive mode provides timeline analysis, direct quotes, and multiple perspectives on news events. |
| grok_twitterC | Search Twitter/X posts using Grok's X search capabilities, optionally filtered by specific handles. Comprehensive mode analyzes social media trends and sentiment. |
| health_checkB | Check the health status of the Grok Search MCP server and API connectivity |
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 5 tools
Multiple tools have overlapping purposes that could cause confusion. grok_search, grok_web_search, and grok_news_search all perform web searches with similar comprehensive analysis modes, making it difficult for an agent to choose the right tool. Only grok_twitter and health_check have clearly distinct functions.
The naming follows a consistent snake_case pattern with a 'grok_' prefix for most tools, which is predictable and readable. The only deviation is health_check, which lacks the prefix but maintains the same naming style, keeping the set mostly consistent.
With 5 tools, the count is reasonable for a search-focused server, but it feels borderline due to redundancy. The set could be streamlined without losing functionality, as multiple tools cover similar search domains, making the number slightly heavy for the apparent scope.
The server covers news, web, and Twitter search with health monitoring, but there are notable gaps. For a search domain, missing tools for filtering, saving results, or handling advanced queries limit agent workflows. The surface is functional but incomplete for comprehensive search operations.