exa-mcp-server and wet-mcp
These are competitors offering overlapping web search and content extraction capabilities, with Exa being the mature, production-ready option built on a specialized search API, while wet-mcp is an experimental alternative that likely wraps different underlying search providers or techniques.
About exa-mcp-server
exa-labs/exa-mcp-server
Exa MCP for web search and web crawling!
Implements an MCP (Model Context Protocol) server that exposes Exa's search APIs—including specialized code search and company research—via HTTP transport to integrate with AI assistants and code editors (Cursor, VS Code, Claude Desktop, etc.). Offers both basic tools (web search, code context, page crawling) and advanced filtering capabilities, with optional Claude Skills for domain-specific workflows like competitor analysis. Deploys as a hosted endpoint or npm package, requiring only an API key for authentication.
About wet-mcp
n24q02m/wet-mcp
MCP server for web search, content extraction, and documentation indexing
Provides embedded metasearch (SearXNG) with semantic reranking and query expansion, plus specialized academic research across Google Scholar, arXiv, and PubMed. Features local full-text documentation indexing with HyDE-enhanced retrieval, batch content extraction from up to 50 URLs, and multimodal analysis—all with zero-config local embeddings (Qwen3) or optional cloud providers. Integrates as an MCP server with Claude, Gemini, and Codex via stdio transport, with automatic setup and encrypted credential storage.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work