Exa MCP server in n8n web search for your workflows.
Exa gives n8n's AI Agent node fast, intelligent web search, crawling, and code-context lookup over MCP. There's no config file to edit — you wire it up with a single MCP Client Tool node.
Exa (4.6k GitHub stars, github.com/exa-labs/exa-mcp-server) is a search-category MCP server that gives agents fast, intelligent web search and crawling, including a code-context search tool. In n8n, that means your AI Agent workflows can pull live web results and page content mid-run instead of working from stale model knowledge.
n8n is different from desktop MCP clients: there is no JSON config file. MCP servers are attached per-workflow through the MCP Client Tool node, and because Exa ships as a hosted remote server, you point that node at a URL rather than spawning a local process. This page walks through exactly that.
Before you start
You need two things: an n8n instance recent enough to include the MCP Client Tool node (it attaches to the AI Agent node as a tool), and an Exa API key from your Exa dashboard. Because Exa runs as a remote server, your n8n instance — cloud or self-hosted — only needs outbound HTTPS access; nothing gets installed on the n8n host.
You can see what the server exposes, including its probed tool list, on Exa's live listing at https://loomal.ai/marketplace/exa before you wire anything up.
Add the MCP Client Tool node
Open the workflow that contains your AI Agent node, click the + under the agent's Tools slot, and pick MCP Client Tool. Set the endpoint to Exa's hosted MCP URL with your API key in the query string, and choose the HTTP Streamable transport. These are the values to enter in the node:
{
"endpointUrl": "https://mcp.exa.ai/mcp?exaApiKey=YOUR_EXA_API_KEY",
"serverTransport": "httpStreamable",
"authentication": "none"
}Verify the connection
Once the node is configured, n8n queries the server and lists the tools it found — you should see Exa's search, crawling, and code-context tools appear in the node's tool list. Run the workflow with a prompt that obviously needs fresh information ("what changed in the latest React release?") and check the agent's execution log: you should see a tool call out to Exa and web results coming back into the agent's context.
If you want to restrict which Exa tools the agent can use, the node lets you include or exclude tools by name rather than exposing the whole set.
Troubleshooting in n8n
Most failures here are wiring, not syntax. The MCP Client Tool node only works attached to an AI Agent node — dropped elsewhere in the canvas it does nothing. If the tool list comes back empty, the usual causes are a typo in the endpoint URL, a missing or invalid exaApiKey query parameter, or the transport set to SSE when the endpoint expects HTTP Streamable.
On self-hosted n8n, also confirm the container or host can reach mcp.exa.ai — locked-down egress rules are a common silent failure. Unlike desktop clients there's nothing to restart: fix the node settings, save, and re-run the workflow. Errors surface in the execution log on the node itself.
Where this fits
Exa is one of the most-starred search servers in the Loomal Index, and the remote-only packaging makes it one of the easiest to use from n8n — no npx, no PATH problems, no process supervision. If your workflow also needs scraping-heavy extraction or site crawling at depth, browse the rest of the search category for servers that complement it.
FAQ
How do I install Exa in n8n?
You don't install anything. Exa is a hosted remote MCP server, so you add an MCP Client Tool node under your AI Agent node's Tools slot and point it at https://mcp.exa.ai/mcp with your Exa API key in the query string. n8n discovers the tools automatically.
Where is n8n's MCP config file?
There isn't one. Unlike Claude Desktop or Cursor, n8n stores MCP configuration inside the workflow itself, as parameters on the MCP Client Tool node. Each workflow can connect to different servers with different credentials.
Why doesn't Exa appear after I add the node?
Check three things: the node is attached to an AI Agent node (it only functions as an agent tool), the endpoint URL includes a valid exaApiKey parameter, and the transport matches what the endpoint serves. Execution errors show up directly on the node in the workflow run log.
Does my self-hosted n8n need anything special?
Only outbound HTTPS to mcp.exa.ai. Because Exa runs remotely, there's no Node.js, npx, or local package requirement on the n8n host — which removes the PATH issues that stdio servers often hit in containers.
Browse more MCP servers for n8n.
Search, scraping, and data servers your workflows can call today.