Practical overview
When it fits
Use it when a compatible AI client needs Exa search or page-fetching tools, or when you want to expose optional research tools through the same MCP connection.
Who it is for
- Developers configuring MCP connections for AI clients
- Teams that want agents to search the web or retrieve page content as research context
- Users of supported clients such as Claude, Codex/ChatGPT, Cursor and Visual Studio Code
Documented uses
- Make web search available to an AI agent through MCP.
- Fetch webpage content as Markdown for an agent’s research context.
- Enable optional advanced search and crawling tools.
- Run multi-step research and return structured output through Exa Agent.
Requirements & limits
The README documents a hosted MCP endpoint and client plugin installation options. Exa Agent requires OAuth or an Exa API key.
- The default tool set includes web_search_exa and web_fetch_exa; advanced search and agent_run are optional.
- Selecting tools through the tools parameter replaces the defaults, so desired default tools must be included explicitly.
- Exa Agent requires OAuth or an API key.
- The public repository lists the MIT license and TypeScript as its primary language.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Connect a compatible MCP client to Exa
Add Exa’s hosted MCP server as a connection in a compatible client.
Before you start
- An MCP-compatible client
- The Exa MCP endpoint: https://mcp.exa.ai/mcp
Steps
Use the client’s Exa installation option if available, or open its MCP server configuration.
Add the server URL https://mcp.exa.ai/mcp using the client’s supported configuration method.
Save the connection in the client.
Expected outcome
The client is configured to connect to Exa MCP tools.
Guide limitations
- The repository gives client-specific installation paths but does not document a single setup flow for every client.
- This setup guidance does not verify a successful connection.
Select optional Exa MCP tools
Configure the hosted endpoint to expose a selected set of tools.
Before you start
- An MCP client configured to use Exa’s hosted endpoint
Steps
Choose the tools to expose, including any desired defaults such as web_search_exa and web_fetch_exa.
Append a tools parameter to the MCP URL listing the selected tools, separated by commas.
Use the resulting endpoint URL in the MCP client configuration.
Expected outcome
The endpoint URL specifies the selected tool set for the MCP connection.
Guide limitations
- The tools parameter replaces the defaults, so include every tool you want available.
- Exa Agent requires OAuth or an Exa API key.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- exa-labs/exa-mcp-server · Official homepage title · retained in its source language