Side-by-Side Model Context Protocol Comparison
Web Retrieval MCP vs Agent Search MCP
In-depth architectural comparison of the Web Retrieval MCP and Agent Search MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Web Retrieval MCP
Search & Data Extraction · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Agent Search MCP
Search & Data Extraction · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Web Retrieval MCP if you need specialized Search & Data Extraction tools running via a local process. Choose Agent Search MCP if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Web Retrieval MCP when:
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
- You have access to required keys:
EXA_API_KEY, FIRECRAWL_API_KEY, TAVILY_API_KEY. - Primary tools included: web_search, web_fetch.
Choose Agent Search MCP when:
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: free_search, free_search_advanced, free_extract.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Web Retrieval MCP Tools (2)
web_search
Neural web search via Exa. One block per result — each with its own title, URL, published date, highlights, and text — plus a `Sources` list. `mode` ∈ `auto` \
web_fetch
One URL's readable content through the tier chain, with a `[served by: …]` provenance header.
Agent Search MCP Tools (7)
free_search
Quick public-web search for current facts and discovery.
Use free_search_advanced for verification or domain filters. Use free_extract for one selected URL.
Returns compact multi-source evidence with confidence, relevance, source_count, stop_reason, evidence_budget, and partialFailures. Provider families are counted once even when several adapters use the same upstream. Optional API providers run only when credentials and policy allow.
@readOnly true @idempotent true — makes outbound HTTP requests to configured search engines. Injection detection and SSRF protection active.
free_search_advanced
Verification-oriented search with domain filters and waterfall fallback.
Use for claim checking, Chinese-source search, or publisher restrictions. Start with free_search for quick discovery. The response exposes source_count, stop_reason, evidence_budget, and partialFailures.
@readOnly true @idempotent true — runs waterfall progressive search across policy-allowed engines. Makes outbound HTTP requests to search engines and optionally to Jina Reader for content enrichment.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Web Retrieval MCP Configuration
Agent Search MCP Configuration
Frequently Asked Questions
More alternatives to Web Retrieval MCPMore alternatives to Agent Search MCPSearch & Data Extraction category hubCanonical compare URL