A self-hosted SearXNG metasearch engine paired with the `mcp-searxng` MCP server, **built for LLMs, agents, and tool-using applications**. Lets your
A self-hosted SearXNG metasearch engine paired with the mcp-searxng MCP server, built for LLMs, agents, and tool-using applications. Lets your model (or autonomous agent) browse the web, run searches across many engines at once, and. The mcp websearch searxng mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
Prerequisites — The Prerequisites tool exposed by this serverYou will need one environment variable: SEARXNG_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Websearch Searxng's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by hypersniper05; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Websearch Searxng's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Variable | Description | Required |
|---|---|---|
| SEARXNG_SECRET | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.