searxlens-mcp
Provides web search capabilities through a SearXNG instance, including single searches, parallel multi-query searches with merged and deduplicated results, and reading and extracting readable text from URLs.
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., "@searxlens-mcp Research the effects of remote work on productivity from several angles"
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.
searxlens-mcp
An MCP server for web search via SearXNG, built for research-style workflows: it can fan a topic out across several related queries and merge the results, not just answer one query at a time.
Inspired by the broader mcp-searxng ecosystem.
Tools
web_search
A single search against SearXNG. Supports count, language, categories,
time_range, pageno, and min_score (drops results below a relevance
threshold, when the instance reports scores). Results are cached in-memory
for SEARXLENS_SEARCH_CACHE_TTL_MS.
multi_search — the differentiator
Takes 2+ related queries, runs them in parallel, and merges the results:
deduplicates by normalized URL (ignores
utm_*tracking params, trailing slashes, and fragments)a URL surfaced by more than one sub-query is ranked above one found by only a single sub-query — cross-query agreement is treated as a stronger signal than any one engine's relevance score
ties are broken by SearXNG's own score, when present
Good for "research this topic from a few angles" prompts, where a single query would miss results that a slightly different phrasing would catch.
read_url
Fetches a URL and extracts its readable text — strips <script>, <nav>,
<footer>, etc., and picks the largest remaining content block (a light
readability heuristic, not a full port of Mozilla Readability). Cached for
SEARXLENS_URL_CACHE_TTL_MS.
Related MCP server: Web Search MCP Server
Configuration
Variable | Default | Description |
|
| One instance, or several separated by |
|
| Default results for |
|
| Hard ceiling on |
|
| Search result cache TTL. |
|
|
|
|
| Max sub-queries per |
|
| Timeout per outbound HTTP request. |
Your SearXNG instance needs JSON output enabled — in settings.yml:
search:
formats:
- html
- jsonInstall & run
npm install
npm run buildMCP client config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"searxlens": {
"command": "node",
"args": ["/absolute/path/to/searxlens-mcp/build/index.js"],
"env": { "SEARXNG_URL": "http://localhost:8080" }
}
}
}Roadmap
Rough priority order for what's next — not committed, just notes for whoever picks this up:
HTTP transport (
MCP_HTTP_PORT), for remote/shared deploymentsInstance capability discovery (
/config) toolHTML fallback when an instance rejects
format=jsonReal test suite (currently just a manual smoke script) + CI
Docker image
Optional: rank fusion in
multi_searchusing reciprocal rank fusion instead of raw hit-count, for more principled merging
License
MIT
Available Tools
3 toolsmulti_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.
Inputs: queries (required), language, time_range, count_per_query.
read_urlA
Fetch a URL and extract its readable text (boilerplate stripped), for reading an article found via search in more depth.
Inputs: url (required), max_length.
web_searchA
Search the web via SearXNG. Use for a single, well-formed query when you need current information.
Inputs: query (required), count, pageno, language, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Web search, URL content extraction to Markdown, site mapping, and recursive web crawler.
Search the web, fetch any URL and map a site as clean, LLM-ready Markdown.
Web search, Google SERP, page extraction to markdown and cited answers for AI agents.
Web search and page reading for AI agents, including JSON APIs, RSS feeds and YouTube.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides web search capabilities using SearxNG, allowing AI assistants like Claude to search the web with a privacy-respecting metasearch engine.112MIT
- AlicenseNot gradedqualityDmaintenanceEnables web search across multiple search engines (DuckDuckGo, Bing, Startpage) with parallel execution and result deduplication. Also provides web page content extraction capabilities.2MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to perform web searches and read URL content via a SearXNG instance.210 npmMIT
- AlicenseAqualityDmaintenanceEnables private web search and webpage content extraction using a local SearxNG instance, prioritizing user privacy and autonomy.212 PyPI2MIT