Skip to main content
Glama

searxng-mcp

SearXNG search MCP for Claude Code and Grok — privacy-respecting web search and page extraction for AI agents and any MCP client.

plugin-validate License: FSL-1.1-ALv2 Docs Claude Code plugin DeepWiki

searxng-mcp is a token-efficient Model Context Protocol (MCP) server that connects your self-hosted SearXNG metasearch instance to Claude Code, Anthropic-compatible clients, and other LLM / AI-agent tooling. You get privacy-respecting web search across 70+ engines plus readable page extraction — without shipping raw HTML into the model context.

Search, multi-query research, and fetch tools keep model-visible output short. Full result payloads stay in hidden _meta, so tokens go to answers. Deploy via stdio for local Claude workflows, or streamable-http / Docker for a self-hosted MCP service with optional Playwright rendered fetch for JS-heavy pages.

Install

Claude Code plugin (hub-first):

/plugin marketplace add 88plug/claude-code-plugins
/plugin install searxng@88plug

Grok Build

grok plugin marketplace add 88plug/claude-code-plugins
grok plugin install searxng@88plug --trust

Standalone MCP server — any client, no install step:

uvx --from git+https://github.com/88plug/searxng-mcp searxng-mcp
NOTE

You need a reachable SearXNG instance. Default base URL ishttp://127.0.0.1:8890. Override with SEARXNG_MCP_BASE_URL.

Related MCP server: SearXNG MCP Bridge

Quickstart

Point the server at a local SearXNG backend and confirm it is healthy:

export SEARXNG_MCP_BASE_URL=http://127.0.0.1:8890
uvx --from git+https://github.com/88plug/searxng-mcp searxng-mcp

In your MCP client, call health. A healthy backend returns ok: true with backend, cache, and render details. Then call search — you get a compact ranked list; the full payload stays in _meta.

Rendered fetch ships in the default install. If the host has Chromium or Chrome, the server uses it. Otherwise the first rendered fetch bootstraps Playwright Chromium into the user cache.

Features

Feature

Detail

Token-efficient MCP tools

Compact model-visible output; full payloads in hidden _meta

Parallel research

Multi-query search and fetch fan-out with dedupe and merged ranking

Rendered extraction

Playwright/Chromium path for JS-heavy pages; no extra install flags

Self-hosted deployment

stdio, streamable-http, SSE, Docker, and Compose for private MCP services

Thin by design

SearXNG does the search; this server shapes tools, cache, extract, transport

MCP tools

Tool

What it does

search

Concise web search; full raw payload in _meta

search_many

Parallel fan-out across queries, with dedupe and merged ranking

search_and_fetch

Search plus source extraction in one call

research

Multi-query search with batch fetches and merged, cited sources

fetch_url

Readable page extraction with citations

fetch_many

Parallel URL extraction with caching

health

Backend, cache, and render status

Tools surface as mcp__searxng__search, mcp__searxng__fetch_url, and so on.

Resources and optional prompts:

  • searxng://config — current settings, transport mode, and render support

  • searxng://guide — available tools and when to use each

  • quick_lookup, deep_research, research_workflow — optional prompts for clients that support prompt surfaces

Transports and deployment

Supports stdio, streamable-http, and sse.

Local stdio for desktop clients and private workflows:

SEARXNG_MCP_TRANSPORT=stdio uvx --from git+https://github.com/88plug/searxng-mcp searxng-mcp

Streamable HTTP for a private service or team deployment:

uvx --from git+https://github.com/88plug/searxng-mcp searxng-mcp \
  --transport streamable-http --host 0.0.0.0 --port 8811

Docker

docker build -t searxng-mcp .
docker run --rm -p 8811:8811 --add-host=host.docker.internal:host-gateway \
  -e SEARXNG_MCP_BASE_URL=http://host.docker.internal:8890 \
  searxng-mcp

Hardened image and Compose for a longer-running self-hosted service:

docker build -f Dockerfile.prod -t searxng-mcp:prod .
cp docker-compose.env.example .env
docker compose up --build -d
TIP

