Advanced web search, extraction and crawling API tuned for LLM agents and RAG pipelines.
unavailable β the package specifier already carries a version
npm
npx -y tavily-mcp@latest
Pick your client β the config below is generated for this server (local stdio). Copy respects the βPin versionβ switch above.
claude_desktop_config.json
{
"mcpServers": {
"tavily": {
"command": "npx",
"args": [
"-y",
"tavily-mcp@latest"
]
}
}
}Format verified against the official Claude Desktop docs β.
terminal
claude mcp add tavily -- npx -y tavily-mcp@latest
Format verified against the official Claude Code docs β.
.cursor/mcp.json
{
"mcpServers": {
"tavily": {
"command": "npx",
"args": [
"-y",
"tavily-mcp@latest"
]
}
}
}Format verified against the official Cursor docs β.
.vscode/mcp.json
{
"servers": {
"tavily": {
"command": "npx",
"args": [
"-y",
"tavily-mcp@latest"
]
}
}
}Format verified against the official VS Code docs β.
mcp_config.json
{
"mcpServers": {
"tavily": {
"command": "npx",
"args": [
"-y",
"tavily-mcp@latest"
]
}
}
}Format verified against the official Windsurf docs β.
Official Β· by tavily-ai
Independent, non-official implementations of the Tavily MCP server maintained by the community.
Last verified: 2026-10-15 ο½ Sources: Verification basis β
β 2,433 stars Β· ζθΏζ΄ζ°δΊ 24 倩ε Β· MIT license
Tavily MCP Server The Tavily MCP server provides: search, extract, map, crawl tools Real-time web search capabilities through the tavily-search tool Intelligent data extraction from web pages via the tavily-extract tool Powerful web mapping tool that creates a structured map of website Web crawler that systematically explores websites π Helpful Resources Tutorial on combining Tavily MCP with Neo4j MCP server Tutorial on integrating Tavily MCP with Cline in VS Code Remote MCP Server Connect directly to Tavily's remote MCP server instead of running it locally. This provides a seamless experience without requiring local installation or configuration. Simply use the remote MCP server URL with your Tavily API key: Get your Tavily API key from tavily.com. Alternatively, you can pass your API key through an Authorization header if the MCP client supports this: Note: When using the remote MCP, you can specify default parameters for all requests by including a DEFAULT PARAMETERS header containing a JSON object with your desired defaults. Example: Connect to Claude Code Claude Code is Anthropic's official CLI tool for Claude. You can add the Tavily MCP server using the claude mcp add command. There are two ways to authenticate: Option 1: API Key in URL Pass your API key directly in the URL. Replace > with your actual Tavily API key: Option 2: OAuth Authentication Flow Add the server without an API key in the URL: After adding, you'll need to complete the authentication flow: Run claude to start Claude Code Type /mcp to open the MCP server management Select the Tavily server and complete the authentication process Tip: Add --scope user to either command to make the Tavily MCP server available globally across all your projects: Once configured, you'll have access to the Tavily search, extract, map, and crawl tools. Connect to Cursor Click the β¬οΈ Add to Cursor β¬οΈ button, this will do most of the work for you but you will still need to edit the configuration to add your API-KEY. You can get a Tavily API key here. once you click the button you should be redirect to Cursor ... Step 1 Click the install button Step 2 You should see the MCP is now installed, if the blue slide is not already turned on, manually turn it on. You also need to edit the configuration to include your own Tavily API key. Step 3 You will then be redirected to your mcp.json file where you have to add your-api-key . Remote MCP Server OAuth Flow The Tavily Remote MCP server supports secure OAuth authentication, allowing you to connect and authorize seamlessly with compatible clients. How to Set Up OAuth Authentication A. Using MCP Inspector: Open the MCP Inspector and click "Open Auth Settings". Select the OAuth flow and complete these steps: Metadata discovery Client registration Preparing authorization Request authorization and obtain the authorization code Token request Authentication complete Once finished, you will receive an access token that lets you securely make authenticated requests to the Tavily Remote MCP server. B. Using other MCP Clients (Example: Cursor): You can configure your MCP client to use OAuth without including your Tavily API key in the URL. For example, in your mcp.json : If you need to clear stored OAuth credentials and reauthenticate, run: > Note: > - OAuth authentication is optional. You can still use API key authentication at any time by including your Tavily API key in the URL query parameter ( ?tavilyApiKey=... ) or by setting it in the Authorization header, as described above. Selecting Which API Key Is Used for OAuth After successful OAuth authentication, you can control which API key is used by naming it mcp auth default : If you set a key named mcp auth default in your personal account , that key will be used for the auth flow. If you are part of a team that has a key named mcp auth default , that key will be used for the auth flow. If you have both a personal key and a team key named mcp auth default , the personal key will be prioritized . If no mcp auth default key is set, the default key in your personal account will be used. If no default key is set, the first available key will be used. Local MCP Prerequisites π§ Before you begin, ensure you have: Tavily API key If you don't have a Tavily API key, you can sign up for a free account here Claude Desktop or Cursor Node.js (v20 or higher) You can verify your Node.js installation by running: node --version Git installed (only needed if using Git installation method) On macOS: brew install git On Linux: Debian/Ubuntu: sudo apt install git RedHat/CentOS: sudo yum install git On Windows: Download Git for Windows Running with NPX Default Parameters Configuration βοΈ You can set default parameter values for the tavily-search tool using the DEFAULT PARAMETERS environment variable. This allows you to configure default search behavior without specifying these parameters in every request. Example Configuration Example usage from Client Identifying the End User (Optional) You can optionally identify the end user on whose behalf requests are being made by setting the TAVILY HUMAN ID environment variable. When set, Tavily MCP forwards it as the X-Human-Id header on every API call, enabling per-user analytics. This is entirely optional β leave it unset and behavior is unchanged. Privacy note: Tavily hashes human id server-side (SHA-256) before storage, so the raw value is never persisted. Even so, prefer opaque identifiers (e.g. an internal user ID) over raw PII like emails when possible. Acknowledgments β¨ Model Context Protocol for the MCP specification Anthropic for Claude Desktopβ¦
Summary from the project README β github.com/tavily-ai/tavily-mcp
Distributed as npm, listed under Search. Review our MCP security guide before granting access to real data.
Tavily MCP Server The Tavily MCP server provides: search, extract, map, crawl tools Real-time web search capabilities through the tavily-search tool Intelligent data extraction from web pages via the tavily-extract tool Powerful web mapping tool that creates a structured map of website Web crawler that systematically explores websites π Helpful Resources Tutorial on combining Tavily MCP with Neo4j MCP server Tutorial on integrating Tavily MCP with Cline in VS Code Remote MCP Server Connect directly to Tavily's remote MCP server instead of running it locally. This provides a seamless experience without requiring local installation or configuration. Simply use the remote MCP server URL with your Tavily API key: Get your Tavily API key from tavily.com. Alternatively, you can pass your API key through an Authorization header if the MCP client supports this: Note: When using the remote MCP, you can specify default parameters for all requests by including a DEFAULT PARAMETERS header containing a JSON object with your desired defaults. Example: Connect to Claude Code Claude Code is Anthropic's official CLI tool for Claude. You can add the Tavily MCP server using the claude mcp add command. There are two ways to authenticate: Option 1: API Key in URL Pass your API key directly in the URL. Replace > with your actual Tavily API key: Option 2: OAuth Authentication Flow Add the server without an API key in the URL: After adding, you'll need to complete the authentication flow: Run claude to start Claude Code Type /mcp to open the MCP server management Select the Tavily server and complete the authentication process Tip: Add --scope user to either command to make the Tavily MCP server available globally across all your projects: Once configured, you'll have access to the Tavily search, extract, map, and crawl tools. Connect to Cursor Click the β¬οΈ Add to Cursor β¬οΈ button, this will do most of the work for you but you will still need to edit the configuration to add your API-KEY. You can get a Tavily API key here. once you click the button you should be redirect to Cursor ... Step 1 Click the install button Step 2 You should see the MCP is now installed, if the blue slide is not already turned on, manually turn it on. You also need to edit the configuration to include your own Tavily API key. Step 3 You will then be redirected to your mcp.json file where you have to add your-api-key . Remote MCP Server OAuth Flow The Tavily Remote MCP server supports secure OAuth authentication, allowing you to connect and authorize seamlessly with compatible clients. How to Set Up OAuth Authentication A. Using MCP Inspector: Open the MCP Inspector and click "Open Auth Settings". Select the OAuth flow and complete these steps: Metadata discovery Client registration Preparing authorization Request authorization and obtain the authorization code Token request Authentication complete Once finished, you will receive an access token that lets you securely make authenticated requests to the Tavily Remote MCP server. B. Using other MCP Clients (Example: Cursor): You can configure your MCP client to use OAuth without including your Tavily API key in the URL. For example, in your mcp.json : If you need to clear stored OAuth credentials and reauthenticate, run: > Note: > - OAuth authentication is optional. You can still use API key authentication at any time by including your Tavily API key in the URL query parameter ( ?tavilyApiKey=... ) or by setting it in the Authorization header, as described above. Selecting Which API Key Is Used for OAuth After successful OAuth authentication, you can control which API key is used by naming it mcp auth default : If you set a key named mcp auth default in your personal account , that key will be used for the auth flow. If you are part of a team that has a key named mcp auth default , that key will be used for the auth flow. If you have both a personal key and a team key named mcp auth default , the personal key will be prioritized . If no mcp auth default key is set, the default key in your personal account will be used. If no default key is set, the first available key will be used. Local MCP Prerequisites π§ Before you begin, ensure you have: Tavily API key If you don't have a Tavily API key, you can sign up for a free account here Claude Desktop or Cursor Node.js (v20 or higher) You can verify your Node.js installation by running: node --version Git installed (only needed if using Git installation method) On macOS: brew install git On Linux: Debian/Ubuntu: sudo apt install git RedHat/CentOS: sudo yum install git On Windows: Download Git for Windows Running with NPX Default Parameters Configuration βοΈ You can set default parameter values for the tavily-search tool using the DEFAULT PARAMETERS environment variable. This allows you to configure default search behavior without specifying these parameters in every request. Example Configuration Example usage from Client Identifying the End User (Optional) You can optionally identify the end user on whose behalf requests are being made by setting the TAVILY HUMAN ID environment variable. When set, Tavily MCP forwards it as the X-Human-Id header on every API call, enabling per-user analytics. This is entirely optional β leave it unset and behavior is unchanged. Privacy note: Tavily hashes human id server-side (SHA-256) before storage, so the raw value is never persisted. Even so, prefer opaque identifiers (e.g. an internal user ID) over raw PII like emails when possible. Acknowledgments β¨ Model Context Protocol for the MCP specification Anthropic for Claude Desktop
Run the install command shown above, then paste the config for your client (Claude Desktop, Claude Code, Cursor, VS Code or Windsurf) into its MCP settings and restart the client.
The MCP server itself is free to install. The source is public on https://github.com/tavily-ai/tavily-mcp. Any third-party service it calls may require its own API key and account.
Any MCP-compatible client can use it, including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and custom agents.
Publish this server? Link back with a badge on your README or site β copy either snippet.
Markdown
[](https://mcpnav.net/server/tavily/)
HTML
<a href="https://mcpnav.net/server/tavily/"><img src="https://mcpnav.net/badge/tavily.svg" alt="Listed on MCPNav" height="20"></a>