How to connect Exa to Claude

Connect Claude Web, Desktop and Cowork to Exa MCP. Summarize recent news articles on ai safety, find similar research papers to this url, and more using natural language, with authentication handled for you.

Exa logoExa
Api Key

Exa is a data extraction and search platform for gathering and analyzing information from websites, APIs, or databases. It helps teams quickly surface insights and automate data-driven workflows.

64 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Exa account to Claude via Composio Connect, enabling it to summarize recent news articles on AI safety, find similar research papers to this URL, create a webset for quarterly sales data, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Exa with

Connecting Exa to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Exa account

Back in Claude, ask it to connect to Exa or give it any Exa-related task.

For example, ask Claude to:

  • "Summarize recent news articles on AI safety"
  • "Find similar research papers to this URL"
  • "Create a webset for quarterly sales data"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Exa account is ready to use.

What is the Exa Claude Connector, and what's possible with it?

The Exa MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Exa account. It provides structured and secure access to Exa’s web search, content extraction, and research tools, so your agent can search the web, generate cited answers, retrieve website content, conduct in-depth research, and organize findings on your behalf.

  • Web search: Have your agent search the web with Exa to find relevant sources for a topic, question, company, or market.
  • Citation-backed answers: Ask the agent to answer specific questions or summarize broad topics using supporting web sources and citations.
  • Website content extraction: Direct your agent to retrieve text, highlights, summaries, and linked subpages from websites or saved documents.
  • Multi-step research: Let the agent start research tasks, check their progress, and return synthesized findings with citations when the work is complete.
  • Research collection management: Instruct your agent to create or delete web collections, import data into them, review imports, add enrichment, and set up monitors.

Troubleshooting

1. Why does Claude not use the Composio connector for Exa?

The connector can show as connected, but Claude must use it in each Exa conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Exa again.

2. Why does Claude show an MCP server error before Exa connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Exa.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Exa.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Exa authorization link not work?

The Composio connector is one server. Your Exa account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Exa connection.
  • Composio creates a fresh Exa authorization link.
  • Open that link in your browser and finish the Exa sign-in.

4. Why do Exa actions fail after they worked before?

The Exa connection can expire or lose permission.

  • Ask Claude to inspect the Exa connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Exa account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Exa.
  • If the action still fails with a permission error, check that the connected account has that permission in Exa itself.

5. How do I switch to a different Exa account?

Claude can manage the Exa connection for you.

  • Ask Claude to disconnect or delete the current Exa account.
  • Ask Claude to connect Exa again.
  • Open the new Composio authorization link for Exa.
  • Sign in with the other Exa account in the browser.
  • After the account connects, ask Claude to retry the Exa task.

6. Why is my Exa connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Exa connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Exa tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Exa.
TOOLS

Supported Tools

Every Exa action and event your agent gets out of the box.

Generate an answer

Generates a direct, citation-backed answer to a clear natural language question or topic using Exa's search, adept at both specific answers and detailed summaries for open-ended queries.

Batch Search Monitors

Delete, pause, or unpause one batch of matching Search API monitors, not Websets monitors.

Cancel Agent Run

Cancel a queued or running Agent run immediately without returning results.

Cancel Webset

Cancel all operations on a Webset, stopping searches and enrichments.

Cancel Webset Enrichment

Cancel a running Webset enrichment and return its updated state.

Cancel Webset Search

Cancel a running search in a Webset and return its updated state.

Create Agent Run

Start an asynchronous Exa Agent run for multi-step web research or enrichment.

Create API Key

Create an API key for the authenticated Exa team.

Create Import

Tool to create a new import to upload data into a Webset.

Create a Monitor

Tool to create a new Monitor.

Create Search Monitor

Create a Search API monitor that delivers new, deduplicated search results to a webhook.

Create Webhook

Create a webhook delivering selected events to your URL.

Create Webset

Tool to create a new Webset with search, import, and enrichment setup.

Create Webset Enrichment

Create an enrichment task for items in an existing Webset.

Create Webset Search

Create a search for an existing Webset and return its initial state.

Delete Agent Run

Delete a stored Exa Agent run by ID and return its deletion receipt.

Delete API Key

