Exa MCP server: web search for every agent

Web retrieval is useful when the task specifies the evidence it needs. Ask for primary-source documentation of an API change, recent implementation examples or a comparison with citations. A search result is an entry point, not evidence that the entire linked page was read.

For coding context, name the library and version. A working example from an older release can still be wrong for your application. Have the agent compare retrieved usage with local package types and the official documentation before changing code.

External pages can contain instructions aimed at the agent. Treat that text as source material, never as authority to use another connection or disclose local data. Search access does not require access to your inbox or deployment tools.

Exa MCP server: direct hosted, local and AIPx

Exa’s MCP page documents the hosted endpoint and default tool choices. The official server repository describes additional implementation options. These are related official routes, not three independent competing search providers.

Direct hosted Exa can be used free under the vendor’s conditions and is the simpler choice for a search-only client. AIPx’s Exa connector requires Pro because it is part of the gateway catalog. Its benefit is sharing search with other accounts and agent-specific tools, not changing Exa’s search quality or limits.

Connect Exa to Claude, Claude Code, Cursor or Codex

Choose Exa on AIPx Pro. This official hosted connection does not require storing your own Exa API key in the AIPx form.

1. Open the AIPx dashboard, choose Exa under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Exa; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Exa

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Exa is the only service you need.

Exa MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

After /mcp authorization, search for primary documentation of the installed library version. Inspect cited evidence before changing code. Claude Code MCP setup covers configuration scope and authentication.

Exa MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

Complete Cursor login and check for the default web_search_exa and coding-context tools. Match examples to the installed dependency version. See Cursor MCP setup for discovery troubleshooting.

Exa MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Exa credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

Custom ChatGPT MCP access can use Exa through an AIPx Pro agent. That gateway subscription does not supply ChatGPT connector eligibility. Check ChatGPT MCP setup before adding the endpoint.

Scope Exa search per agent

A research agent can have web search on Allow; a coding agent may also need coding context. Hide either tool where external queries are outside the task. Although these tools are reads, the query text is sent to an external service, so avoid including credentials or unnecessary private context.

The default read mode is Allow, and the recommendation narrows availability by job. MCP permissions controls the tool surface. Keep unrelated write tools hidden so an external search result cannot persuade the agent to publish or alter connected data.

For source-backed documentation, pair search with Notion reads. GitHub gives repository context, and Linear can hold a reviewed research task. Google Maps is a more specific source when the question is about places or routes.

Exa default tools and source limits

AIPx’s default URL has no tool-selection query parameters. Do not expect every optional researcher or crawler from the vendor catalog to appear. Inspect discovery to see what the connected endpoint actually provides.

Citations need to support the answer, and search snippets alone can omit conditions. For a consequential technical claim, read the primary documentation and compare it with the code you are changing. Provider limits still apply. The gateway adds another request processor and does not make retrieved content safe from prompt injection.

Browse all MCP integrations to choose another connection for this agent.

The Exa gateway connector requires AIPx Pro at $3/month; check AIPx pricing for gateway plans and keep provider or client charges separate.