searxng-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_MCP_BASE_URL | No | SearXNG base URL | http://127.0.0.1:8890 |
| SEARXNG_MCP_CACHE_DIR | No | Cache directory path | |
| SEARXNG_MCP_TRANSPORT | No | Transport mode: stdio, streamable-http, or sse | |
| SEARXNG_MCP_FETCH_TIMEOUT | No | Fetch timeout in seconds | |
| SEARXNG_MCP_RENDER_SANDBOX | No | Set to 1 to keep Chromium sandboxing enabled | |
| SEARXNG_MCP_RENDER_TIMEOUT | No | Browser navigation timeout for rendered fetches | |
| SEARXNG_MCP_RENDER_WAIT_MS | No | Extra wait after DOM content load for rendered fetches | |
| SEARXNG_MCP_SEARCH_TIMEOUT | No | Backend search timeout in seconds | |
| SEARXNG_MCP_FETCH_CACHE_TTL | No | Fetch cache TTL in seconds | |
| SEARXNG_MCP_RENDER_HEADLESS | No | Set to 0 to show the browser | |
| SEARXNG_MCP_FETCH_VERIFY_TLS | No | Set to 0 to skip TLS verification on fetches | |
| SEARXNG_MCP_SEARCH_CACHE_TTL | No | Search cache TTL in seconds | |
| SEARXNG_MCP_FALLBACK_BASE_URLS | No | Optional comma-separated fallback SearXNG instances | |
| SEARXNG_MCP_RENDER_CONCURRENCY | No | Concurrent rendered fetch limit | |
| SEARXNG_MCP_RENDER_BROWSER_PATH | No | Explicit Chromium or Chrome binary path | |
| SEARXNG_MCP_RENDER_AUTO_FALLBACK | No | Set to 0 to disable automatic rendered fallback | |
| SEARXNG_MCP_RENDER_AUTO_MIN_CHARS | No | Lower this to make auto-render more aggressive | |
| SEARXNG_MCP_RENDER_AUTO_MIN_WORDS | No | Lower this to make auto-render more aggressive | |
| SEARXNG_MCP_RENDER_BLOCK_RESOURCES | No | Set to 0 to allow images, fonts, stylesheets, and media during render |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | 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 |
| search_manyA | 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 |
| search_and_fetchA | Search SearXNG for one query and fetch+extract the top results in a single call. Combines |
| researchA | 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 |
| fetch_urlA | Fetch one URL, extract readable content (Readability-style), and return a compact excerpt plus link list. The full extracted text is preserved in hidden |
| fetch_manyA | Fetch and extract several URLs in parallel. URLs are deduplicated after canonicalisation. Each per-source full text is preserved in hidden |
| healthA | 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: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| quick_lookup | Seed the fastest single-question workflow. |
| deep_research | Seed the broader multi-query research workflow. |
| research_workflow | Compatibility router that chooses quick_lookup or deep_research. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| config_resource | Machine-readable server configuration and capability summary. |
| guide_resource | Machine-readable workflow guidance for agent-driven clients. |
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.