tavily-mcp MCP server in Continue.dev web search in your open-source assistant.

Continue.dev configures MCP servers in YAML, not JSON — either globally or per project. Here's the exact block that connects tavily-mcp (2.1k stars) so your agent can search the live web.

Continue.dev is an open-source coding assistant for VS Code and JetBrains, and it loads MCP servers from YAML configuration — a different format than most MCP clients, which use JSON. tavily-mcp is an npm-packaged server that exposes Tavily's web search API as tools, so Continue's agent mode can fetch current information while it codes.

You have two placement options: your global ~/.continue/config.yaml for every project, or a YAML file under .continue/mcpServers/ inside one repo. Both work the same way; the project file is the one you'd commit for your team.

Get the prerequisites

Create a Tavily account at tavily.com and copy your API key (tvly-...). Node.js must be installed because Continue launches the server with npx. That's it — there's nothing to install ahead of time; npx fetches the tavily-mcp package on first run.

Note that MCP tools in Continue are used in agent mode, where the model can take actions — plain chat mode won't call them.

Add the YAML block

Open ~/.continue/config.yaml (global) or create .continue/mcpServers/tavily.yaml in your project. The same keys apply in either location — mind the indentation, since YAML errors are the Continue equivalent of a JSON trailing comma:

~/.continue/config.yaml

mcpServers:
  - name: tavily-mcp
    command: npx
    args:
      - "-y"
      - tavily-mcp
    env:
      TAVILY_API_KEY: tvly-YOUR_API_KEY

Reload and test

Continue doesn't always pick up config edits instantly. Reload the extension — in VS Code, run "Developer: Reload Window" from the Command Palette, or use the reload control in Continue's own settings UI. Then switch to agent mode and ask something that requires live data, like "search for the latest changes to the MCP specification." The Tavily tools should appear in the assistant's available-tools list and get invoked.

If you used a project-scoped file, confirm you actually have that project open; .continue/mcpServers/*.yaml only loads for its own workspace.

When it doesn't load

YAML syntax is the top offender: a tab character instead of spaces, or a missing dash on the list item, makes Continue skip the whole block silently. Run the file through a YAML linter if tools don't appear.

Next, check that npx works in the environment Continue inherits — open the integrated terminal and run npx -y tavily-mcp manually; if it starts and waits for input, the server side is fine and the problem is the config. API key errors surface only when a tool is called, so a server that connects but fails on search almost always means the TAVILY_API_KEY value is wrong or out of quota. After any fix, reload the window again — stale config is a recurring Continue gotcha.

Where this server lives in the index

You can inspect tavily-mcp's listing and live tool list on Loomal at https://loomal.ai/marketplace/tavily-mcp. The server code is open source under github.com/tavily-ai/tavily-mcp; the Tavily API behind it is metered under your key. Loomal indexes search servers like this one alongside paid, x402-ready alternatives that agents can call and pay per request.

FAQ

How do I add tavily-mcp to Continue.dev?

Add an mcpServers list item to ~/.continue/config.yaml (or a file in .continue/mcpServers/) with command npx, args -y and tavily-mcp, and TAVILY_API_KEY under env. Reload the Continue extension so it re-reads the config.

Global config.yaml or project .continue/mcpServers/ — which should I use?

Global gives every project the tool with one edit; the project folder scopes it to one repo and can be committed so teammates get the same setup. Behavior is identical — only scope differs. Keep real API keys out of committed files.

Why aren't the Tavily tools showing up in Continue?

Three common causes: YAML indentation errors (Continue skips invalid blocks silently), the extension not reloaded after the edit, or being in chat mode — MCP tools are used in agent mode. Validate the YAML, reload the window, switch modes.

Is tavily-mcp free to run?

The MCP server itself is open source and free. Searches go through Tavily's API under your key, which Tavily meters — they have a free tier; check tavily.com for current limits.

tavily-mcp in Cline tavily-mcp in Zed Search MCP servers What is an MCP client?

More MCP servers for Continue.dev.

Every Loomal listing shows the server's actual tools before you configure it.

Browse the marketplace