Open Agent Search vs MCP SearXNG
A side-by-side look at the Open Agent Search and MCP SearXNG MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Open Agent Search for search & data extraction work as a local process; choose MCP SearXNG for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Open Agent Search when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
Choose MCP SearXNG when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
SEARXNG_URL. - You want tools like
searxng_web_search, searxng_search_suggestions, searxng_instance_info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 45/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | SEARXNG_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 1,320 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Open Agent Search | View MCP SearXNG |
Tools & capabilities
Open Agent Search tools
No tool names declared yet. Check the project README from the listing page.
MCP SearXNG tools 4
searxng_web_searchSearches 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 `query` (not `prompt`, `q`, or any other name). Calls an external SearXNG instance; availability depends on the `SEARXNG_URL` configuration. Use `pageno` to paginate results; combine `time_range` and `language` to narrow scope. When `engines` and `time_range` are both provided, every selected engine must explicitly advertise time-range support via SearXNG /config; otherwise the request is rejected before search. To read the full text of a result URL, follow up with `web_url_read`.searxng_search_suggestionsReturns autocomplete suggestions from the configured SearXNG instance. Use this to refine vague or partial queries before searching.searxng_instance_infoDiscovers capabilities from all reachable configured SearXNG instances via /config, including categories.common/available, engines.common/available, defaults, locales, and plugins.web_url_readFetches 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 `startChar`/`maxLength` to paginate large pages. (2) Section extraction — set `section` to return content under a specific heading. (3) Headings only — set `readHeadings: true` to list all headings (mutually exclusive with other filtering params). Returns an error string if the URL is unreachable or content cannot be extracted. Use after `searxng_web_search` to read the full content of individual result URLs.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Open Agent Search
{
"mcpServers": {
"open-agent-search": {
"command": "npx",
"args": [
"--yes",
"open-agent-search@1.0.5"
]
}
}
}
MCP SearXNG
{
"mcpServers": {
"ihor-sokoliuk-mcp-searxng": {
"command": "npx",
"args": [
"-y",
"mcp-searxng"
],
"env": {
"SEARXNG_URL": "YOUR_SEARXNG_URL_HERE"
}
}
}
}
Frequently asked questions
Open Agent Search is categorized under Search & Data Extraction and uses a local stdio subprocess. MCP SearXNG belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Open Agent Search for search & data extraction work and MCP SearXNG for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Open Agent Search has no declared pricing — check the project's own site. MCP SearXNG is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add open-agent-search and ihor-sokoliuk-mcp-searxng as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Open Agent Search has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. MCP SearXNG has 67/100 (Great) with 4 views, 0 installs and 1,320 GitHub stars.