Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
web_searchA
Deep web + X (Twitter) search. Grok runs the retrieval; you read the sources.

In native mode this calls xAI's Responses API with the real web_search and
x_search tools, so citations come back as structured API data rather than
text the model wrote. X search is the reason to reach for this tool: live
community reaction, developer chatter, and breaking discussion that does not
exist in a search index yet.

Use x_handles to pin the search to specific accounts, and from_date/to_date
to bound it in time (both ISO8601, e.g. 2026-08-01).

Returns:
- session_id: string (pass to get_sources for the full source list)
- content: string (answer only)
- sources_count: int (0 means retrieval genuinely returned nothing -- treat
  any factual claim in content as unverified)
- search_mode: "native" | "legacy" (which path actually served the request)
get_sourcesB
When you feel confused or curious about the search response content, use the session_id returned by web_search to invoke the this tool to obtain the corresponding list of information sources.
Retrieve all cached sources for a previous web_search call.
Provide the session_id returned by web_search to get the full source list.
web_fetchA
Fetches and extracts complete content from a URL, returning it as a structured Markdown document.

**Key Features:**
    - **Full Content Extraction:** Retrieves and parses all meaningful content (text, images, links, tables, code blocks).
    - **Markdown Conversion:** Converts HTML structure to well-formatted Markdown with preserved hierarchy.
    - **Content Fidelity:** Maintains 100% content fidelity without summarization or modification.

**Edge Cases & Best Practices:**
    - Ensure URL is complete and accessible (not behind authentication or paywalls).
    - May not capture dynamically loaded content requiring JavaScript execution.
    - Large pages may take longer to process; consider timeout implications.
web_mapA
Maps a website's structure by traversing it like a graph, discovering URLs and generating a comprehensive site map.

**Key Features:**
    - **Graph Traversal:** Explores website structure starting from root URL.
    - **Depth & Breadth Control:** Configure traversal limits to balance coverage and performance.
    - **Instruction Filtering:** Use natural language to focus crawler on specific content types.

**Edge Cases & Best Practices:**
    - Start with low max_depth (1-2) for initial exploration, increase if needed.
    - Use instructions to filter for specific content (e.g., "only documentation pages").
    - Large sites may hit timeout limits; adjust timeout and limit parameters accordingly.
get_config_infoA
Returns current Grok Search MCP server configuration and tests API connectivity.

**Key Features:**
    - **Configuration Check:** Verifies environment variables and current settings.
    - **Connection Test:** Sends request to /models endpoint to validate API access.
    - **Model Discovery:** Lists all available models from the API.

**Edge Cases & Best Practices:**
    - Use this tool first when debugging connection or configuration issues.
    - API keys are automatically masked for security in the response.
    - Connection test timeout is 10 seconds; network issues may cause delays.
switch_modelA
Switches the default Grok model used for search and fetch operations, persisting the setting.

**Key Features:**
    - **Model Selection:** Change the AI model for web search and content fetching.
    - **Persistent Storage:** Model preference saved to ~/.config/grok-search/config.json.
    - **Immediate Effect:** New model used for all subsequent operations.

**Edge Cases & Best Practices:**
    - Use get_config_info to verify available models before switching.
    - Invalid model IDs may cause API errors in subsequent requests.
    - Model changes persist across sessions until explicitly changed again.
toggle_builtin_toolsA
Toggle Claude Code's built-in WebSearch and WebFetch tools on/off.

**Key Features:**
    - **Tool Control:** Enable or disable Claude Code's native web tools.
    - **Project Scope:** Changes apply to current project's .claude/settings.json.
    - **Status Check:** Query current state without making changes.

**Edge Cases & Best Practices:**
    - Use "on" to block built-in tools when preferring this MCP server's implementation.
    - Use "off" to restore Claude Code's native tools.
    - Use "status" to check current configuration without modification.
plan_intentA
Phase 1 of search planning: Analyze user intent. Call this FIRST to create a session.
Returns session_id for subsequent phases. Required flow:
plan_intent → plan_complexity → plan_sub_query(×N) → plan_search_term(×N) → plan_tool_mapping(×N) → plan_execution

Required phases depend on complexity: Level 1 = phases 1-3; Level 2 = phases 1-5; Level 3 = all 6.
plan_complexityA

Phase 2: Assess search complexity (1-3). Controls required phases: Level 1 = phases 1-3; Level 2 = phases 1-5; Level 3 = all 6.

plan_sub_queryA

Phase 3: Add one sub-query. Call once per sub-query; data accumulates across calls. Set is_revision=true to replace all.

plan_search_termB

Phase 4: Add one search term. Call once per term; data accumulates. First call must set approach.

plan_tool_mappingC

Phase 5: Map a sub-query to a tool. Call once per mapping; data accumulates.

plan_executionC

Phase 6: Define execution order. parallel_groups: semicolon-separated groups of comma-separated IDs (e.g., 'sq1,sq2;sq3').

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation4/5

The core search/fetch tools (web_search, get_sources, web_fetch, web_map) are clearly distinct. The six planning tools (plan_*) are sequential phases with explicit ordering, so though they share a prefix, each has a unique purpose. Minor risk of confusion between plan_sub_query and plan_search_term, but descriptions clarify the difference.

Naming Consistency5/5

All tools use snake_case and follow a clear verb_noun pattern (e.g., web_search, get_sources, switch_model, plan_intent). The planning tools uniformly start with 'plan_' and the rest use action verbs. Consistent naming across the entire set.

Tool Count4/5

13 tools is a moderate count. The core search operations (search, fetch, map, sources) justify their presence, and the 6 planning tools form a structured workflow. While it feels slightly heavy for a search server, every tool has a defined role and the count is not excessive.

Completeness4/5

The tool set covers the search lifecycle: planning (plan_*), executing search (web_search), retrieving sources (get_sources), fetching content (web_fetch), and site exploration (web_map). Configuration and integration tools (get_config_info, switch_model, toggle_builtin_tools) round out the surface. Minor gap: no explicit tool to clear or manage cached sessions, but that is not a core search operation.

Maintenance

ActivityMaintained
ResponsivenessNo issues