mcp-exa
Related Servers
Alternatives to mcp-exa
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that integrates real-time web search capabilities into AI assistants using the Exa API, providing both basic and advanced search functionality with formatted markdown results.143MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server that integrates with Poe's API to provide AI-powered search and research tools from Perplexity, Reka, Exa, and Linkup.19 npm8MIT
- AlicenseAqualityCmaintenanceAn open-source MCP server providing AI agents with neural web search via Exa and tiered web fetch (Exa, local browser, Firecrawl) as a drop-in replacement for built-in web tools, preserving provenance and guarding against SSRF.623 PyPI2MIT
- AlicenseAqualityBmaintenanceAn MCP server that exposes Gemini's Deep Research Agent for comprehensive web research.212 npm4MIT
- AlicenseAqualityBmaintenanceMCP server that exposes SearXNG search and HTTP fetch tools for AI agents, enabling web search and clean page text extraction via natural language.4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for using various search tools like Tavily API. Planning to support various search tools (i.e. wiki search, searxng, etc)3MIT
TDQS
Scored across 9 tools
Most tools have clear boundaries (search, get_contents, find_similar, research_*), but answer and stream_answer are nearly identical except for streaming behavior, which could cause misselection. find_similar and search are related but distinct enough with descriptions.
The research_* tools follow a consistent prefix pattern, but the rest mix bare verbs (search, answer), verb_noun (find_similar, get_contents, stream_answer), and a long descriptive phrase (research_poll_until_finished), creating an inconsistent feel.
9 tools is a reasonable size for a search and research server, covering immediate searches, content retrieval, and async research workflows. Slightly more than strictly necessary due to answer/stream_answer duplication, but not excessive.
The core search, similar, content, answer, and research lifecycle (create, get, poll, list) are covered. A notable gap is the lack of a cancel/delete research operation, but most main workflows are complete.