Spicrawl vs Fetcher MCP
A side-by-side look at the Spicrawl and Fetcher MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Spicrawl for search & data extraction work as a local process; choose Fetcher MCP 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 Spicrawl when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SPICRAWL_API_KEY.
Choose Fetcher MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 37/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | SPICRAWL_API_KEY | None listed |
Tools & capabilities
Spicrawl tools
No tool names declared yet. Check the project README from the listing page.
Fetcher MCP tools
No tool names declared yet. Check the project README from the listing page.
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.
Spicrawl
{
"mcpServers": {
"spicrawl": {
"command": "npx",
"args": [
"-y",
"@spicrawl/mcp"
],
"env": {
"SPICRAWL_API_KEY": "YOUR_SPICRAWL_API_KEY_HERE"
}
}
}
}
Fetcher MCP
{
"mcpServers": {
"jae-jae-fetcher-mcp": {
"command": "npx",
"args": [
"-y",
"fetcher-mcp"
]
}
}
}
Frequently asked questions
Spicrawl is categorized under Search & Data Extraction and uses a local stdio subprocess. Fetcher MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Spicrawl for search & data extraction work and Fetcher MCP 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.
Spicrawl is listed as freemium — a free tier with paid plans. Auth: api key required. Fetcher MCP 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 spicrawl and jae-jae-fetcher-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Spicrawl has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Fetcher MCP has 60/100 (Good) with 6 views, 0 installs and 1,088 GitHub stars.
