Default
Exa MCP connector
The Exa connector brings live web search, page contents, cited answers, deep research tasks, and monitors into Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so your team can research the web from the tool they already use.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize the last 20 Exa agent runs for me.
Working in Exa with Elaichi
-
Get single Exa agent run by ID
-
List all Exa agent runs
-
List all Exa runs
How to connect Exa to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Exa MCP connector for 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.
Exa MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Exa MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Exa MCP connector for 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.
Exa MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Exa through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Exa is logged.
-
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.”
What connecting Exa gets you
6 screens from Elaichi, each doing one job for your Exa account.
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, Cursor or Microsoft Copilot
The agent
Ask in plain language, answer from Exa.
The agent reads live Exa runs, contents and answers to reply.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Exa here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
56 Exa tools ready without custom code.
Agent runs, runs, contents, contexts and monitors, with every method listed.
Toolboxes
Every team gets its own Exa toolbox.
Research, content and engineering each see the Exa tools their work needs.
Shared connections
Teammates use Exa without seeing a key.
Each Exa connection shows who connected it and which teams share it.
Audit log
Every Exa call is written down.
When, who, what happened, type and resource, in an append only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Exa digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Exa
Queued
Automations
A schedule fires, Exa research ships itself.
Six steps fetch Exa contents, group them, draft a digest, then await approval.
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%
Collections and dashboards
Exa health in numbers, refreshed on schedule.
Four metrics, 14 days of records created and a team breakdown, computed directly.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Exa
All three can connect Exa to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Exa tools | Allow or restrict single Exa tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Exa call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting the actions that create, update, or delete monitors, runs, and research tasks. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client at the same time.
Does the Exa MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Exa is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Exa?
Yes. Both let Claude, ChatGPT or Cursor use Exa. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Exa call.
How is Elaichi different from Composio for Exa?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Exa: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Exa in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot