Resources · Claude connector

Claude Exa connectorWhat Claude can do in your Exa account.

The Claude Exa connector exposes 2 tools. 1 searches the live web for Claude, 0 change anything in an account, 1 is undocumented. Here: what the search gives you, what stays unknown, and why Exa's docs list other tools than the sheet.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can search with Exa

Claude answers from what it already knows. With Exa plugged in, it can look things up on the web while it answers, read the pages that matter and build its reply on current sources. You ask in plain language; you get content, not a bare list of links. Useful when the answer depends on something published last week.

A fresh answer on a moving topic. You ask for the breaking changes in the latest release of a library your team uses, and web_search_exa brings back relevant, ready-to-use content from the web that Claude sums up for you.

A quick competitive scan. You want the public pricing pages of three rival tools compared side by side. Claude runs the searches itself and writes the comparison from what it found, with its sources.

Research inside a longer task. Exa says the connector works in Cowork too: during a longer task, Claude can search, read the pages that matter and keep using those sources as it goes.

Now the limits. The second tool, get_code_context_exa, is described by no official source, so this page says nothing about what it does. Nothing on the sheet changes an account. Without signing in, Exa serves you through keyless access, which is rate-limited. And nothing runs on its own: no search fires on a schedule or on an event. For recurring monitoring you want an automation tool, a different job; the Exa Make integration covers that side, and the Integrations hub lists the others.

Vocabulary

The vocabulary in one minute

Five words you will run into while plugging Exa in.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory lists them by name.
Authorization
The sign-in screen of Exa itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
Approval
The confirmation Claude waits for before it goes ahead with something that changes your account, shown right in the chat.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Exa.
Connect

Plug Exa into Claude in three steps

  1. 01

    Find Exa in Claude

    In Claude's settings, open Customize, then Connectors, and look for Exa in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can connect.

  2. 02

    Start the connection

    Click Connect on the Exa row, then sign in to Exa in the window the service opens itself. If the link ever breaks, use Disconnect and plug it back in.

  3. 03

    Read the authorization screen

    Read the authorization screen before you approve it. It belongs to Exa, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Exa account.

Tools

The 2 tools of the Claude Exa connector

Exa gives Claude 2 tools: 1 that read your account, 0 that change something in it, and 1 no official source describes.

Two groups: what Claude looks up, and what no official source describes. The names stay the ones Claude shows, in English.

  • 1 read
  • 1 not documented

What Claude looks up (1)

1 tool

One search tool that reads the public web and changes nothing in your account.

web_search_exa

Runs a web search from your question and returns relevant content that is ready to use, which Claude then reads and cites in its answer. Exa enables it by default.

When it helps
a product manager needs the current state of a regulation before a Monday meeting and wants the sources, not a summary from memory.
Watch out
without an Exa sign-in, it runs on keyless access and can hit a rate limit.

Sourcedocs.exa.ai · September 30, 2026 ↗

Undocumented (1)

1 tool

The directory publishes this name and nothing else. No official text says what it does, and this page will not guess from a name.

get_code_context_exa

This name appears on the directory sheet, and that is all anyone publishes about it. Exa's own documentation does not mention it, and no Claude page does either, so this page stops there.

Watch out
whatever it does, the general approval rule below covers it.
Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.

On a Team or Enterprise workspace, the owners decide whether a member can let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keep reading open and close writing. That setting applies to everyone, and nobody gets around it from their own account. Claude also works with the access you grant to Exa and nothing more.

Plans

Which plans include it

Out of the 819 sheets in the official directory, not one shows availability by plan. The connector by connector answer is published nowhere: that is a real gap in the catalogue.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, check the Exa sheet in the official directory from your own account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a page changes, news breaks or a schedule comes around.

This connector is documented only by its publisher: no Claude help page covers it. The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in what comes from a publisher you trust, here Exa itself.

Two official sources disagree

Which Exa tools does the connector give Claude?

What this page followsThe two lists share only web_search_exa. Neither is marked stale. For Claude, the list that counts is the one on the directory sheet of your own account, so check it there rather than trusting Exa's page or this one.

Need help

Need help connecting Exa to Claude?

A person reads every message.

FAQ

Questions about the Claude Exa connector

01What can Claude do with the Exa connector?
Claude can search the live web through Exa while it answers you. The documented tool, web_search_exa, runs a search and returns relevant, ready-to-use content that Claude reads and uses as a source, which helps on anything that changed recently. The directory sheet lists a second tool, get_code_context_exa, but no official source describes it, so what it does stays unknown. Exa also describes Claude reading the pages that matter and using those sources while it works.
02Can Claude write, send or delete anything with Exa?
Not with the tools the sheet shows today. The directory lists two tools, and the only documented one searches the web without changing any account. The second one is undocumented, so nobody can say for sure what it does. Treat that as a floor observed today rather than a guarantee: a connector's tool list can change, and an admin can open actions that no public sheet shows. Check the sheet again from your own account before relying on it.
03Does Claude ask before running an Exa search?
By default, Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to web_search_exa or to get_code_context_exa, so that default rule is what covers them. On a Team or Enterprise workspace, owners decide whether members can let some actions through without a prompt, and they can restrict what the connector may do for the whole organization. A member cannot undo that restriction from their own account, even for a simple search.
04Which Claude plans include the Exa connector?
No official source publishes availability plan by plan for a given connector, and none of the directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner switching the connector on first on Team and Enterprise. Exa's own rate limits are a separate matter tied to your Exa team. The directory sheet is where to check your own account.
05Does Claude see my whole Exa account?
Claude works with the access you grant and nothing more. Exa offers two ways in: without signing in, through keyless access that is rate-limited, or signed in through OAuth, where usage belongs to your Exa team. The documented tool searches the public web; no source describes Claude reading your Exa account settings. On Team and Enterprise, an owner can also restrict what the connector may do for the whole organization, and a member cannot lift that from their own account.
06Why does Claude hit a rate limit with Exa?
Because the connection is running on Exa's keyless limits. Exa says a connection without sign-in or API key gets rate-limited access, and a 429 error means that ceiling was reached. The fix Exa gives is to sign in with OAuth or add your own API key, then reconnect so requests use your team's plan and limits. Until then, searches can fail in the middle of a conversation, and Claude has to answer without the web.
07Claude or an automation tool for Exa: which one fits?
They do different jobs, so choose by use rather than by ranking. The connector fits when you want an answer backed by fresh web sources during a conversation, with you reading the result. An automation tool fits when a search should run every morning or each time a record changes, and feed its results somewhere without anyone asking. Nothing in the connector starts on its own, so recurring monitoring belongs to automation.