SearchForge vs Fetch
A side-by-side look at the SearchForge and Fetch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SearchForge for search & data extraction work; choose Fetch 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 SearchForge when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You have the keys it needs:
SEARCHFORGE_SEARXNG_URL, SEARCHFORGE_API_KEY.
Choose Fetch 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 want tools like
fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 40/100 · Fair | 80/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SEARCHFORGE_SEARXNG_URLSEARCHFORGE_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 91,512 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View SearchForge | View Fetch |
Tools & capabilities
SearchForge tools
No tool names declared yet. Check the project README from the listing page.
Fetch tools 1
fetchFetches a URL from the internet and extracts its contents as markdown.
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.
SearchForge
No confirmed install command for SearchForge yet — follow the setup steps linked from its listing page rather than a guessed package name.
Fetch
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}
}