Skip to content

Working with clients? Stay ahead of what they ask for.

VendorSearch

Exa Search MCP

by Exa Labs

Exa’s MCP server for finding web sources and fetching page content, with configurable advanced search and authenticated research capabilities.

★ 4,371·MIT
Share:

“A candidate for research that begins with a question and needs traceable web sources. Evaluate source relevance and support for the final claims separately from the presentation of the answer.”

Documentation guidance · sources below

PRACTICAL WORKFLOW REVIEW

· Documentation review. This assessment draws on Exa’s official repository and product documentation. Installation, tool execution and performance testing are outside this review.

Exa Search MCP suits work that starts with a question and needs sources to investigate. Its current hosted tools cover web search and page fetching, with additional research capabilities available through configuration and authentication. The useful output is a traceable set of sources and conclusions that a reader can inspect.

Jump to connection settings ↓

Suggested workflow: compare approaches with sources

Consider a builder investigating ways to connect an application to an external service. Define the question, required platform and acceptable publication dates, then ask for a short set of relevant sources. Review the candidates and fetch the pages that support the comparison. Keep each conclusion linked to a passage and distinguish vendor documentation from independent commentary.

Exa’s Search API documentation describes returned titles, URLs, dates and content options. Those fields help organise the evidence. For a decision that depends on an exact parameter or current limitation, open the underlying official page and check the relevant section. A search summary is a starting point for that verification.

Documented setup and tool selection

The official MCP guide documents the hosted endpoint at https://mcp.exa.ai/mcp, keyless access within rate limits, OAuth and API-key authentication. The repository also links client setup instructions. Choose the account and usage arrangement before making the connection part of a recurring team workflow.

The current tool list includes web_search_exa and web_fetch_exa. Advanced search is an opt-in tool with additional controls; agent_run adds multi-step research and requires authentication. An explicit tools URL parameter replaces the default selection, so include each intended tool and refresh the client’s discovered tool list after configuration changes.

Selection advice: discovery, context and evidence

Use discovery when the relevant sources are still being identified, then retrieve a selected URL for closer reading. Exa’s content documentation distinguishes relevant highlights, full text and generated summaries. Match the content view to the task: a narrow factual question needs a supporting passage, while reviewing a document’s argument may require wider context.

Keep the initial question specific and set a source budget. For an advanced search, check which date and domain controls the enabled tool exposes. For multi-step research, agree the desired output and usage limit first. Exa and a scraper such as Firecrawl have overlapping capabilities; compare them against your actual discovery and extraction requirements.

Proposed acceptance check

Prepare several questions with known authoritative sources and one open research question. Check source relevance, dates, accessible passages and whether the final answer’s claims match those passages. Record tool selection, authentication mode, usage, failures and the reviewer’s corrections. Score relevance and evidence quality separately so an attractive answer and a well-supported answer receive distinct evaluation.

INSTALL THIS SERVER

Access optionsKeyless hosted search within limits, OAuth, or an API key. Multi-step Exa Agent research requires authentication.

Follow the provider’s current setup guide for your client and deployment. Check the available tools and permissions after connecting.

3 SELECTED TOOLS

web_search_exa
Search the web for relevant sources and content
Read
web_fetch_exa
Read content from one or more known URLs
Read
web_search_advanced_exa
Opt-in search with additional filters and controls
Read

OUR ASSESSMENT

The current hosted Exa MCP guide lists search and page-fetch tools, opt-in advanced search and authenticated multi-step research. This supplement reviews that interface and its configuration. Suggested tasks and acceptance checks are editorial guidance; relevance, usage and answer quality need evaluation against the intended questions.

Strengths
  • Web discovery and page fetching in the hosted tool surface
  • Opt-in advanced search controls
  • Documented keyless, OAuth and API-key access options
  • Explicit hosted tool selection through the connection URL
Weaknesses
  • Source relevance and claim support need checking for each research task
  • Explicit tool selection replaces the default hosted tool list
  • Authenticated research has usage implications that need a defined budget
Security Notes

Choose the Exa account and authentication mode for the intended workload. Keep API keys in supported secret or header configuration. Review the enabled tools and agree a usage limit before recurring or multi-step research; check the selected plan’s current terms and controls.

Best For

Builders researching an unfamiliar topic and assembling a short, inspectable source set.

TECHNICAL DETAILS

Language
typescript
Transport
streamable-http
Clients
Claude DesktopClaude CodeCursorVS CodeWindsurf
License
MIT
GitHub
npm
exa-mcp-server

RECORDED ADOPTION METRICS

Saved directory snapshots. Record last checked MAY 3, 2026. The review date above does not refresh these figures.

// GitHub Stars
4,371
// Popularity Rank
#1
Recorded directory rank · #1 in Search

SOURCES & RECORDED CHECKS

These are the directory listings and check details held in this record. Client compatibility, directory listings and installation testing are separate signals. Recorded client names describe the scope of a check; they do not establish a security assessment or a recurring test schedule.

01
Discovered
Source not recorded
First indexed MAY 3, 2026
02
Directory listings
5 directories
PulseMCP, MCP.so, Glama, Smithery, Official MCP Registry
03
Recorded client testing
Testing not recorded
Check current setup against the provider documentation
04
Record last checked
MAY 3, 2026
Record date; functional retest scope may differ
// How other directories see it

The same server, 5 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.

SourceTheir ratingTheir star countTheir downloadsLast synced
AutomationSwitch This page4.6editorial4,371—MAY 3, 2026
PulseMCP— unratedunavailableunavailableMAY 3, 2026
MCP.so— unratedunavailableunavailableMAY 3, 2026
Glama— unratedunavailableunavailableMAY 3, 2026
Smithery— unratedunavailableunavailableMAY 3, 2026
Official MCP Registry— unratedunavailableunavailableMAY 3, 2026

// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.

OTHER SEARCH MCP SERVERS

// Get in touch

DISCUSS YOUR
MCP REQUIREMENTS.

Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.

Discuss Your MCP Requirements →