Exa MCP Server
Related Servers
Alternatives to Exa MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA server that enables AI assistants like Claude to perform web searches using the Exa AI Search API, providing real-time web information in a safe and controlled way.222,768 npmMIT
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.822,768 npm5,048MIT
- AlicenseCqualityCmaintenanceA Model Context Protocol server implementation that enables AI assistants like Claude to perform Google searches and retrieve web data directly through natural language requests.1250 npm169MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to perform real-time web searches, retrieving up-to-date information from the internet via a Crawler API.197 npm41ISC
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI applications like Claude Desktop and Cursor IDE to perform web searches via DuckDuckGo's search engine.-
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides real-time web search capabilities to AI assistants through pluggable search providers, currently integrated with the Brave Search API.516MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_code_context_exa is specialized for programming-related searches with high-quality code context, while web_search_exa is for general web searches and URL scraping. There is no overlap in functionality, making it easy for an agent to choose the right tool based on the query type.
Both tools follow a consistent naming pattern: they use snake_case and start with a verb (get, search) followed by a noun (code_context, web), with a suffix (_exa) indicating the server. This uniformity makes the tool set predictable and easy to understand.
With only 2 tools, the server feels thin for its apparent scope of providing search capabilities via Exa AI. While the tools cover code-specific and general web searches, the lack of additional tools (e.g., for filtering, advanced queries, or other Exa features) limits functionality and suggests an incomplete surface for a search-oriented server.
The tool set is severely incomplete for a search server. It lacks essential operations such as configuring search parameters beyond result counts, handling pagination, saving or managing search history, or accessing other Exa AI features. This creates significant gaps that could lead to agent failures when more complex search tasks are required.