Delete an API key belonging to the authenticated team using a Team Management service key.

Delete import

Tool to delete an existing import.

Delete Search Monitor

Permanently delete a Search API monitor and return the deleted monitor.

Delete Webhook

Delete a webhook, making its status inactive and stopping future deliveries to its URL.

Delete webset

Tool to delete a Webset.

Delete Webset Enrichment

Delete a Webset enrichment and return the deleted enrichment.

Delete Webset Item

Delete an item from a Webset and return the deleted item.

Delete Websets Monitor

Delete a Websets monitor and return the deleted monitor.

Get Agent Run

Retrieve an Agent run to inspect its status, output, citations, usage, or cost.

Get API Key

Tool to retrieve details of a specific API key by its ID.

Get API Key Usage

Get an Exa API key's total cost and cost breakdown for a time period.

Get contents from URLs or document IDs

Retrieve text / highlights / summary / subpages from URLs.

Get Event

Tool to get details of a specific event by its ID.

Get Import

Retrieve an import by ID to inspect its status, entity count, and failure details.

Get Search Monitor

Retrieve a Search API monitor's configuration, status, and next scheduled run by ID.

Get Search Monitor Run

Retrieve a Search API monitor run's status and full output when completed.

Get Webhook

Retrieve a webhook's status, events, destination URL, and metadata by ID.

Get Webset

Retrieve a Webset by ID or external ID, including its status and operations.

Get Webset Enrichment

Retrieve an enrichment configured on a Webset, including its status, description, format, and options.

Get Webset Item

Retrieve a Webset item by ID, including its properties, evaluations, and enrichments.

Get Webset Search

Retrieve a Webset search by ID to inspect its status, progress, and recall metrics.

Get Websets Monitor

Retrieve a Websets monitor's status, schedule, search behavior, and last run.

Get Websets Monitor Run

Retrieve a Websets monitor run's status, type, timestamps, and failure reason.

Get Websets Team Info

Get the authenticated Websets team's identity, current concurrency usage, and limits.

List Agent Run Events

List one page of stored Exa Agent run events as JSON.

List Agent Runs

List one page of your team's Exa Agent runs, ordered newest to oldest.

List API Keys

List the authenticated Exa team's API keys, or retrieve one by API key ID.

List events

Tool to list all events that have occurred in the system.

List imports

Tool to list all imports for the Webset.

List Search Monitor Runs

List one page of a Search API monitor's runs, newest first, including status and output.

List Search Monitors

List one page of the authenticated team's Search API monitors, not Websets monitors.

List Webhook Attempts

List one page of a webhook's delivery attempts in descending order.

List webhooks

Tool to list all webhooks for Websets.

List Webset Items

List one page of a Webset's items, optionally filtered by source ID.

List Websets

List one page of Websets, optionally filtered by ID, external ID, or title.

List Websets Monitor Runs

List one page of runs for a Websets monitor, including status and timestamps.

List Websets Monitors

List one page of Websets monitors, optionally filtered by Webset ID.

Preview Webset

Preview how Exa interprets a search before creating a Webset.

Search

Web search via the Exa engine.

Stop Agent Run

Complete a running ultra-effort Agent run early and return results gathered so far.

Trigger Search Monitor

Trigger an immediate Search API monitor run regardless of its schedule.

Update API Key

Update an API key's name, rate limit, or billing-period spending budget.

Update import

Tool to update an import configuration by ID.

Update Search Monitor

Update a Search API monitor's settings, pause or resume it, or remove its schedule with trigger=null.

Update Webhook

Update a webhook's destination URL, subscribed events, or metadata.

Update Webset

Update a Webset's title or metadata, leaving omitted fields unchanged.

Update Webset Enrichment

Update an enrichment's task, format, options, or metadata on a Webset.

Update Websets Monitor

Update a Websets monitor's status, schedule, search behavior, or metadata.

FAQ

Frequently asked questions

With a standalone Exa MCP server, the agents and LLMs can only access a fixed set of Exa tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Exa and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Exa tools.

Yes, absolutely. You can configure which Exa scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Exa data and credentials are handled as safely as possible.

Start with Exa.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Exa tool your agent needs.Free to start.

Start building