If you expose the HTTP transport, treat it like an internal service.fetch_url and fetch_many can request client-supplied URLs, so put streamable-http behind auth or a reverse proxy. Apply the same controls you would for any SSRF-capable tool. SEARXNG_MCP_FETCH_VERIFY_TLS=0 is only for private or self-signed backends.

Configuration

Common environment variables:

  • SEARXNG_MCP_BASE_URL — SearXNG base URL. Default http://127.0.0.1:8890

  • SEARXNG_MCP_FALLBACK_BASE_URLS — comma-separated fallback SearXNG instances

  • SEARXNG_MCP_TRANSPORT — stdio, streamable-http, or sse

  • SEARXNG_MCP_SEARCH_TIMEOUT — backend search timeout, seconds

  • SEARXNG_MCP_FETCH_TIMEOUT — fetch timeout, seconds

  • SEARXNG_MCP_SEARCH_CACHE_TTL — search cache TTL, seconds

  • SEARXNG_MCP_FETCH_CACHE_TTL — fetch cache TTL, seconds

  • SEARXNG_MCP_FETCH_VERIFY_TLS — set to 0 to skip TLS verification on fetches

  • SEARXNG_MCP_CACHE_DIR — cache directory path

  • SEARXNG_MCP_RENDER_TIMEOUT — browser navigation timeout for rendered fetches

  • SEARXNG_MCP_RENDER_WAIT_MS — extra wait after DOM content load

  • SEARXNG_MCP_RENDER_CONCURRENCY — concurrent rendered fetch limit

  • SEARXNG_MCP_RENDER_HEADLESS — set to 0 to show the browser

  • SEARXNG_MCP_RENDER_BROWSER_PATH — explicit Chromium or Chrome binary path

  • SEARXNG_MCP_RENDER_SANDBOX — set to 1 to keep Chromium sandboxing enabled

  • SEARXNG_MCP_RENDER_BLOCK_RESOURCES — set to 0 to allow images, fonts, stylesheets, and media

  • SEARXNG_MCP_RENDER_AUTO_FALLBACK — set to 0 to disable automatic rendered fallback

  • SEARXNG_MCP_RENDER_AUTO_MIN_WORDS — lower to make auto-render more aggressive

  • SEARXNG_MCP_RENDER_AUTO_MIN_CHARS — lower to make auto-render more aggressive

Client configs

Use either command shape with any MCP client:

  • searxng-mcp — when the entry point is on PATH (after uv sync from a checkout, or pipx install)

  • uvx --from git+https://github.com/88plug/searxng-mcp searxng-mcp — runs from this repo with no install step

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "searxng": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/88plug/searxng-mcp", "searxng-mcp"],
      "env": {
        "SEARXNG_MCP_BASE_URL": "http://127.0.0.1:8890",
        "SEARXNG_MCP_TRANSPORT": "stdio"
      }
    }
  }
}

See client configs for Codex CLI, gemini-cli, and more.

Benchmarks

uv run searxng-mcp-bench --rounds 3

Reports raw backend latency, token-visible output size, merged multi-query search latency, research latency, fetch extraction latency, rendered fetch latency, and batch variants.

Documentation

Full site: 88plug.github.io/searxng-mcp

Development

From a checkout:

uv sync
uv run searxng-mcp

Build and test:

uv sync --all-groups
uv run pytest -q
uv run python -m compileall src
uv run mkdocs build --strict

Contributions welcome. See CONTRIBUTING.md and the code of conduct.

License

Released under the Functional Source License, Version 1.1, ALv2 Future License (FSL-1.1-ALv2).

Free to use, copy, modify, and redistribute for any purpose except a Competing Use — offering this software (or a substantially similar substitute) as a commercial product or service. Each released version converts to the Apache License 2.0 on the second anniversary of its release date.

For commercial-use inquiries outside the Permitted Purpose: andrew@88plug.com.

Available Tools

7 tools
fetch_manyA
Read-onlyIdempotent

Fetch and extract several URLs in parallel. URLs are deduplicated after canonicalisation. Each per-source full text is preserved in hidden _meta.pages[].full_text. Best for: reading a batch of search results, comparing several known sources, building a multi-source citation set. Returns: per-source {title, url, excerpt, citations, render_mode} and aggregate stats (success_count, error_count, elapsed_ms). Rendered fetch is automatic for JS-heavy pages; pass rendered=true to force browser mode for every URL (slower). Use fetch_url for a single URL; research for an end-to-end multi-query workflow.

