A 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.
Demo video https://www.loom.com/share/ac676f29664e4c6cb33a2f0a63772038?sid=0e72619f-5bfc-415d-a705-63d326373f60
The Model Context Protocol (MCP) is a system that lets AI apps, like Claude Desktop, connect to external tools and data sources. It gives a clear and safe way for AI assistants to work with local services and APIs while keeping the user in control.
The Exa MCP server:
Before you begin, ensure you have:
You can verify your Node.js installation by running:
node --version # Should show v18.0.0 or higher
npm install -g exa-mcp-server
To install the Exa MCP server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install exa --client claude
git clone https://github.com/exa-labs/exa-mcp-server.git
cd exa-mcp-server
npm install
npm run build
npm link
You can find claude_desktop_config.json inside the settings of Claude Desktop app:
Open the Claude Desktop app and enable Developer Mode from the top-left menu bar.
Once enabled, open Settings (also from the top-left menu bar) and navigate to the Developer Option, where you'll find the Edit Config button. Clicking it will open the claude_desktop_config.json file, allowing you to make the necessary edits.
OR (if you want to open claude_desktop_config.json from terminal)
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
code %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"exa": {
"command": "npx",
"args": ["/path/to/exa-mcp-server/build/index.js"],
"env": {
"EXA_API_KEY": "your-api-key-here"
}
}
}
}
Replace your-api-key-here
with your actual Exa API key from dashboard.exa.ai/api-keys.
The Exa MCP server includes the following tools:
You can choose which tools to enable by adding the --tools
parameter to your Claude Desktop configuration:
{
"mcpServers": {
"exa": {
"command": "npx",
"args": [
"/path/to/exa-mcp-server/build/index.js",
"--tools=twitter_search"
],
"env": {
"EXA_API_KEY": "your-api-key-here"
}
}
}
}
For enabling multiple tools, use a comma-separated list:
{
"mcpServers": {
"exa": {
"command": "npx",
"args": [
"/path/to/exa-mcp-server/build/index.js",
"--tools=web_search,research_paper_search,twitter_search"
],
"env": {
"EXA_API_KEY": "your-api-key-here"
}
}
}
}
If you don't specify any tools, all tools enabled by default will be used.
For the changes to take effect:
If you prefer to run the server directly, you can use npx:
# Run with all tools enabled by default
npx exa-mcp-server
# Enable specific tools only
npx exa-mcp-server --tools=web_search
# Enable multiple tools
npx exa-mcp-server --tools=web_search,research_paper_search
# List all available tools
npx exa-mcp-server --list-tools
Once configured, you can ask Claude to perform web searches. Here are some example prompts:
Can you search for recent developments in quantum computing?
Search for and summarize the latest news about artificial intelligence startups in new york.
Find and analyze recent research papers about climate change solutions.
Search Twitter for posts from @elonmusk about SpaceX.
Find tweets from @samaltman that were published in the last week about AI safety.
The server will:
You can test the server directly using the MCP Inspector:
npx @modelcontextprotocol/inspector node ./build/index.js
This opens an interactive interface where you can explore the server's capabilities, execute search queries, and view cached search results.
Server Not Found
API Key Issues
Connection Issues
# macOS
tail -n 20 -f ~/Library/Logs/Claude/mcp*.log
# Windows
type "%APPDATA%\Claude\logs\mcp*.log"
Seamless access to top MCP servers powering the future of AI integration.