Default
Exa MCP connector
The Exa connector brings live web search, page contents, cited answers, deep research tasks, and monitors into Claude, ChatGPT, Cursor, and any MCP client, so your team can research the web from the tool they already use.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
56 tools
How to connect
How to connect Exa to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Exa once
-
Open Connections, choose Add connection, and pick Exa.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Exa API key. One person generates a token in Exa and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Exa to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Exa to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Exa to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Exa to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Exa through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Research a prospect before the first call
Ask for a company's recent news, funding, leadership changes, and what its own site says, then walk in with a briefing instead of a browser full of tabs.
-
Marketing
Watch competitors for new launches and pricing
Set up an Exa monitor on a competitor's product pages and announcements, and check the latest monitor runs for what changed since last week.
-
Research
Run a deep research task on a question
Hand Exa a hard question, let the research task gather sources across the web, and get back a written answer with the pages it drew from.
-
Recruiting
Build a shortlist of candidates and companies
Search for people and organizations that match a role, pull the full text of their public profiles and company pages, and keep the list in one place.
-
Product
Pull the text of documentation and reviews
Fetch the contents of docs, changelogs, and review pages for tools you are evaluating, then ask for a summary of the differences.
-
Leadership
Get a cited answer to a market question
Ask how large a market is or who the main players are, and get an answer with links to the sources behind every claim.
Try asking
- “Summarize the last 20 Exa agent runs for me.”
- “Draft an Exa answer on competitor pricing changes this week.”
- “List Exa contents saved for the launch research brief.”
AI tools
Exa tools for your AI agents
56 tools are ready to call through Elaichi's MCP endpoint the moment you connect Exa, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Exa gets you
6 screens from the product, each doing one job for your Exa account.
The agent
Ask in plain language, answer from Exa.
The agent reads live Exa runs, contents and answers to reply.
- agent runs
- runs
- contents
- answers
Ask Elaichi to work across your apps.
Summarize the last 20 Exa agent runs for me.
Draft an Exa answer on competitor pricing changes this week.
List Exa contents saved for the launch research brief.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Exa here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
56 Exa tools ready without custom code.
Agent runs, runs, contents, contexts and monitors, with every method listed.
- Create a Exa nevermined purchase
- Delete a Exa agent run by ID
- Get single Exa agent run by ID
- Create a Exa agent run
ElaichiToolsToolboxes
Every team gets its own Exa toolbox.
Research, content and engineering each see the Exa tools their work needs.
- Research
- Content
- Engineering
- Competitive intelligence
ElaichiToolboxesShared connections
Teammates use Exa without seeing a key.
Each Exa connection shows who connected it and which teams share it.
- Research
- Content EMEA
- Competitive intel
- Engineering
ElaichiConnectionsAudit log
Every Exa call is written down.
When, who, what happened, type and resource, in an append only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, Exa research ships itself.
Six steps fetch Exa contents, group them, draft a digest, then await approval.
Exa digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch agent runs
Exa
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Exa
Queued
Collections and dashboards
Exa health in numbers, refreshed on schedule.
Four metrics, 14 days of records created and a team breakdown, computed directly.
Exa health
Refreshed 4 minutes ago · every 15 minutes · from the agent runs collection
Agent runs
1,284 ↓ 12%
Runs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agent runs created
Last 14 days
By team
Share of activity
Research 34%
Content EMEA 27%
Competitive intel 21%
Engineering 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Exa to Claude?
First connect Exa in Elaichi by pasting your Exa API key, which you copy from your Exa dashboard. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Exa search, contents, answers, research tasks, and monitors are available in your conversation.
Does Exa work with ChatGPT and Cursor as well as Claude?
Yes. Once Exa is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect Exa once and every client you use picks it up.
What can an AI agent actually do with Exa?
With Exa connected, an AI agent can search the web for pages, people, and companies, fetch the full text of a page, and give a cited answer to a direct question. It can also start a deep research task on a hard question, create monitors that watch for new results on a topic, and read back what those monitors found. Because Exa offers many actions, short concrete asks such as "find the pricing page for Acme" work better than long paragraphs.
Does connecting Exa give the AI my whole Exa account?
The AI can only do what the Exa account behind the connected API key can do, and every call is tied to the Elaichi user who made it. Elaichi can narrow that further, for example allowing search and page contents but not creating monitors or research tasks, and it never widens access beyond what the Exa key already permits.
Can I stop an agent from deleting or changing things in Exa?
Yes. Restrictions in Elaichi work per action, so you can allow Exa search and page contents while blocking the actions that create, update, or delete monitors, runs, and research tasks. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to an Exa connection when someone leaves?
When a person is offboarded in Elaichi, their access to Exa through every connected client ends at once. If they were using a shared Exa connection, it keeps working for everyone else on the team, and if they were the one who connected Exa, an admin can reassign it. Disconnecting Exa once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Exa in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.