Tavily
AI-optimized web search with cleaned, citation-ready results.
Quick answer
What it does
Provides AI-optimized web search via the Tavily API, including standard search, news search, and combined search-and-extract that returns cleaned page bodies as Markdown.
Best for
- Research-grade web search
- News monitoring
- Citation-ready summaries
- Search + extract in one call
Not for
- Raw SERP introspection
- High-volume free-tier needs
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "tavily": { "command": "npx", "args": [ "-y", "tavily-mcp" ], "env": { "TAVILY_API_KEY": "${TAVILY_API_KEY}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export TAVILY_API_KEY=tvly-your_api_key claude mcp add tavily -- npx -y tavily-mcpRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "tavily": { "command": "npx", "args": [ "-y", "tavily-mcp" ], "env": { "TAVILY_API_KEY": "${TAVILY_API_KEY}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "tavily": { "command": "npx", "args": [ "-y", "tavily-mcp" ], "env": { "TAVILY_API_KEY": "${TAVILY_API_KEY}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "tavily": { "command": "npx", "args": [ "-y", "tavily-mcp" ], "env": { "TAVILY_API_KEY": "${TAVILY_API_KEY}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "tavily": { "command": "npx", "args": [ "-y", "tavily-mcp" ], "env": { "TAVILY_API_KEY": "${TAVILY_API_KEY}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": [ "-y", "tavily-mcp" ], "env": { "TAVILY_API_KEY": "${TAVILY_API_KEY}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.tavily] command = "npx" args = [ "-y", "tavily-mcp", ] env = { TAVILY_API_KEY = "${TAVILY_API_KEY}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "tavily": { "command": { "path": "npx", "args": [ "-y", "tavily-mcp" ] }, "env": { "TAVILY_API_KEY": "${TAVILY_API_KEY}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Apps directorynoneTavily doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.
- 2
Set required secrets
Set
TAVILY_API_KEYin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Citation-ready research summary
Using Tavily, search for the latest reporting on "Model Context Protocol adoption" with topic=news, max_results=8. Then call tavily-extract on the top 3 results and produce a 200-word summary with inline citations.Tested with: Claude Desktop, Cursor.
Tools & permissions
| Tool | Description | Args | Side effects |
|---|---|---|---|
tavily-search | Run a web search and return ranked results with snippets. | query: string, topic?: string, max_results?: number | Network |
tavily-extract | Fetch and clean the body of one or more URLs. | urls: string[] | Network |
tavily-news | Search news sources only, with publication-date metadata. | query: string, days?: number | Network |
Security & scope
- Access scope
- Network
- Sandbox
- Calls the Tavily API over HTTPS with the key in TAVILY_API_KEY. The MCP itself only reads from Tavily — no write capability, no local filesystem reach. Rate limits and per-call cost are the main operational concerns.
- Gotchas
- Per-call cost rises with `include_raw_content: true` — set a budget at the API-key level before unleashing an autonomous loop.
- Tavily caches some searches; if you need real-time freshness for time-sensitive prompts, pass `include_raw_content: true` or pair with Brave Search for news-burst coverage.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. web search work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-web-search
Compare Tavily MCP vs [Brave Search MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/tavily - top-mcps.com listing for Brave Search
Install the Tavily MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/tavily (fetch https://top-mcps.com/mcp/tavily.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (TAVILY_API_KEY) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Web Search MCPs
Other tools in the same category worth evaluating.
Search for homes conversationally with live listing data — verified for 2026.
Compared with Tavily
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Web Search? See all Web Search MCPs →