Command · Analytics & Data
Exa
Bridge an Exa API key into an MCP server so agents can run web searches through Exa.
How it works
Exa is a web search API. This connector bridges your Exa API key into an MCP server so agents can search the web through Exa. It differs from Exa's own hosted MCP server.
Before you start
- An Exa account
- An Exa API key
- Access to raia Command
What you need to make the connection
| Field | Where to get it |
|---|---|
| LabelOptional | Any name that helps you recognize the account in Command. |
| Exa API key | Created in the Exa dashboard, linked from Exa's documentation. |
Recommended practice: keep credentials private. If one is exposed, revoke or rotate it with the provider before reconnecting.
Setup steps
- 01
In raia Command, click Connectors in the left sidebar and open Exa.
- 02
On the Setup tab, click Add account if the blank form is not already open.
- 03
Enter a Label (optional) and paste your Exa API key, then click Save & verify.
Enter an optional Label and the Exa API key, then click Save & verify. Check the connection status after saving. - Highlight 1: Label (optional)
- Highlight 2: Exa API key
- Highlight 3: Save & verify
- 04
Check that the account shows as connected. Exa is MCP-only: there is no import flow — agents search through the MCP tools.
- 05
If verification fails, confirm the key in the Exa dashboard and try again.
Good to know
- Exa's plans and pricing change; check Exa's current terms rather than relying on this guide.