searxng-mcp
searxng-mcp is an MCP server providing web search, content extraction, and research workflows powered by a SearXNG backend, with compact model-visible output and full payloads in hidden metadata.
search– Single web search query with options for engines, language, categories, safe search, time range, and pagination.search_many– Run multiple queries in parallel, deduplicate, and return a merged, ranked list — ideal for broader topic coverage.search_and_fetch– Combine search with automatic content extraction of top results; supports browser rendering for JS-heavy pages.research– Multi-query parallel search + batch fetch of top sources with citations — the most comprehensive single-call research tool.fetch_url– Fetch a single URL and extract readable content; auto-falls back to browser rendering for complex pages.fetch_many– Parallel fetch and content extraction from multiple URLs with caching and optional browser rendering.health– Check the status of the SearXNG backend, local cache, and browser render support.
Provides web search capabilities through SearXNG, offering tools for concise search results with full metadata preservation, parallel search operations, URL content extraction, and research workflows with batch fetching.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@searxng-mcp search for latest AI developments in quantum computing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
searxng-mcp
SearXNG search MCP for Claude Code and Grok — privacy-respecting web search and page extraction for AI agents and any MCP client.
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@88plugGrok Build
grok plugin marketplace add 88plug/claude-code-plugins
grok plugin install searxng@88plug --trustStandalone MCP server — any client, no install step:
uvx --from git+https://github.com/88plug/searxng-mcp searxng-mcpYou 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-mcpIn 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 |
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 |
| Concise web search; full raw payload in |
| Parallel fan-out across queries, with dedupe and merged ranking |
| Search plus source extraction in one call |
| Multi-query search with batch fetches and merged, cited sources |
| Readable page extraction with citations |
| Parallel URL extraction with caching |
| 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 supportsearxng://guide— available tools and when to use eachquick_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-mcpStreamable 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 8811Docker
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-mcpHardened 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 -dIf 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. Defaulthttp://127.0.0.1:8890SEARXNG_MCP_FALLBACK_BASE_URLS— comma-separated fallback SearXNG instancesSEARXNG_MCP_TRANSPORT—stdio,streamable-http, orsseSEARXNG_MCP_SEARCH_TIMEOUT— backend search timeout, secondsSEARXNG_MCP_FETCH_TIMEOUT— fetch timeout, secondsSEARXNG_MCP_SEARCH_CACHE_TTL— search cache TTL, secondsSEARXNG_MCP_FETCH_CACHE_TTL— fetch cache TTL, secondsSEARXNG_MCP_FETCH_VERIFY_TLS— set to0to skip TLS verification on fetchesSEARXNG_MCP_CACHE_DIR— cache directory path
SEARXNG_MCP_RENDER_TIMEOUT— browser navigation timeout for rendered fetchesSEARXNG_MCP_RENDER_WAIT_MS— extra wait after DOM content loadSEARXNG_MCP_RENDER_CONCURRENCY— concurrent rendered fetch limitSEARXNG_MCP_RENDER_HEADLESS— set to0to show the browserSEARXNG_MCP_RENDER_BROWSER_PATH— explicit Chromium or Chrome binary pathSEARXNG_MCP_RENDER_SANDBOX— set to1to keep Chromium sandboxing enabledSEARXNG_MCP_RENDER_BLOCK_RESOURCES— set to0to allow images, fonts, stylesheets, and mediaSEARXNG_MCP_RENDER_AUTO_FALLBACK— set to0to disable automatic rendered fallbackSEARXNG_MCP_RENDER_AUTO_MIN_WORDS— lower to make auto-render more aggressiveSEARXNG_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 onPATH(afteruv syncfrom a checkout, orpipx 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 3Reports 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-mcpBuild and test:
uv sync --all-groups
uv run pytest -q
uv run python -m compileall src
uv run mkdocs build --strictContributions 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 toolsfetch_manyARead-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_urlARead-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.
healthARead-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.
researchARead-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.
searchARead-only
Search the open web via SearXNG for a single query and return a compact, token-efficient summary of the top results.
Best for: quick fact-finding, current events, locating likely sources, single-question lookups.
Returns: ranked list of {title, url, domain, snippet, engine, score} plus answers, infoboxes, suggestions and corrections when SearXNG provides them. The full SearXNG payload is also available in hidden _meta.raw_payload.
Use search_many instead when running multiple parallel queries; search_and_fetch when you also need extracted page content; research for multi-query investigations with merged sources and fetched excerpts.
Inputs: query (required), categories, engines, enabled_engines, +7 more.
search_and_fetchARead-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_manyARead-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
Scored across 7 tools
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.
Most tools follow a verb_noun pattern in snake_case (fetch_url, search_many), but 'health' and 'research' deviate slightly. Overall pattern is recognizable.
Seven tools cover the core operations of searching, fetching, and health checking without unnecessary bloat. The count is appropriate for the server's purpose.
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
Related MCP Connectors
Web search API and MCP server for developers building AI agents.
One MCP server for all web data. Scrape, search, crawl, and AI research in one install.
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Serper MCP — wraps the Serper Google Search API (serper.dev)
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server for connecting agentic systems to search systems via searXNG.1132MIT
- AlicenseNot gradedqualityFmaintenanceAn 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 npm7MIT
- FlicenseAqualityDmaintenanceMCP server that provides a search_web tool to query a self-hosted SearXNG instance and return structured web search results.1-
- FlicenseNot gradedqualityBmaintenanceA 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-