Skip to main content
Glama
grok-native-search-mcp

grok-native-search-mcp

by zuozh11

Grok Native Search MCP

미니멀한 stdio MCP Server로, 세 가지 읽기 전용 도구를 제공합니다:

  • web_search(query): Grok 네이티브 Web Search

  • x_search(query): Grok 네이티브 X Search

  • web_fetch(url): Jina Reader 웹페이지를 Markdown으로 변환

검색은 항상 grok-4.6, reasoning.effort: low, max_turns: 1을 사용합니다. 단일 턴 내에서 보완 검색을 병렬로 실행할 수 있고, 충분한 1차 증거를 찾으면 중단하며, 증거가 없거나 충돌하는 경우에만 범위를 확장합니다. 도구 응답은 파싱하거나 재작성하지 않고 MCP 텍스트로 직접 반환됩니다.

도구 라우팅: URL을 알고 있거나 페이지 본문을 검증해야 할 때는 web_fetch를 사용합니다. X 게시물, 계정, 스레드, 트렌드는 x_search를 사용합니다. 명확한 URL이 없는 기타 웹 전체 검색은 web_search를 사용합니다. 검색 결과 검증이 필요한 외부 URL이 나오면 계속해서 web_fetch를 호출합니다.

환경 변수

변수

용도

XAI_API_KEY

xAI 또는 호환 게이트웨이의 API Key

XAI_BASE_URL

선택 사항, Responses API 기본 주소; 기본값은 https://aiapiv2.kamipon.com:442/v1

JINA_API_KEY

Jina Reader API Key

HTTP_PROXY / HTTPS_PROXY / NO_PROXY

선택 사항, Jina Reader 요청에만 사용되는 환경 프록시 설정

Related MCP server: Ollama Web Search

npx로 시작하기

npx -y grok-native-search-mcp@latest

Codex 설정

[mcp_servers.grok_native_search]
command = "npx"
args = ["-y", "grok-native-search-mcp@latest"]
env_vars = ["XAI_API_KEY", "JINA_API_KEY", "HTTP_PROXY", "HTTPS_PROXY", "NO_PROXY"]

설정 후 Codex를 다시 시작하세요.

로컬 개발

npm install
npm test

Available Tools

3 tools
web_fetchA
Read-only

Use this when an exact HTTP(S) URL is known, including URLs returned by web_search or x_search, and the task is to read, quote, summarize, or verify page text. Prefer it over Browser, curl, or shell when no login, click, form interaction, or visual inspection is required. Do not use it to discover URLs. Returns raw Markdown from Jina Reader.

Inputs: url (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: web_search for general web discovery, x_search specifically for X content, and web_fetch for retrieving a known URL. The descriptions explicitly cross-reference each other (e.g., web_search notes 'For X-only content use x_search'), leaving no ambiguity about which tool to select.

    Naming Consistency5/5

    All three tool names follow a consistent `[source]_[action]` pattern: web_search, x_search, web_fetch. The naming convention is uniform, predictable, and immediately conveys scope (web vs. x) and operation (search vs. fetch).

    Tool Count5/5

    With only 3 tools, the server is tightly scoped for its purpose: general web search, X-specific search, and URL fetching. This is well within the ideal 3–15 range and every tool earns its place; adding more would likely introduce redundancy.

    Completeness5/5

    The surface covers the full lifecycle of a search task: discover sources (web_search, x_search) and then retrieve/verify content (web_fetch). The tools explicitly reference each other to create a complete workflow, with no obvious gaps for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables real-time web search via DeepSeek's search-enhanced dialogue, providing search results as answers through MCP tools.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables web search and web fetch operations using Ollama's hosted APIs, allowing MCP clients to search the web and retrieve page content.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables web search, page fetching and cleaning, OCR from images, and broken-link checking through MCP tools, with multi-provider aggregation, caching, and anti-detection features.
      35 npm
      MIT