Log inSubmit server
Tavily MCP logo

Tavily MCP

Adds Tavily web search, page extraction, website mapping, and crawling tools to MCP-compatible clients.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Tavily MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.tavily.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

The tavily-mcp MCP server connects MCP clients to Tavily for real-time web search, page extraction, website mapping, and crawling. It can run locally through Node.js or remotely through Tavily's hosted MCP endpoint. Local use requires a Tavily API key, while remote connections support API-key and OAuth authentication. Reach for it when an agent needs current web information or structured content from websites.

Use cases

  • Search the live web for current information
  • Extract content from specified web pages
  • Map a website into a structured representation
  • Crawl a site for distributed page content
  • Combine web research with a Neo4j MCP workflow

Key features

  • Real-time Tavily web search
  • Web page data extraction
  • Structured website mapping
  • Systematic website crawling
  • Local and hosted MCP operation
  • API-key and OAuth authentication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

14/14 checks healthy over the last 45d

Supply-chain signal

1 high-severity advisory on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 1High 0Medium 0Low 0

Scanned 9/18/2026 via OSV.dev · https://mcp.tavily.com/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2.5kStargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Tavily MCP works

What tavily-mcp does

The tavily-mcp MCP server exposes Tavily web capabilities to MCP-compatible clients. Its tool set covers four related tasks: searching the live web, extracting information from web pages, generating a structured map of a website, and crawling a site systematically.

Search is suited to requests that need current online information rather than only the model's existing knowledge. Extraction focuses on retrieving content from specified pages. Mapping helps represent a site's structure, while crawling can explore pages across a website.

How it works

The server is available in two modes. For local use, an MCP client starts the package with Node.js, commonly through npx -y tavily-mcp@latest. The client passes the Tavily API key through its environment. For remote use, the client connects to https://mcp.tavily.com/mcp/ and supplies the key in the URL or an Authorization header when supported.

Remote connections can also use OAuth. Claude Code can register the hosted endpoint with its MCP command and then complete authentication from the /mcp interface. Other compatible clients can use an OAuth-capable MCP configuration. The remote endpoint accepts a DEFAULT_PARAMETERS header for request defaults such as image inclusion, search depth, and result count.

Setup and configuration

Local operation requires Node.js 20 or newer and a Tavily API key. Git is only needed when using the Git installation method described by the project. A typical local client configuration starts the package with npx and sets TAVILY_API_KEY in the server environment.

DEFAULT_PARAMETERS is optional. Set it to a JSON object when search requests should share default values, for example a preferred search depth or maximum result count. TAVILY_HUMAN_ID is also optional. When provided, the server forwards it as X-Human-Id so Tavily can associate API calls with an end user; Tavily hashes this value before storage.

Tools and capabilities

The tavily-mcp MCP server provides these capabilities:

  • tavily-search for real-time web search.
  • tavily-extract for extracting data from web pages.
  • A website mapping tool for producing a structured site map.
  • A web crawler for systematic website exploration.

It also references using the server with Cline in VS Code. A tutorial describes combining it with a Neo4j MCP server for a knowledge-graph assistant.

Limitations and notes

Tavily authentication and account access are required; the README directs users to obtain an API key from Tavily. Remote OAuth is optional, so API-key authentication remains available through the URL or Authorization header. If OAuth credentials need to be cleared, the documented approach is to remove the local ~/.mcp-auth directory and authenticate again.

The TAVILY_HUMAN_ID setting should use an opaque identifier rather than raw personal information where possible.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Tavily MCP

tavily-mcp is an MCP server that connects MCP clients to Tavily's web search and extraction services. It provides tools for real-time search, extracting page content, mapping websites, and crawling sites systematically. Local use runs through Node.js, while remote use connects to Tavily's hosted MCP endpoint with an API key or OAuth.

Install it for local use by configuring your MCP client to run `npx -y tavily-mcp@latest` and supplying `TAVILY_API_KEY`. Node.js 20 or newer is required. You can also avoid local installation by connecting to Tavily's remote MCP endpoint.

Yes, tavily-mcp works with Cursor. The README provides a Cursor installation flow using the remote MCP endpoint and an `mcp.json` configuration. Add your Tavily API key to the configuration, or configure the supported OAuth flow without placing the key in the URL.

Connect it by running `claude mcp add --transport http tavily https://mcp.tavily.com/mcp` or by including the Tavily API key in the endpoint URL. Without a key in the URL, start Claude Code, open `/mcp`, select the Tavily server, and complete OAuth authentication.

The local setup uses `TAVILY_API_KEY` for authentication. `DEFAULT_PARAMETERS` can provide JSON defaults for search requests, and `TAVILY_HUMAN_ID` can identify an end user for Tavily analytics. The latter two settings are optional.

Related MCP servers

All in Search & Data Extraction All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTavily MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tavily-mcp?style=directory)](https://allmcps.com/mcp/tavily-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tavily-mcp"><img src="https://allmcps.com/api/badge/tavily-mcp?style=directory" alt="Tavily MCP on AllMCPs" /></a>