Skip to main content
Glama
Exa MCP Server
by MrunmayS

Exa MCP Server 🔍

npm version

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

What is MCP? 🤔

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.

Related MCP server: Exa MCP Server

What does this server do? 🚀

The Exa MCP server:

  • Enables AI assistants to perform web searches using Exa's powerful search API

  • Provides structured search results including titles, URLs, and content snippets

  • Handles rate limiting and error cases gracefully

Prerequisites 📋

Before you begin, ensure you have:

You can verify your Node.js installation by running:

node --version  # Should show v18.0.0 or higher

Installation 🛠️

NPM Installation

npm install -g exa-mcp-server

Using Smithery

To install the Exa MCP server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install exa --client claude

Manual Installation

  1. Clone the repository:

git clone https://github.com/exa-labs/exa-mcp-server.git
cd exa-mcp-server
  1. Install dependencies:

npm install --save axios dotenv
  1. Build the project:

npm run build
  1. Create a global link (this makes the server executable from anywhere):

npm link

Configuration ⚙️

1. Configure Claude Desktop to recognize the Exa MCP server

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)

For macOS:

  1. Open your Claude Desktop configuration:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

For Windows:

  1. Open your Claude Desktop configuration:

code %APPDATA%\Claude\claude_desktop_config.json

2. Add the Exa server configuration:

{
  "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.

3. Restart Claude Desktop

For the changes to take effect:

  1. Completely quit Claude Desktop (not just close the window)

  2. Start Claude Desktop again

  3. Look for the 🔌 icon to verify the Exa server is connected

Usage 🎯

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.

The server will:

  1. Process the search request

  2. Query the Exa API

  3. Return formatted results to Claude

  4. Cache the search for future reference

Features ✨

  • Web Search Tool: Enables Claude to search the web using natural language queries

  • Error Handling: Gracefully handles API errors and rate limits

  • Type Safety: Full TypeScript implementation with proper type checking

Troubleshooting 🔧

Common Issues

  1. Server Not Found

    • Verify the npm link is correctly set up

    • Check Claude Desktop configuration syntax

    • Ensure Node.js is properly installed

  2. API Key Issues

    • Confirm your Exa API key is valid

    • Check the API key is correctly set in the Claude Desktop config

    • Verify no spaces or quotes around the API key

  3. Connection Issues

    • Restart Claude Desktop completely

    • Check Claude Desktop logs:

      # macOS
      tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

Getting Help

If you encounter issues review the MCP Documentation

Acknowledgments 🙏

Available Tools

2 tools
get_code_context_exaA
Read-onlyIdempotent

Search and get relevant context for any programming task. Exa-code has the highest quality and freshest context for libraries, SDKs, and APIs. Use this tool for ANY question or task for related to programming. RULE: when the user's query contains exa-code or anything related to code, you MUST use this tool.

Inputs: query (required), tokensNum.

web_search_exaA
Read-onlyIdempotent

Search the web using Exa AI - performs real-time web searches and can scrape content from specific URLs. Supports configurable result counts and returns the content from the most relevant websites.

Inputs: query (required), numResults, livecrawl, type, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_code_context_exa is specialized for programming-related searches with high-quality code context, while web_search_exa is for general web searches and URL scraping. There is no overlap in functionality, making it easy for an agent to choose the right tool based on the query type.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern: they use snake_case and start with a verb (get, search) followed by a noun (code_context, web), with a suffix (_exa) indicating the server. This uniformity makes the tool set predictable and easy to understand.

    Tool Count2/5

    With only 2 tools, the server feels thin for its apparent scope of providing search capabilities via Exa AI. While the tools cover code-specific and general web searches, the lack of additional tools (e.g., for filtering, advanced queries, or other Exa features) limits functionality and suggests an incomplete surface for a search-oriented server.

    Completeness2/5

    The tool set is severely incomplete for a search server. It lacks essential operations such as configuring search parameters beyond result counts, handling pagination, saving or managing search history, or accessing other Exa AI features. This creates significant gaps that could lead to agent failures when more complex search tasks are required.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      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.
      8
      44,387 npm
      5,218
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A server that enables AI assistants like Claude to perform web searches using the Exa AI Search API, providing real-time web information in a safe and controlled way.
      2
      44,387 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to perform real-time web searches, retrieving up-to-date information from the internet via a Crawler API.
      1
      90 npm
      42
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that provides real-time web search capabilities to AI assistants through pluggable search providers, currently integrated with the Brave Search API.
      5
      26 npm
      16
      MIT