Primary capability
Search and clean fetch
Documentation ↗MCP server / search / source-linked
Exa MCP
Exa hosted MCP for web search, fetching and authenticated multi-step research. Its documented tradeoff is convenience versus authenticated usage: keyless search is easy to try, while agent_run and higher limits require a team connection. Treat structured output as a format aid, not truth validation.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Exa hosted MCP for web search, fetching and authenticated multi-step research. Its documented tradeoff is convenience versus authenticated usage: keyless search is easy to try, while agent_run and higher limits require a team connection. Treat structured output as a format aid, not truth validation.
Implementation source ↗
Exa hosted MCP for web search, fetching and authenticated multi-step research. Its documented tradeoff is convenience versus authenticated usage: keyless search is easy to try, while agent_run and higher limits require a team connection. Treat structured output as a format aid, not truth validation.
Implementation source ↗
Exa hosted MCP for web search, fetching and authenticated multi-step research. Its documented tradeoff is convenience versus authenticated usage: keyless search is easy to try, while agent_run and higher limits require a team connection. Treat structured output as a format aid, not truth validation.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- remote HTTP; local fallback
- Authentication
- keyless, OAuth or x-api-key
Use the official endpoint/package, store secrets outside committed config, and review returned tools before use.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
https://mcp.exa.ai/mcpWhat it actually exposes.
Concrete capabilities with maintainer sources.
Secondary capability
agent_run with sources/schema
Documentation ↗Workflow fit
Choose by transport, auth and state needs.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Proposed decision workflow (proposed; not tested)
Suggested evaluation, not an observed test result.
- Choose a bounded public test task.
- Record setup, tool calls and source URLs.
- Review result, cost and failure boundaries.
What to inspect: Suggested evaluation; not tested.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Explicit tool lists replace defaults.
Boundary reference ↗Free limits hide agent_run.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
Suggested evaluation; not tested.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Tavily MCP | Editorial inference: you need a different workflow. | Compare transport, auth and state tradeoffs. Documentation ↗ |
| Brave Search MCP | Editorial inference: you need another workflow. | Compare scope and operational tradeoffs. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
What should I verify first?
Confirm current endpoint, auth and returned tools.
Documentation ↗
Is this page a test result?
No; the workflow is a proposed editorial comparison.
Documentation ↗
Source trail.
Maintainer documentation used in this record.