All servers / AI / Grok MCP server
Grok MCP server
MCP server that proxies to xAI Grok API for searching X (formerly Twitter)
Tested by ConnectATDScore 84 out of 100. Tested 2026-11-18 on package version 0.2.4. Package: grok-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 14 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (14.5 seconds including download)
- Tools offered: 1
- Last published: 2026-05-06
- Weekly downloads (npm): 1,701
- License: MIT · Direct dependencies: 6
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
x_search5 of 5 parameters describedSearch X (formerly Twitter) in real-time using Grok's X Search. Supports structured output via JSON Schema and multi-turn chaining via response IDs. Use this tool when you need: - Real-time posts, trends, or public opinion from X - Fetching a specific post and its thread/replies by URL - Structured extraction of X data (topics, sentiment, reactions, etc.) - Follow-up searches that build on a previous result (drill-down, filtering, summarization) Workflow for deep research: 1. First call: use output_schema to get structured data + capture response_id 2. Follow-up calls: pass previous_response_id to continue with context Workflow for thread extraction: 1. Pass the post URL as prompt with output_schema to get structured thread data (original post + top replies ranked by engagement) 2. Use the returned structured data for analysis, commentary, or conversation
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.