Grok Search MCP

Grok Search MCP

A local stdio MCP server that exposes xAI-compatible server-side search through a Responses API relay, providing web and X search tools with citation and cost reporting.

Category
Visit Server

README

Grok Search MCP

A local stdio MCP server that exposes xAI-compatible server-side search through a Responses API relay.

Tools

  • grok_web_search: public web search with optional allowed or excluded domains.
  • grok_x_search: X post/profile/thread search. This is deliberately separate and marked high-cost because one request can expand into many metered tool calls.

Both tools report citations, actual upstream tool-call counts, token usage, the effective model, and the relay's raw cost_in_usd_ticks value when present.

Configuration

Required at call time:

BOTCF_API_KEY

On Windows, run npm run setup for the first-install configuration window. Enter Base URLs, models, and API keys separated by semicolons; the positions are paired, and one model value may be reused for every provider. Public provider settings are stored in config.json, while the complete provider array including keys is stored as a current-user DPAPI ciphertext under %APPDATA%\grok-search-mcp\api-key.dpapi.

Requests rotate across configured providers. Recoverable network/timeout, authentication, rate-limit, route/model compatibility, and 5xx failures can switch to the next distinct provider. Each provider is attempted at most once and each MCP call has a hard maximum of three provider attempts. A failover can still duplicate upstream work if a provider accepted a request before its response was lost, so account-side spend limits remain necessary.

For CI or temporary sessions, GROK_SEARCH_PROVIDERS may contain a JSON provider array. The legacy BOTCF_API_KEY, BOTCF_BASE_URL, and GROK_SEARCH_MODEL variables remain supported.

Optional:

BOTCF_BASE_URL=https://botcf.com
GROK_SEARCH_MODEL=grok-4.5

The server starts and lists tools without a key, then fails closed with a clear error if a tool is called before BOTCF_API_KEY is configured. Secrets are never accepted as tool arguments or printed.

Each installation must use its own provider credentials. Do not share .env files, DPAPI ciphertext, setup screenshots, or API keys with other users.

Development

npm install
npm run check

Codex configuration

After building, register the compiled entry point and forward only the required environment variable:

[mcp_servers.grok_search]
command = "node"
args = ["D:/path/to/grok-search-mcp/dist/index.js"]
env_vars = ["GROK_SEARCH_PROVIDERS", "BOTCF_API_KEYS", "BOTCF_API_KEY", "GROK_SEARCH_BASE_URLS", "BOTCF_BASE_URL", "GROK_SEARCH_MODELS", "GROK_SEARCH_MODEL"]
startup_timeout_sec = 20
tool_timeout_sec = 180

No request is retried automatically. HTTP redirects are rejected so the API key cannot be forwarded to another origin.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured