exa-mcp-server and one-search-mcp
These are competitors offering overlapping web search and scraping capabilities, with Exa being the established, production-ready option while OneSearch provides a more flexible multi-backend approach supporting various search providers.
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 one-search-mcp
yokingma/one-search-mcp
🚀 OneSearch MCP Server: Web Search & Scraper & Extract, Support agent-browser, SearXNG, Tavily, DuckDuckGo, Bing, etc.
Implements Model Context Protocol (MCP) server with pluggable search backends (SearXNG, Tavily, DuckDuckGo, Bing, Google, etc.) and exposes four tools—`one_search`, `one_scrape`, `one_map`, `one_extract`—for web search, scraping, and structured data extraction. Uses local browser automation via `agent-browser` for privacy-preserving searches and scraping without external API dependencies, with automatic Chromium detection across Chrome, Edge, and Canary installations. Integrates with Claude Desktop, Cursor, and Windsurf through standard MCP configuration files.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work