Claude Tavily connectorWhat Claude can do with your Tavily account.
The Claude Tavily connector exposes 5 tools. 4 read the public web through Tavily, 0 change anything in an account, 1 is not described by any source. Below: what each one fetches, what it will not do, and what happens before you connect.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude answers from the live web
Claude answers from what it already knows, and that knowledge has a date. With Tavily plugged in, it can go and look: run a fresh search, open the pages that matter and bring back their content, then answer from there. Tavily pitches this as grounding answers in live data. You still ask in plain words; the difference is where the facts come from.
A current answer, not a remembered one. Ask what changed in a regulation this week and tavily_search runs a real-time search. Claude then answers from what it found.
The article itself, not the headline. Paste three links from a newsletter and tavily_extract pulls the main content out of each page, so Claude can compare them without you copying text around.
A whole site at a glance. Preparing a call with a prospect, you want the shape of their website: tavily_map builds a structured map of its pages, and tavily_crawl walks through them systematically when you need the content too.
What it will not do: nothing here touches an account of yours. The documented tools read public web pages and change nothing, and the fifth one, tavily_research, is not described anywhere. Nothing runs by itself either: no tool watches a page and alerts you when it changes. For recurring monitoring, a scenario tool is the right fit, and the Tavily Make integration page covers that side. They do different jobs.
The vocabulary in one minute
Five words you will meet while plugging Tavily into Claude.
- 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 action the connector opens to Claude. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- The sign-in screen of Tavily itself, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Tavily.
Connect Tavily to Claude in three steps
- 01
Find Tavily in Claude
In Claude's settings, open Customize, then Connectors, and look for Tavily in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row and sign in to Tavily in the window the service opens itself. If the link breaks one day, use Disconnect, then plug it back in from the same row.
- 03
Read the authorization screen
Read the service's screen before you accept. It belongs to Tavily, not Claude, and it decides what the access covers. You can also withdraw that access later from your Tavily account.
The 5 tools, grouped by what they do
Tavily gives Claude 5 tools: 4 that read your account, 0 that change something in it, and 1 no official source describes.
Four tools that read the web, one that no source describes. Names stay in English, as Claude shows them.
- 4 read
- 1 not documented
What Claude reads (4)
4 toolsFour tools that fetch public web content. None of them changes anything in an account.
tavily_search
Runs a real-time search on the web and returns results Claude can read and cite back to you.
tavily_extract
Pulls the relevant content out of a web page you point it at, rather than handing Claude the whole page. Claude then works on the text itself.
tavily_crawl
Explores a website methodically, page after page, so Claude can gather content from far more than a single URL.
tavily_map
Draws a structured map of a website: which sections and pages exist and how they hang together. You see the layout before anyone reads the pages.
Not documented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and this page will not guess from a name.
tavily_research
The directory lists this name and nothing else. Neither Tavily's documentation nor its public code page describes it, and no Claude page does either, so this page says no more about it.
What Claude asks before acting
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 Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked every time. They can also cap what a connector may do for the whole organisation, keeping reading open and closing writing, for example. That setting applies to everyone and nobody gets around it from their own account. And Claude works with your rights, nothing more: what you cannot reach in Tavily stays out of its reach too.
Which plans it works on
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a page changes, a new article appears or a competitor updates its prices.
The tool list is an observed floor, not a promise: by default Tavily's sheet exposes reading only, and an administrator could open more that no public sheet shows. The partner badge in the directory 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 described. Everything below comes from Tavily's own documentation, since neither Claude's help centre nor Anthropic's docs have a page on this connector. For a connector that works inside your own data instead, see the Claude airtable connector.
Need help connecting Tavily to Claude?
A person reads every message.
