grok-search-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@grok-search-mcpsearch X for recent posts about AI agents"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
grok-search-mcp
MCP server that brings Grok CLI web and X/Twitter search to Codex and Claude Code.
This project exists to give Codex and Claude Code a better search lane when
their built-in search experience is not enough. Grok's search, especially for
X/Twitter content, is often noticeably better than what these coding agents can
reach on their own. grok-search-mcp exposes that advantage through a small,
isolated MCP server, so agents can ask Grok for web or X search results without
turning Grok into a general chat dependency.
This project is intentionally narrow:
no xAI API key
no API credits
no image or video tools
no generic Grok chat tool
only web search and X/Twitter search through
grok
The server runs grok with an isolated HOME, so it does not load your normal
Cursor/Claude/Grok user-level MCP servers, hooks, or skills.
Tools
Tool | Purpose |
| Search X/Twitter through Grok CLI runtime search tools |
| Search the web through Grok CLI runtime web search |
Both tools return a JSON string with this shape:
{
"summary": "short summary",
"items": [],
"urls": [],
"rawText": "raw Grok answer",
"diagnostics": {
"mode": "x",
"parseOk": true,
"model": "grok-build",
"isolatedHome": "/Users/me/.grok-search-mcp",
"warnings": []
}
}If Grok does not return parseable JSON, the server keeps the raw answer and sets
diagnostics.parseOk=false.
Related MCP server: grok-build-plugin
Requirements
Node.js 20+
The official Grok CLI installed
A Grok CLI account/subscription that can use search
Install Grok CLI if needed:
curl -fsSL https://x.ai/cli/install.sh | bashOne-time login
The MCP server uses a dedicated profile home, defaulting to
~/.grok-search-mcp. Log in once for that isolated profile:
GROK_BIN="/Users/zhangyuze/.grok/bin/grok" \
GROK_SEARCH_MCP_HOME="$HOME/.grok-search-mcp" \
npx -y github:z2z23n0/grok-search-mcp loginYou do not need to log in for every search. Run this again only if the isolated profile token expires or is revoked.
Check the setup:
GROK_BIN="/Users/zhangyuze/.grok/bin/grok" \
GROK_SEARCH_MCP_HOME="$HOME/.grok-search-mcp" \
npx -y github:z2z23n0/grok-search-mcp doctordoctor should report:
{
"ok": true,
"authenticated": true,
"isolation": {
"hooks": 0,
"skills": 0,
"mcpServers": 0
}
}Client setup
Codex
Add this to ~/.codex/config.toml:
[mcp_servers.grok_search]
command = "npx"
args = ["-y", "github:z2z23n0/grok-search-mcp"]
enabled_tools = ["grok_x_search", "grok_web_search"]
default_tools_approval_mode = "auto"
startup_timeout_sec = 120
tool_timeout_sec = 240
[mcp_servers.grok_search.env]
GROK_BIN = "/Users/zhangyuze/.grok/bin/grok"
GROK_SEARCH_MCP_HOME = "/Users/zhangyuze/.grok-search-mcp"
GROK_SEARCH_MCP_MODEL = "grok-build"
NPM_CONFIG_REGISTRY = "https://registry.npmjs.org"Restart Codex after editing MCP config.
Claude Code
Add the MCP server with Claude Code's CLI:
claude mcp add --scope user --transport stdio grok-search \
--env GROK_BIN=/Users/zhangyuze/.grok/bin/grok \
--env GROK_SEARCH_MCP_HOME=$HOME/.grok-search-mcp \
--env GROK_SEARCH_MCP_MODEL=grok-build \
--env NPM_CONFIG_REGISTRY=https://registry.npmjs.org \
-- npx -y github:z2z23n0/grok-search-mcpCheck the registration:
claude mcp listExample prompts:
Use grok_search.grok_x_search to search X for recent @grok posts about Grok CLI.Use grok_search.grok_web_search to search docs.x.ai for Grok Build headless scripting.Environment
Variable | Default | Purpose |
|
| Path to the Grok CLI binary |
|
| Isolated profile home |
|
| Grok CLI model |
|
| Per-call timeout |
|
| Max Grok turns per search |
The server sets these for the Grok subprocess:
HOME=$GROK_SEARCH_MCP_HOMEXDG_CONFIG_HOME=$GROK_SEARCH_MCP_HOME/.configXDG_CACHE_HOME=$GROK_SEARCH_MCP_HOME/.cacheXDG_DATA_HOME=$GROK_SEARCH_MCP_HOME/.local/share
It also runs Grok from a temporary empty working directory instead of your repo.
Local development
npm install
npm test
npm run typecheck
npm run buildIntegration tests are skipped by default because they require a logged-in isolated Grok profile:
RUN_GROK_INTEGRATION=1 npm run test:integrationNotes
grok_x_search relies on Grok CLI agent runtime behavior. It does not call the
public xAI API x_search tool, so it avoids API billing but cannot promise API
level filtering or schemas.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/z2z23n0/grok-search-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server