Skip to content
actionlake
Start free

Connectors · Developer & infrastructure

Exa MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Exa and the rest of your systems. It gives your agent 70 Exa actions (35 reads, 18 writes and 17 that wait for a confirmation) and holds the Exa credential itself, so the agent never does. It paces Exa's limits and records every call.

Connect Exa freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "exa.webhooks.list",  intent: "check which Exa account is connected"}# List webhooks · read · 1 upstream call
  • 70actionsin one signed file
  • 35readlook, never change
  • 18writecreate and update
  • 17wait for a yesdestructive, confirmed first

Set up

Connect Exa in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Exa.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyExa API key, from dashboard.exa.ai/api-keys
    account { op: "connections.requirements", service: "exa" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "exa.webhooks.list" }# list webhooks · read · 1 upstream callcheck { action: "exa.webhooks.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Exa at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
10 calls a second, per connection
API covered
Exa Public API 2.0.0 + Team Management API 1.0.0api.exa.ai
Built from
Exa's documentation, read 23 October 2026exa.aiexa.aiexa.ai
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
30 of 35 reads, for up to 5 minutes; a write clears what it affects
Shared entities
2, so ask can line Exa up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Exa.

70 actions in 20 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 35readlook, never change
  • 18writecreate and update
  • 17destructivewait for a confirmation

  1. Monitors

    7

    2 read · 3 write · 2 destructive

    List monitors · Get a monitor · Create a monitor · Trigger a monitor

  2. Websets

    7

    3 read · 2 write · 2 destructive

    List all Websets · Preview a webset · Get a Webset · Create a Webset

  3. Agent runs

    6

    2 read · 1 write · 3 destructive

    List runs · Get a run · Create a run · Delete a run

  4. API keys

    6

    3 read · 2 write · 1 destructive

    List API keys · Get API key · Create API key · Delete API key

  5. Batches

    5

    2 read · 1 write · 2 destructive

    List batches · Get a batch · Create a batch · Delete a batch

  6. Imports

    5

    2 read · 2 write · 1 destructive

    List Imports · Get Import · Create an Import · Update Import

  7. Webhooks

    5

    2 read · 2 write · 1 destructive

    List webhooks · Get a Webhook · Create a Webhook · Update a Webhook

  8. Webset enrichments

    5

    1 read · 2 write · 2 destructive

    Get an Enrichment · Create an Enrichment · Update an Enrichment · Delete an Enrichment

12 more areas · 24 actions
  • Webset monitors 5
  • Webset items 3
  • Webset searches 3
  • Events 2
  • Monitor runs 2
  • Search 2
  • Webset monitor runs 2
  • Agent run events 1
  • Answer 1
  • Contents 1
  • Team 1
  • Webhook attempts 1

Top actions

The Exa API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 16 of Exa's 16 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
exa.webhook_attempts.listList webhook attemptsList webhook attempts.readautomation.webhook_delivery.list33 connectors
exa.webhooks.listList webhooksList webhooks.readautomation.webhook.list202 connectors
exa.api_keys.listList API keysList API keys.readidentity.api_key.list96 connectors
exa.webhooks.getGet a WebhookGet a Webhook.readautomation.webhook.get162 connectors
exa.api_keys.getGet API keyGet API key.readidentity.api_key.get66 connectors
exa.webhooks.createCreate a WebhookCreate a Webhook.writeautomation.webhook.create209 connectors
exa.api_keys.createCreate API keyCreate API key.writeidentity.api_key.create100 connectors
exa.webhooks.updateUpdate a WebhookUpdate a Webhook.writeautomation.webhook.update175 connectors
exa.webhooks.deleteDelete a WebhookDelete a Webhook.destructiveautomation.webhook.delete211 connectors
exa.webset_items.listList all Items for a WebsetList all Items for a Webset.readthis connector
exa.search.runSearchSearch.readplatform.search_result.search18 connectors
exa.team.getGet team infoGet team info.readthis connector

Try it

Prompts to paste into Claude.

Each one names the Exa actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    List the companies in Exa and flag likely duplicates by name or domain.

    callsexa.webset_items.list

  2. Writewrite

    Create a Webhook in Exa. Show me exactly what you will send before you save it.

    callsexa.webhooks.create

Governance for Exa

Destructive actions wait for a yes.

17 Exa actions are destructive. These are all of them:

  • Delete a Webhookexa.webhooks.delete
  • Delete API keyexa.api_keys.delete
  • Delete a batchexa.batches.delete
  • Batch action on monitorsexa.monitors.batch
  • Delete a Websetexa.websets.delete
  • Delete a monitorexa.monitors.delete
  • Delete a runexa.agent_runs.delete
  • Delete an Itemexa.webset_items.delete
  • Delete Monitorexa.webset_monitors.delete
  • Delete an Enrichmentexa.webset_enrichments.delete
  • Cancel a batchexa.batches.cancel
  • Cancel a running Websetexa.websets.cancel
  • Stop a runexa.agent_runs.stop
  • Cancel a runexa.agent_runs.cancel
  • Cancel a running Searchexa.webset_searches.cancel
  • Cancel a running Enrichmentexa.webset_enrichments.cancel
  • Delete Importexa.imports.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doexa.webhooks.deleteconfirm_policy: human

Delete a Webhook?

intent: the user asked me to delete a Webhook