Inputs: urls (required), max_excerpt_chars, max_links, rendered, +3 more.

fetch_urlA
Read-onlyIdempotent

Fetch one URL, extract readable content (Readability-style), and return a compact excerpt plus link list. The full extracted text is preserved in hidden _meta.full_text. Best for: reading a known page after search/search_many, extracting clean prose from an article, getting an outbound-link list from a hub page. Returns: {title, url, excerpt, citations, links, content_type, render_mode} plus domain and word/char counts. Rendered fetch is automatic for JS-heavy pages; pass rendered=true to force browser mode when a previous fetch came back nearly empty. Use fetch_many for multiple URLs in one call; search_and_fetch if you do not yet have URLs.

Inputs: url (required), max_excerpt_chars, max_links, rendered, +2 more.

healthA
Read-onlyIdempotent

Report backend, cache, and render-engine readiness. Takes no arguments. Best for: a one-shot check before a session, debugging a 'search failed' result, verifying that the SearXNG backend is reachable and that rendered fetch is available. Returns: {backend, cache, render} with status, latency, and any active fallback URLs.

Inputs: no named parameters.

researchA
Read-only

Run multi-query research: search several queries in parallel, merge and dedupe results, then fetch and extract the strongest sources with citations. Best for: open-ended investigations, building a multi-source briefing, answering a complex question that needs cross-checking across providers. Returns: merged ranking, per-source extracted excerpts and citations, plus a query map showing which queries surfaced each source. Full payloads in hidden _meta. Rendered fetch is automatic for JS-heavy pages; pass rendered=true to force browser mode. Use search_many when extraction is not needed; search_and_fetch for a single query.

Inputs: queries (required), categories, engines, enabled_engines, +12 more.

search_and_fetchA
Read-only

Search SearXNG for one query and fetch+extract the top results in a single call. Combines search and fetch_many for one-query research workflows. Best for: answering one question that needs evidence from full pages, building a citation-backed answer to a single prompt, getting both ranked results and readable excerpts in one round-trip. Returns: search summary plus per-source {title, url, excerpt, citations, render_mode}. The full SearXNG payload and per-page full text are in hidden _meta. Rendered fetch is automatic for JS-heavy pages; pass rendered=true to force browser mode (slower). Use search if extraction is not needed; research for multi-query investigations.

Inputs: query (required), categories, engines, enabled_engines, +11 more.

search_manyA
Read-only

Run several SearXNG searches in parallel, then dedupe and merge their result sets into a single ranked list. Best for: broadening coverage on one topic with synonym/angle variants, comparing how different phrasings rank, building a high-recall source pool before fetching. Returns: merged hits with per-hit queries (which inputs surfaced it), engines, hit_count, and a merged_score. Per-query raw payloads are in hidden _meta. Use search for a single query; research when you also need the top sources fetched and excerpted in the same call.

Inputs: queries (required), categories, engines, enabled_engines, +8 more.

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 7 tools

    Disambiguation4/5

    Tools have distinct purposes, but search_and_fetch and research are similar enough that an agent might misselect if descriptions aren't carefully read. However, descriptions clearly differentiate them.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern in snake_case (fetch_url, search_many), but 'health' and 'research' deviate slightly. Overall pattern is recognizable.

    Tool Count5/5

    Seven tools cover the core operations of searching, fetching, and health checking without unnecessary bloat. The count is appropriate for the server's purpose.

    Completeness5/5

    The tool surface covers all typical workflows: single/multi search, single/multi fetch, combined search+fetch, and multi-query research. Health check ensures backend status. No obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that acts as a bridge to SearXNG instances, allowing AI models to perform web searches with privacy-focused search tools. It supports both STDIO and HTTP transports, featuring built-in rate limiting and session management.
      57 npm
      7
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      MCP server that provides a search_web tool to query a self-hosted SearXNG instance and return structured web search results.
      1
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server providing private web search, web page fetching, and current date/time tools, powered by a bundled SearXNG instance for API-key-free local search.
      2
      -