mcp-searxng
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BYPARR_URL | No | URL of the Byparr instance for browser solver support. | |
| SEARXNG_URL | Yes | The URL of your SearXNG instance (or semicolon-separated list of interchangeable replicas). This is the only required variable. | |
| MCP_HTTP_HOST | No | Host/interface to bind for HTTP transport. Defaults to 127.0.0.1. | |
| MCP_HTTP_PORT | No | Port for HTTP transport mode. Set to use HTTP instead of STDIO. | |
| SEARXNG_FANOUT | No | When true, queries all healthy replicas in parallel and merges results. | |
| MCP_HTTP_HARDEN | No | When true, enables hardened mode for HTTP transport. | |
| FLARESOLVERR_URL | No | URL of the FlareSolverr instance for browser solver support. | |
| MCP_HTTP_STATELESS | No | When true, enables stateless HTTP mode. | |
| SEARXNG_LITE_TOOLS | No | When true, uses minimal tool schemas for local models. | |
| SEARXNG_MAX_RESULTS | No | Operator ceiling for maximum number of results (1-20). | |
| MCP_HTTP_TRUST_PROXY | No | When true, trusts proxy headers for rate limiting and logging. | |
| SEARXNG_HTML_FALLBACK | No | When true, falls back to HTML parsing for instances that reject format=json. | |
| SEARXNG_MAX_RESULT_CHARS | No | Truncates result content in compact and full text/JSON responses. | |
| SEARXNG_DEFAULT_RESPONSE_FORMAT | No | Default response format for search calls: 'text' or 'json'. | |
| URL_READ_MAX_CONTENT_LENGTH_BYTES | No | Maximum content length in bytes for URL reading, also caps PDF input and extracted text. |
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 | {} |
| logging | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searxng_web_searchA | Searches the web using SearXNG and returns a list of results, each with a title, URL, and content snippet. CRITICAL: The required parameter name is exactly |
| searxng_search_suggestionsA | Returns autocomplete suggestions from the configured SearXNG instance. Use this to refine vague or partial queries before searching. |
| searxng_instance_infoA | Discovers capabilities from all reachable configured SearXNG instances via /config, including categories.common/available, engines.common/available, defaults, locales, and plugins. |
| web_url_readA | Fetches a URL and returns readable content as markdown. Content-type aware: HTML is converted to markdown; JSON is pretty-printed; plain text, YAML, TOML, and XML are returned as fenced readable text. PDF text extraction is supported with bounded input, output, page count, time, concurrency, and memory; OCR is not supported. Binary, media, archive, and octet-stream downloads other than PDFs are intentionally rejected instead of being returned as raw bytes. When the operator configures browser solvers, mcp-searxng attempts FlareSolverr first and then Byparr only after a busy or transient-unavailable acquisition; cache hits bypass acquisition and a final busy or unavailable provider uses one uncached direct-fetch fallback. Three modes: (1) Full content — omit filtering params; use |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Configuration | Current server configuration and environment variables |
| Usage Guide | How to use the MCP SearXNG server effectively |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: web search, search suggestions, instance configuration, and URL content retrieval. No overlapping functionality between the tools.
Three tools use the 'searxng_' prefix, but 'web_url_read' breaks the pattern. Verb placement varies (e.g., 'web_search' vs 'url_read'), and some names are noun-heavy like 'instance_info' and 'search_suggestions'.
Four tools is well-scoped for a SearXNG integration, covering search, refinement, instance discovery, and content reading without unnecessary bloat.
The set covers the core search workflow end-to-end: from query and suggestions to reading result content. Minor gaps like OCR or advanced result parsing are not essential for the intended purpose.