Prerequisites
- An Exa account with an API key
- project_contributor access in AgentRuntime
Connect in AgentRuntime
Get an Exa API key
Sign up at exa.ai and copy your API key from the dashboard.
Create a connection
Go to Connections and click New custom connection to create an API key connection with
APIKey.Add exa MCP instance
Go to MCP, click Add instance for exa, wire your connection on Instance config, set the profile active, and save.
What you can build
- Research briefs —
exa_searchwithinclude_text=true→ LLM synthesizes findings → save to Notion or Google Docs. - Competitive intel —
exa_find_similaron a competitor landing page → rank overlapping products. - Q&A with citations —
exa_answerfor user questions in Chat Autopilot → display answer plus source URLs. - Deep research mode —
exa_searchwithtype=deepfor multi-hop investigation before human review.
Tools
| Tool | Description |
|---|---|
exa_search | Web search with modes auto, fast, or deep; optional full page text |
exa_find_similar | Find pages semantically similar to a given URL |
exa_answer | AI-generated answer with cited web sources |
Example
Search the web and pass results to an LLM step:Configuration
| Key | Required | Description |
|---|---|---|
APIKey | Yes | Exa API key |
APIBase | No | Exa API base URL |
Troubleshooting
| Issue | Fix |
|---|---|
| Empty results | Broaden query; try type=deep for niche topics |
| Rate limits | Reduce num_results or add backoff between workflow runs |
Stale citations in exa_answer | Re-run search; Exa synthesizes from live index at query time |
| High latency on deep search | Increase step timeout_s; deep mode takes longer than fast |
Related
- Integrations quickstart
- Brave connector — alternative web search
- Connector catalog
- Troubleshooting