tavily-mcp MCP server in Cursor give the agent fresh search results.
Cursor's agent is only as current as its context. tavily-mcp (2.1k GitHub stars) plugs Tavily's search API into Cursor as an MCP tool — a small mcp.json entry and a toggle, and the agent can research while it codes.
Cursor supports MCP servers in two scopes: ~/.cursor/mcp.json applies everywhere, while .cursor/mcp.json inside a repo applies to that project only. tavily-mcp works identically in both — it's an npm package Cursor spawns over stdio, with your Tavily API key passed as an environment variable.
Once connected, Cursor's agent can call Tavily search on its own when a task needs current information: checking what an error message means, confirming an API's current signature, or pulling recent docs the model hasn't seen.
Two ways in: settings UI or the file
The UI route: Cursor Settings > MCP > Add new MCP server, which writes the same JSON for you. The direct route: create or edit ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project root. Either way you'll need a Tavily API key from tavily.com and Node.js on your machine.
Project-scoped config is worth considering for teams — committing .cursor/mcp.json (with the key supplied some other way, never committed) means everyone who opens the repo gets the same toolset.
The config block
Cursor uses the common mcpServers shape:
{
"mcpServers": {
"tavily-mcp": {
"command": "npx",
"args": ["-y", "tavily-mcp"],
"env": {
"TAVILY_API_KEY": "tvly-YOUR_API_KEY"
}
}
}
}Enable the toggle and confirm tools
This is the step people miss in Cursor: after saving the file, open Settings > MCP and flip the toggle next to tavily-mcp to enabled. Cursor lists each server with a status dot and, once green, shows the tools the server exposed. No full editor restart is required for config changes picked up through the settings page, though restarting is a clean fallback.
Test it in the agent panel: "use tavily to search for the latest TypeScript release notes." The agent should surface a tool call you can approve, then cite what it found.
Fixing a red dot
Yellow or red status next to the server means the spawn failed. Check, in order: JSON validity (Cursor won't parse a file with a trailing comma), the package name (exactly tavily-mcp), and whether npx resolves in Cursor's environment — on macOS, GUI apps don't always inherit shell PATH tweaks from .zshrc, so a Node installed via the official installer is the most reliable.
If the server connects but searches fail, that's the API key: wrong value, or the Tavily account is over its quota. The env block in mcp.json must use the literal key string — Cursor doesn't expand $VARIABLES there. And if you used a project-scoped file, the server only appears when that folder is open.
See the listing
tavily-mcp is indexed on the Loomal marketplace with its live tool list at https://loomal.ai/marketplace/tavily-mcp. The server is free, open-source software; Tavily's API meters usage under your key. Loomal's index also carries x402-ready endpoints that agents pay per call in USDC — relevant if you're comparing search options where you'd rather pay per query than manage another subscription.
FAQ
How do I install tavily-mcp in Cursor?
Add a tavily-mcp entry to ~/.cursor/mcp.json (or .cursor/mcp.json for one project) with command npx, args ["-y", "tavily-mcp"], and your TAVILY_API_KEY in env — then enable the server's toggle in Cursor Settings > MCP.
Should the config go in ~/.cursor or .cursor in my repo?
Global (~/.cursor/mcp.json) makes Tavily available in every project. Project scope (.cursor/mcp.json) limits it to one repo and is shareable with teammates — just don't commit a real API key.
I added the JSON but no tools appear — why?
Most often the server toggle in Settings > MCP is still off. After that, check for JSON syntax errors and confirm npx runs in a terminal. The status dot next to the server in settings tells you whether it started.
Does Cursor ask before running Tavily searches?
By default the agent shows MCP tool calls for approval before executing them. You can allow tools to run automatically in Cursor's settings if you'd rather not approve each search.
Browse more MCP servers for Cursor.
Live tool lists on every Loomal listing — know what a server does before you add it.