Exa
Give the Sazabi agent tools to search the web, research companies, crawl pages, and run deep research using Exa's hosted MCP server.
All Exa integration capabilities
About
This is an MCP connector that gives the Sazabi agent tools from Exa's hosted MCP server (mcp.exa.ai/mcp). Sazabi stores your Exa API key securely and sends it as the x-api-key header to Exa's MCP endpoint. Agents can then run neural and keyword web searches, fetch page contents, crawl URLs, research companies, and kick off deep research tasks.
What the agent can do:
- Run neural and keyword web searches with content retrieval
- Research companies and produce structured summaries
- Crawl and extract contents from specific URLs
- Find similar links to a given page
- Run deep research tasks over the web
Prerequisites
- An Exa account
- An Exa API key from the Exa dashboard
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Exa in Settings > MCP connectors.
Add your key
Create or copy an API key from the Exa dashboard. Paste it into Sazabi. Sazabi stores it securely and sends it as the x-api-key header to Exa's hosted MCP endpoint at https://mcp.exa.ai/mcp.
Set up with the CLI
Exa authenticates with an Exa API key. With the Sazabi CLI installed and authenticated (see sazabi mcp-connectors reference), connect it in one command, passing the credential as a header:
sazabi mcp-connectors connect exa --header x-api-key=<api-key>The CLI connects to the MCP server at once and prints the connection with the tools it discovered; a credential the server rejects is reported, and the connection is left needing attention. Use NAME=@<file> to read a value from a file, or --header-file <file.json> for a JSON object of header names and values. To rotate the stored credentials later, use sazabi mcp-connectors update-credentials <connection-id>; find the connection ID with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to search the web for something and confirm it returns results. If no tools appear, confirm the API key is correct.
Troubleshooting
No tools discovered — Confirm the Exa API key is valid. Check that it was copied correctly from the Exa dashboard.
Connection shows needs attention — The API key may have expired or been revoked; create a new key and reconnect from Settings > MCP connectors.