websearch-mcp
Performs web searches via SearXNG, retrieving top N result URLs which are then fetched for full page content.
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., "@websearch-mcp Search PHP send email class and summarize the top 3 results."
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.
websearch-mcp
An MCP server that hooks into Claude Code and answers queries with full page content, not just snippets.
Flow when Claude calls the websearch tool:
Claude: websearch("PHP send email class")
→ 1. SearXNG search → top N result URLs (title + url + snippet)
→ 2. BrowserOS → open each URL as a background tab, read body text (no HTML)
→ 3. fallback → Playwright (headless Chromium) if present, else plain HTTP fetch
→ 4. return → [{title, url, text}] back to Claude"10 tabs at a time": BrowserOS opens up to WEBSEARCH_RESULTS background tabs in one batch and reads them in parallel. Any page that fails (blocked, DNS, 404) is skipped gracefully and reported, with a per-page fallback to Playwright/curl.
Setup
npm install
npm run buildNode 18+. Playwright is optional — if globally installed (npm root -g) the fallback picks it up automatically; otherwise it silently uses plain HTTP fetch.
Related MCP server: SearxNG MCP Server
Register in Claude Code
In the project you want to use it from, copy the template and set your absolute path:
cp .mcp.json.example .mcp.json # then edit <YOUR_CLONE_DIR>{
"mcpServers": {
"websearch": {
"command": "node",
"args": ["<YOUR_CLONE_DIR>/dist/index.js"],
"env": { "WEBSEARCH_SEARXNG_URL": "http://100.77.7.3:8890/search", "WEBSEARCH_BROWSEROS_URL": "http://127.0.0.1:9002/mcp" }
}
}
}
.mcp.jsonholds a machine-specific absolute path, so it's gitignored here — don't commit it. Configure per-machine from the.mcp.json.exampletemplate.
Then in a Claude Code session ask anything, e.g. "Search PHP send email class and summarize the top 3 results."
Config (env vars)
All config is via env vars in the MCP server entry — no code changes to move endpoints.
Var | Default | Meaning |
|
| SearXNG endpoint (JSON format auto-appended) |
|
| BrowserOS MCP (streamable HTTP) |
|
| Top N results to fetch full text for (max 12) |
|
| Truncate each page's text to this many chars (context budget) |
|
| Per-page read/navigation timeout |
|
| Use BrowserOS batch extraction |
|
| Fall back to headless Chromium |
|
| Last fallback: plain HTTP fetch |
Set WEBSEARCH_USE_BROWSEROS=0 to force the Playwright/curl path.
Tool
websearch(query, n?)—querystring,n= how many top results to read (defaultWEBSEARCH_RESULTS). Returns JSON:{ query, results: [{ title, url, text, source, error? }] }.sourceisbrowseros/playwright/curl;errorpresent on failures (e.g. bot-blocked).
Layout
src/
index.ts MCP stdio server + websearch tool
config.ts env-var config
searxng.ts SearXNG JSON search
text.ts html-strip / squash / bot-block heuristics
extraction/
extractor.ts orchestrates BrowserOS → playwright → curl
browseros.ts MCP *client* to BrowserOS (tabs new/list, read, close)
playwright.ts headless Chromium fallback (auto-resolves global install)
curl.ts realistic-browser HTTP fetch + cheerio text extractionAvailable Tools
1 toolwebsearchA
Search the web (SearXNG) and return the full body text of the top N results. Pages are loaded in parallel via BrowserOS, falling back to headless Chromium (Playwright) then plain HTTP fetch. Returns each result as {title, url, text}.
Inputs: query (required), n.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another. The tool's purpose is clearly defined as web search, with a detailed description of behavior.
With a single tool named 'websearch', there is no inconsistency or mixed conventions. The name is descriptive and matches the server's purpose.
The server has only one tool, which is borderline thin. However, for a focused web search server, a single tool can be appropriate, though it lacks the breadth of a multi-tool search suite.
The tool covers the core web search workflow, including fetching top results and body text. Minor gaps may exist such as advanced filtering options, but the essential functionality is present.
Maintenance
Related MCP Connectors
Live web search results and web pages as Markdown; page fetches use a residential network.
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
Real-time web search and page fetch for AI agents from Andi's own index. LLM-ready markdown output.
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
Related MCP Servers
- AlicenseAqualityFmaintenanceProvides web search functionality via DuckDuckGo for Claude Code and MCP-compatible clients, featuring advanced content exploration, navigation across search results, and detailed webpage analysis.317MIT
- AlicenseBqualityDmaintenanceProvides web search capabilities using SearxNG, allowing AI assistants like Claude to search the web with a privacy-respecting metasearch engine.112MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive web searching and content extraction using multiple search engines (Bing, Brave, DuckDuckGo) without API keys. Provides tools for full web searches with content extraction, quick search summaries, and single webpage content retrieval.1,194MIT
- FlicenseNot gradedqualityDmaintenanceProvides free web search, content fetching, image search, and deep research via SearXNG, no API keys required.-