exa-search
Related Servers
Alternatives to exa-search
No user-submitted related servers found.
Related Servers
- 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
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to perform real-time web searches using the Exa AI Search API in a safe and controlled manner.222,768 npm-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots.3999 npm20MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots in real-time.4999 npm9MIT
- AlicenseBqualityFmaintenanceA Model Context Protocol (MCP) server for web research. Bring real-time info into Claude and easily research any topic.3999 npm298MIT
- FlicenseAqualityCmaintenanceEnables AI assistants like Claude to perform web searches using the Exa AI Search API, providing real-time structured search results.16-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one is specialized for programming-related searches (code context), while the other is for general web searches. There is no overlap in functionality, and the descriptions explicitly differentiate their use cases.
Both tools follow a consistent naming pattern: they use snake_case and start with a verb (get, search) followed by a noun phrase (code_context, web). This makes them predictable and easy to understand.
With only two tools, the server feels under-scoped for a search domain. While the tools cover distinct areas (code and web), a search server typically benefits from more granular operations like filtering, pagination, or specialized search types, making this set feel thin.
The tools cover two key search domains (code and web), but there are notable gaps. For example, there are no tools for advanced search configurations, result management, or handling different content types beyond code and general web pages, which limits flexibility for agents.