searxlens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | No | One SearXNG instance URL, or several separated by ';' for failover (tried in order). | http://localhost:8080 |
| SEARXLENS_MAX_RESULTS | No | Hard ceiling on count. | 20 |
| SEARXLENS_DEFAULT_RESULTS | No | Default results for web_search. | 8 |
| SEARXLENS_URL_CACHE_TTL_MS | No | read_url cache TTL in milliseconds. 0 disables. | 900000 |
| SEARXLENS_MAX_MULTI_QUERIES | No | Max sub-queries per multi_search call. | 6 |
| SEARXLENS_REQUEST_TIMEOUT_MS | No | Timeout per outbound HTTP request in milliseconds. | 10000 |
| SEARXLENS_SEARCH_CACHE_TTL_MS | No | Search result cache TTL in milliseconds. 0 disables. | 300000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web via SearXNG. Use for a single, well-formed query when you need current information. |
| multi_searchA | Run several related queries in parallel and merge the results, deduplicated by URL and ranked by how many sub-queries agreed on them. Use this for exploratory research on a topic ('search this from a few angles') rather than a single precise lookup. |
| read_urlA | Fetch a URL and extract its readable text (boilerplate stripped), for reading an article found via search in more depth. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, non-overlapping purpose: web_search for single precise queries, multi_search for exploratory multi-query research, and read_url for fetching page content. The descriptions explicitly contrast the two search tools, leaving no ambiguity.
web_search and multi_search follow a consistent [modifier]_search pattern, while read_url uses a verb_noun pattern. The naming is predictable and readable, with only a minor deviation in the third tool's structure.
Three tools is a well-scoped set for a search-and-read server. Each tool serves a distinct need without redundancy, and the count feels appropriately minimal yet complete for the stated purpose.
The toolset covers the core workflow of searching (both single and multi-query) and reading results. Minor gaps like advanced search filters or pagination are not included, but these are optional conveniences rather than essential dead ends for basic research.