Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
MCP server for advanced web search using Tavily
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"tavily": {
"command": "npx",
"args": [
"-y",
"tavily-mcp"
],
"env": {
"TAVILY_API_KEY": "your-value",
"DEFAULT_PARAMETERS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add tavily --env TAVILY_API_KEY=your-value --env DEFAULT_PARAMETERS=your-value -- npx -y tavily-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tavily": {
"command": "npx",
"args": [
"-y",
"tavily-mcp"
],
"env": {
"TAVILY_API_KEY": "your-value",
"DEFAULT_PARAMETERS": "your-value"
}
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"tavily": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tavily-mcp"
],
"env": {
"TAVILY_API_KEY": "your-value",
"DEFAULT_PARAMETERS": "your-value"
}
}
}
}DEFAULT_PARAMETERS envValues marked secret are keys to your account. Never share them or paste them into a chat.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026
The registry name was verified with the GitHub account tavily-ai, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Needs the server’s tool list first; this check starts in the next step
Compared only with servers in this prototype, not the whole registry.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TAVILY_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.2.15) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The Tavily MCP server provides:
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:
https://mcp.tavily.com/mcp/?tavilyApiKey=<your-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:
Authorization: Bearer <your-api-key>
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:
{"include_images":true, "search_depth": "basic", "max_results": 10}
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:
Pass your API key directly in the URL. Replace with your actual Tavily API key:
claude mcp add --transport http tavily https://mcp.tavily.com/mcp/?tavilyApiKey=<your-api-key>
Add the server without an API key in the URL:
claude mcp add --transport http tavily https://mcp.tavily.com/mcp
After adding, you'll need to complete the authentication flow:
claude to start Claude Code/mcp to open the MCP server managementTip: Add --scope user to either command to make the Tavily MCP server available globally across all your projects:
claude mcp add --transport http --scope user tavily https://mcp.tavily.com/mcp/?tavilyApiKey=<your-api-key>
Once configured, you'll have access to the Tavily search, extract, map, and crawl tools.
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 ...
Click the install button
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.
You will then be redirected to your mcp.json file where you have to add your-api-key.
{
"mcpServers": { "tavily-remote-mcp": { "command": "npx -y mcp-remote https://mcp.tavily.com/mcp/?tavilyApiKey= ", "env": {} } } }
The Tavily Remote MCP server supports secure OAuth authentication, allowing you to connect and authorize seamlessly with compatible clients.
A. Using MCP Inspector:
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:
{
"mcpServers": { "tavily-remote-mcp": { "command": "npx mcp-remote https://mcp.tavily.com/mcp", "env": {} } } }
If you need to clear stored OAuth credentials and reauthenticate, run:
rm -rf ~/.mcp-auth
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 theAuthorizationheader, as described above.
After successful OAuth authentication, you can control which API key is used by naming it mcp_auth_default:
mcp_auth_default in your personal account, that key will be used for the auth flow.mcp_auth_default, that key will be used for the auth flow.mcp_auth_default, the personal key will be prioritized.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.Before you begin, ensure you have:
node --versionbrew install gitsudo apt install gitsudo yum install gitnpx -y tavily-mcp@latest
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.
export DEFAULT_PARAMETERS='{"include_images": true}'
{
"mcpServers": { "tavily-mcp": { "command": "npx", "args": ["-y", "tavily-mcp@latest"], "env": { "TAVILY_API_KEY": "your-api-key-here", "DEFAULT_PARAMETERS": "{\"include_images\": true, \"max_results\": 15, \"search_depth\": \"advanced\"}" } } } }
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.
{
"mcpServers": { "tavily-mcp": { "command": "npx", "args": ["-y", "tavily-mcp@latest"], "env": { "TAVILY_API_KEY": "your-api-key-here", "TAVILY_HUMAN_ID": "your-user-id" } } } }
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.