--- title: "Exa MCP server for AI agents - actionlake" description: "Give Claude 70 Exa actions through one MCP server: monitors, websets, agent runs, API keys. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/exa updated: 2026-10-23 --- 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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 ``` - 70 actions in one signed file - 35 read look, never change - 18 write create and update - 17 wait for a yes destructive, 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_key` Exa 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 call check { 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.0`api.exa.ai` **Built from** Exa's documentation, read 23 October 2026[exa.ai](https://exa.ai/docs/exa-spec.yaml) [exa.ai](https://exa.ai/docs/team-management-spec.yaml) [exa.ai](https://exa.ai/docs/llms.txt) **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. - **35** read look, never change - **18** write create and update - **17** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `exa.webhook_attempts.list` List webhook attempts | List webhook attempts. | read | `automation.webhook_delivery.list` 33 connectors | | `exa.webhooks.list` List webhooks | List webhooks. | read | `automation.webhook.list` 202 connectors | | `exa.api_keys.list` List API keys | List API keys. | read | `identity.api_key.list` 96 connectors | | `exa.webhooks.get` Get a Webhook | Get a Webhook. | read | `automation.webhook.get` 162 connectors | | `exa.api_keys.get` Get API key | Get API key. | read | `identity.api_key.get` 66 connectors | | `exa.webhooks.create` Create a Webhook | Create a Webhook. | write | `automation.webhook.create` 209 connectors | | `exa.api_keys.create` Create API key | Create API key. | write | `identity.api_key.create` 100 connectors | | `exa.webhooks.update` Update a Webhook | Update a Webhook. | write | `automation.webhook.update` 175 connectors | | `exa.webhooks.delete` Delete a Webhook | Delete a Webhook. | destructive | `automation.webhook.delete` 211 connectors | | `exa.webset_items.list` List all Items for a Webset | List all Items for a Webset. | read | this connector | | `exa.search.run` Search | Search. | read | `platform.search_result.search` 18 connectors | | `exa.team.get` Get team info | Get team info. | read | this 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. Read read List the companies in Exa and flag likely duplicates by name or domain. calls `exa.webset_items.list` 2. Write write Create a Webhook in Exa. Show me exactly what you will send before you save it. calls `exa.webhooks.create` Governance for Exa ## Destructive actions wait for a yes. 17 Exa actions are destructive. These are all of them: - Delete a Webhook `exa.webhooks.delete` - Delete API key `exa.api_keys.delete` - Delete a batch `exa.batches.delete` - Batch action on monitors `exa.monitors.batch` - Delete a Webset `exa.websets.delete` - Delete a monitor `exa.monitors.delete` - Delete a run `exa.agent_runs.delete` - Delete an Item `exa.webset_items.delete` - Delete Monitor `exa.webset_monitors.delete` - Delete an Enrichment `exa.webset_enrichments.delete` - Cancel a batch `exa.batches.cancel` - Cancel a running Webset `exa.websets.cancel` - Stop a run `exa.agent_runs.stop` - Cancel a run `exa.agent_runs.cancel` - Cancel a running Search `exa.webset_searches.cancel` - Cancel a running Enrichment `exa.webset_enrichments.cancel` - Delete Import `exa.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. do exa.webhooks.delete confirm_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: "lead@example.com" }, { match: "exa.api_keys.delete", approver: "lead@example.com" }, { match: "exa.batches.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 70 Exa actions - 12 actions page each page of a long list is one call - 30 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Exa action. 70 actions by area: the id your agent calls, what it does, and its effect. **Monitors 7** - `exa.monitors.batch` Batch action on monitors destructive - `exa.monitors.create` Create a monitor write - `exa.monitors.delete` Delete a monitor destructive - `exa.monitors.get` Get a monitor read - `exa.monitors.list` List monitors read - `exa.monitors.trigger` Trigger a monitor write - `exa.monitors.update` Update a monitor write **Websets 7** - `exa.websets.cancel` Cancel a running Webset destructive - `exa.websets.create` Create a Webset write - `exa.websets.delete` Delete a Webset destructive - `exa.websets.get` Get a Webset read - `exa.websets.list` List all Websets read - `exa.websets.preview` Preview a webset read - `exa.websets.update` Update a Webset write **Agent runs 6** - `exa.agent_runs.cancel` Cancel a run destructive - `exa.agent_runs.create` Create a run write - `exa.agent_runs.delete` Delete a run destructive - `exa.agent_runs.get` Get a run read - `exa.agent_runs.list` List runs read - `exa.agent_runs.stop` Stop a run destructive **API keys 6** - `exa.api_keys.create` Create API key write - `exa.api_keys.delete` Delete API key destructive - `exa.api_keys.get` Get API key read - `exa.api_keys.list` List API keys read - `exa.api_keys.update` Update API key write - `exa.api_keys.usage` Get API key usage read **Batches 5** - `exa.batches.cancel` Cancel a batch destructive - `exa.batches.create` Create a batch write - `exa.batches.delete` Delete a batch destructive - `exa.batches.get` Get a batch read - `exa.batches.list` List batches read **Imports 5** - `exa.imports.create` Create an Import write - `exa.imports.delete` Delete Import destructive - `exa.imports.get` Get Import read - `exa.imports.list` List Imports read - `exa.imports.update` Update Import write **Webhooks 5** - `exa.webhooks.create` Create a Webhook write - `exa.webhooks.delete` Delete a Webhook destructive - `exa.webhooks.get` Get a Webhook read - `exa.webhooks.list` List webhooks read - `exa.webhooks.update` Update a Webhook write **Webset enrichments 5** - `exa.webset_enrichments.cancel` Cancel a running Enrichment destructive - `exa.webset_enrichments.create` Create an Enrichment write - `exa.webset_enrichments.delete` Delete an Enrichment destructive - `exa.webset_enrichments.get` Get an Enrichment read - `exa.webset_enrichments.update` Update an Enrichment write **Webset monitors 5** - `exa.webset_monitors.create` Create a Monitor write - `exa.webset_monitors.delete` Delete Monitor destructive - `exa.webset_monitors.get` Get Monitor read - `exa.webset_monitors.list` List Monitors read - `exa.webset_monitors.update` Update Monitor write **Webset items 3** - `exa.webset_items.delete` Delete an Item destructive - `exa.webset_items.get` Get an Item read - `exa.webset_items.list` List all Items for a Webset read **Webset searches 3** - `exa.webset_searches.cancel` Cancel a running Search destructive - `exa.webset_searches.create` Create a Search write - `exa.webset_searches.get` Get a Search read **Events 2** - `exa.events.get` Get an Event read - `exa.events.list` List all Events read **Monitor runs 2** - `exa.monitor_runs.get` Get a run read - `exa.monitor_runs.list` List runs read **Search 2** - `exa.search.find_similar` Find similar links read - `exa.search.run` Search read **Webset monitor runs 2** - `exa.webset_monitor_runs.get` Get Monitor Run read - `exa.webset_monitor_runs.list` List Monitor Runs read **Agent run events 1** - `exa.agent_run_events.list` List run events read **Answer 1** - `exa.answer.run` Answer read **Contents 1** - `exa.contents.get` Contents read **Team 1** - `exa.team.get` Get team info read **Webhook attempts 1** - `exa.webhook_attempts.list` List webhook attempts read 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 - [LaunchDarkly 10](https://actionlake.com/connectors/launchdarkly) - [PlanetScale 9](https://actionlake.com/connectors/planetscale) - [Cloudsmith 7](https://actionlake.com/connectors/cloudsmith) - [Browserbase 6](https://actionlake.com/connectors/browserbase) - [Porkbun 6](https://actionlake.com/connectors/porkbun) - [Optimizely Feature Experimentation 5](https://actionlake.com/connectors/optimizely-feature-experimentation) Joins with, on shared entities - [CIPP 2](https://actionlake.com/connectors/cipp) - [ImmyBot 2](https://actionlake.com/connectors/immybot) - [Sophos Central 2](https://actionlake.com/connectors/sophos-central) - [lemlist 2](https://actionlake.com/connectors/lemlist) - [Crayon CloudIQ 2](https://actionlake.com/connectors/crayon-cloudiq) - [Microsoft 365 Lighthouse and GDAP 2](https://actionlake.com/connectors/microsoft-365-lighthouse-and-gdap) Browse - [All Developer & infrastructure connectors](https://actionlake.com/connectors/category/developer-and-infrastructure) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/exa More: https://actionlake.com/llms.txt