run suspended · waiting for a named person · key exa-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "exa-agent",  allowed_actions: ["exa.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "exa.webhooks.delete", approver: "[email protected]" },    { match: "exa.api_keys.delete", approver: "[email protected]" },    { match: "exa.batches.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Exa only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Exa costs on actionlake.

Every Exa action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Exa refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 70 Exa actions
  • 12actions pageeach page of a long list is one call
  • 30reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Exa action.

70 actions by area: the id your agent calls, what it does, and its effect.

Monitors7
  • exa.monitors.batchBatch action on monitorsdestructive
  • exa.monitors.createCreate a monitorwrite
  • exa.monitors.deleteDelete a monitordestructive
  • exa.monitors.getGet a monitorread
  • exa.monitors.listList monitorsread
  • exa.monitors.triggerTrigger a monitorwrite
  • exa.monitors.updateUpdate a monitorwrite
Websets7
  • exa.websets.cancelCancel a running Websetdestructive
  • exa.websets.createCreate a Websetwrite
  • exa.websets.deleteDelete a Websetdestructive
  • exa.websets.getGet a Websetread
  • exa.websets.listList all Websetsread
  • exa.websets.previewPreview a websetread
  • exa.websets.updateUpdate a Websetwrite
Agent runs6
  • exa.agent_runs.cancelCancel a rundestructive
  • exa.agent_runs.createCreate a runwrite
  • exa.agent_runs.deleteDelete a rundestructive
  • exa.agent_runs.getGet a runread
  • exa.agent_runs.listList runsread
  • exa.agent_runs.stopStop a rundestructive
API keys6
  • exa.api_keys.createCreate API keywrite
  • exa.api_keys.deleteDelete API keydestructive
  • exa.api_keys.getGet API keyread
  • exa.api_keys.listList API keysread
  • exa.api_keys.updateUpdate API keywrite
  • exa.api_keys.usageGet API key usageread
Batches5
  • exa.batches.cancelCancel a batchdestructive
  • exa.batches.createCreate a batchwrite
  • exa.batches.deleteDelete a batchdestructive
  • exa.batches.getGet a batchread
  • exa.batches.listList batchesread
Imports5
  • exa.imports.createCreate an Importwrite
  • exa.imports.deleteDelete Importdestructive
  • exa.imports.getGet Importread
  • exa.imports.listList Importsread
  • exa.imports.updateUpdate Importwrite
Webhooks5
  • exa.webhooks.createCreate a Webhookwrite
  • exa.webhooks.deleteDelete a Webhookdestructive
  • exa.webhooks.getGet a Webhookread
  • exa.webhooks.listList webhooksread
  • exa.webhooks.updateUpdate a Webhookwrite
Webset enrichments5
  • exa.webset_enrichments.cancelCancel a running Enrichmentdestructive
  • exa.webset_enrichments.createCreate an Enrichmentwrite
  • exa.webset_enrichments.deleteDelete an Enrichmentdestructive
  • exa.webset_enrichments.getGet an Enrichmentread
  • exa.webset_enrichments.updateUpdate an Enrichmentwrite
Webset monitors5
  • exa.webset_monitors.createCreate a Monitorwrite
  • exa.webset_monitors.deleteDelete Monitordestructive
  • exa.webset_monitors.getGet Monitorread
  • exa.webset_monitors.listList Monitorsread
  • exa.webset_monitors.updateUpdate Monitorwrite
Webset items3
  • exa.webset_items.deleteDelete an Itemdestructive
  • exa.webset_items.getGet an Itemread
  • exa.webset_items.listList all Items for a Websetread
Webset searches3
  • exa.webset_searches.cancelCancel a running Searchdestructive
  • exa.webset_searches.createCreate a Searchwrite
  • exa.webset_searches.getGet a Searchread
Events2
  • exa.events.getGet an Eventread
  • exa.events.listList all Eventsread
Monitor runs2
  • exa.monitor_runs.getGet a runread
  • exa.monitor_runs.listList runsread
Search2
  • exa.search.find_similarFind similar linksread
  • exa.search.runSearchread
Webset monitor runs2
  • exa.webset_monitor_runs.getGet Monitor Runread
  • exa.webset_monitor_runs.listList Monitor Runsread
Agent run events1
  • exa.agent_run_events.listList run eventsread
Answer1
  • exa.answer.runAnswerread
Contents1
  • exa.contents.getContentsread
Team1
  • exa.team.getGet team inforead
Webhook attempts1
  • exa.webhook_attempts.listList webhook attemptsread

Questions

The Exa MCP server, answered.

Is there an Exa MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 70 Exa actions across monitors, websets, agent runs and API keys, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Exa.

What do I need to connect Exa?

Exa API key, from dashboard.exa.ai/api-keys. The free call account { op: "connections.requirements", service: "exa" } lists exactly what to paste.

Can an AI agent delete or change things in Exa?

Only if its key allows it, and only with an explicit confirmation. 17 Exa actions are destructive, including delete a Webhook, delete API key and delete a batch. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Exa API limit?

actionlake paces every call to the limits in the Exa service file: 10 calls a second per connection. Repeated reads are answered from cache (30 Exa actions can be), which never reaches Exa.

What does an Exa action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (12 Exa actions page). Cache hits, searches, dry runs and calls Exa refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Exa API does it cover?

The Exa Public API 2.0.0 + Team Management API 1.0.0 at api.exa.ai. It is built from Exa's documentation as read on 23 October 2026. 70 actions in 20 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Exa data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Exa credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Exa

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Exa; the name is the vendor's own. Counts are from the Exa service file, version 1.0.0.

Give your agent Exa today.

Connect Exa freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.