tavily-mcp MCP server in Cline let your coding agent search the web.
Cline plans and executes multi-step coding tasks inside VS Code — but it can only work with what it can see. tavily-mcp (2.1k stars) adds Tavily web search as a tool Cline can call autonomously while it works.
Cline is an agentic coding extension for VS Code, and MCP servers are how you extend what it can do mid-task. With tavily-mcp connected, Cline can look up current library docs, error messages, or release notes through the Tavily search API instead of guessing from stale training data.
Cline manages its MCP servers in its own settings file, separate from VS Code's. Setup is a short JSON entry plus a Tavily API key from tavily.com.
Open Cline's MCP settings
You don't need to hunt for the file manually. In VS Code, open the Cline panel, click the MCP Servers icon, then Configure MCP Servers — Cline opens cline_mcp_settings.json in the editor for you. The file physically lives in VS Code's globalStorage under saoudrizwan.claude-dev/settings/, which is why editing it through the panel beats finding it on disk.
Grab a Tavily API key first (tavily.com — keys start with tvly-). The server is an npm package, so Node.js needs to be installed.
Add the server entry
Paste this into cline_mcp_settings.json. Cline supports two extra fields worth knowing: disabled toggles the server without deleting it, and autoApprove lists tool names Cline may call without asking you each time.
{
"mcpServers": {
"tavily-mcp": {
"command": "npx",
"args": ["-y", "tavily-mcp"],
"env": {
"TAVILY_API_KEY": "tvly-YOUR_API_KEY"
},
"disabled": false,
"autoApprove": []
}
}
}Verify the connection
Save the file and check the MCP Servers view in the Cline panel. Cline starts servers as soon as the settings change — a green status row means tavily-mcp launched and its tools were registered; expand the row to see them. No full VS Code restart is normally needed, though the Restart Server button in that view is the quickest recovery when something looks stuck.
Then give Cline a task that needs the web — "find the current stable version of Vite and check the migration notes" — and watch it call the Tavily tool, asking for approval unless you've added the tool to autoApprove.
Troubleshooting Cline specifics
Red status dot: expand the server row — Cline surfaces the spawn error inline. The usual suspects are a JSON syntax error, npx not on the PATH VS Code inherited (launch VS Code from a terminal to test), or a typo in the package name. It must be exactly tavily-mcp.
Tools run but return auth errors: the TAVILY_API_KEY env value is wrong or hit its quota — that fails per call, not at startup. If you edited the settings file directly on disk rather than through the panel, make sure you edited the one inside globalStorage/saoudrizwan.claude-dev/settings/ and not a stray copy; reloading the VS Code window forces Cline to re-read it.
The listing on Loomal
tavily-mcp's live listing — including its probed tool list — is on the Loomal marketplace at https://loomal.ai/marketplace/tavily-mcp. The server software is open source; Tavily meters API usage under your key. Loomal's broader index exists so agents can discover tools and pay per call in USDC over x402, with prices starting at $0.01 per call.
FAQ
How do I install tavily-mcp in Cline?
Open the Cline panel in VS Code, go to MCP Servers > Configure MCP Servers, and add a tavily-mcp entry with command npx, args ["-y", "tavily-mcp"], and TAVILY_API_KEY in env. Cline picks up the change on save.
Where does Cline store its MCP configuration?
In cline_mcp_settings.json inside VS Code's globalStorage at saoudrizwan.claude-dev/settings/. The reliable way to open it is through the Cline panel's MCP Servers > Configure button rather than browsing the filesystem.
What does autoApprove do?
It's a list of tool names Cline may invoke without prompting you each time. Leave it empty at first so you can see when and how Tavily search gets called, then add specific tools once you trust the pattern.
Why does the server show an error in the MCP view?
Expand the server row — Cline shows the underlying error. Most failures are malformed JSON, npx missing from VS Code's PATH, or a misspelled package name. Use the Restart Server button after fixing.
Find more tools for Cline.
Loomal lists MCP servers with live tool lists, so you know what you're installing.