Skip to main content
Glama
kicito

xai-search-mcp

by kicito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xAI Search MCP Server

An MCP (Model Context Protocol) server that provides real-time web search and X (Twitter) search capabilities via the xAI API.

Quick Start

The easiest way to use this server is via npx — no clone or build required:

XAI_API_KEY=your_key npx @kicito/xai-search-mcp

Just set your XAI_API_KEY environment variable and configure your MCP client (see Configuration below).

Related MCP server: superhighway-mcp

Tools

web_search

Search the web in real-time. Returns results with source citations.

Parameter

Type

Required

Description

query

string

✅

The search query

allowed_domains

string[]

❌

Only search within these domains (max 5)

excluded_domains

string[]

❌

Exclude these domains from search (max 5)

x_search

Search X (Twitter) posts, users, and threads. Returns results with source citations.

Parameter

Type

Required

Description

query

string

✅

The search query for X posts

allowed_x_handles

string[]

❌

Only consider posts from these handles (max 10)

excluded_x_handles

string[]

❌

Exclude posts from these handles (max 10)

from_date

string

❌

Start date (ISO8601, e.g. 2025-01-01)

to_date

string

❌

End date (ISO8601, e.g. 2025-06-01)

Setup

Prerequisites

Install & Build

npm install
npm run build

Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "xai-search": {
      "command": "npx",
      "args": ["-y", "@kicito/xai-search-mcp"],
      "env": {
        "XAI_API_KEY": "your-xai-api-key-here"
      }
    }
  }
}

Cursor

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "xai-search": {
      "command": "npx",
      "args": ["-y", "@kicito/xai-search-mcp"],
      "env": {
        "XAI_API_KEY": "your-xai-api-key-here"
      }
    }
  }
}

If you prefer to clone and build manually:

git clone https://github.com/kicito/x_search_mcp.git
cd x_search_mcp
npm install
npm run build

Then use the full path in your config:

{
  "mcpServers": {
    "xai-search": {
      "command": "node",
      "args": ["/absolute/path/to/x_search_mcp/build/index.js"],
      "env": {
        "XAI_API_KEY": "your-xai-api-key-here"
      }
    }
  }
}

Environment Variables

Variable

Required

Default

Description

XAI_API_KEY

✅

—

Your xAI API key

XAI_MODEL

❌

grok-4-1-fast-reasoning

The xAI model to use

How It Works

The server uses the xAI Responses API with built-in server-side tools (web_search and x_search). When an MCP client calls one of the tools, the server:

  1. Sends the query to POST https://api.x.ai/v1/responses with the appropriate tool configuration

  2. Grok executes the search, gathers results, and generates a response

  3. Citations (source URLs) are extracted from the response annotations

  4. The response text and formatted citations are returned to the MCP client

Development

# Install dependencies
npm install

# Build
npm run build

# Start (requires XAI_API_KEY env var)
XAI_API_KEY=your-key npm start

License

MIT

Available Tools

2 tools

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.3
    • First observedweb_search
    • First observedx_search
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools target completely distinct domains: web_search is for general web content, while x_search is specifically for X (Twitter). There is no overlap in their search scopes, so an agent can easily distinguish between them.

Naming Consistency5/5

Both tools use a consistent verb_noun pattern (web_search, x_search), with the verb 'search' followed by a clear domain identifier. The naming is uniform and predictable.

Tool Count4/5

With only 2 tools, the server is minimal but justified for its focused purpose of providing real-time search across two specific sources (web and X). It could potentially include more search types, but the current count is reasonable for a specialized search server.

Completeness4/5

The server covers the primary search needs implied by its name: web and X/Twitter searches. Minor gaps like additional search options or filters are missing, but the core functionality is adequately addressed for basic real-time searches.

Resources

Related MCP Connectors

Related MCP Servers

  • perplexity-mcp-server

    cyanheads
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables AI agents to perform search-augmented queries and deep multi-source research using the Perplexity API.
    81 npm
    25
    Apache 2.0

  • evo-scry

    krich11
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for internet search via direct Google and DuckDuckGo HTML scraping with AI-powered result normalization and optional summarization, requiring no API keys for search.
    MIT