exa-mcp-server

Installation

Connect to Exa's hosted MCP server:

https://mcp.exa.ai/mcp

Or use a plugin when your client supports one.

Agent Plugin

This repository is an Agent Plugin. Install it with any compatible client.

Claude

Install from the Claude Plugin Marketplace, or run:

claude plugin install exa@claude-plugins-official

Codex / ChatGPT

Install via Plugins in ChatGPT, or run:

codex mcp add exa --url https://mcp.exa.ai/mcp

Other MCP Clients

Most clients can be configured manually with the standard mcpServers shape:

{
  "mcpServers": {
    "exa": {
      "type": "streamable-http",
      "url": "https://mcp.exa.ai/mcp",
    }
  }
}

Exa MCP works with most other clients, point them at https://mcp.exa.ai/mcp.

Available Tools

Default Tools

Optional Tools (enable via the tools parameter)

Enable tools by appending them to the MCP URL (this will replace the defaults, so include all you want):

https://mcp.exa.ai/mcp?tools=web_search_advanced_exa
https://mcp.exa.ai/mcp?tools=web_search_exa,web_fetch_exa,agent_run

Exa Agent requires authentication (OAuth or an API key).

Agent Skills

Skills live in skills/ and load with Agent Plugin installs. The Claude plugin in plugins/exa/ ships a copy of them; npm test fails when the copy drifts. Each package version bump on main publishes plugins/exa/ to the root of the claude-plugin branch, which Claude's plugin directory reads. To publish a plugin-only change between releases, run the Publish Claude plugin workflow manually.

Invoke from your client's skill UI (or /skill-name where supported). MCP-only setups still get the tools; skills add orchestration on top.

Authentication

The hosted MCP server works anonymously with rate limits. For higher limits and access to Exa Agent, use either OAuth or an API key.

OAuth is preferred: most clients prompt you to sign in to Exa. To force the login flow (useful for shared connectors and plugins), use https://mcp.exa.ai/mcp?login or https://mcp.exa.ai/mcp/oauth.

If you prefer, you can get an API key from the dashboard and pass it on the URL as ?exaApiKey=…. You can also send it as a Authorization: Bearer … header or an x-api-key header.

Built with ❤️ by Exa