Local stdio MCP proxy with lazy Tavily API key failover
Most developer tooling work still happens through a UI a human drives. Tavily MCP server moves it into the conversation instead. Local stdio MCP proxy with lazy Tavily API key failover.
它将 Tavily 上游提供的工具定义、参数和调用结果转发给 Agent，并负责管理多个 API Key。当当前 Key 的额度耗尽、受到限流或失效时，代理会自动切换到下一个 Key， 无需修改 Agent 的提示词或工具调用方式。
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 4 tools. What each one is for:
TAVILY_API_KEYS — The TAVILY_API_KEYS tool exposed by this serverTAVILY_MCP_URL — The TAVILY_MCP_URL tool exposed by this serverTAVILY_PROXY_LOG_LEVEL — The TAVILY_PROXY_LOG_LEVEL tool exposed by this serverTAVILY_RESET_GRACE_SECONDS — Tavily 说明月度额度在每月第一天重置，但 Usage API 不提供精确重置时刻。本工具会在 下个月 UTC 1 日 00:00 后等待该缓冲时间，再检查旧 Key 是否恢复额度。Configuration is passed through the environment: TAVILY_API_KEYS, TAVILY_PROXY_LOG_LEVEL, TAVILY_MCP_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tavily's toolset — TAVILY_API_KEYS, TAVILY_MCP_URL, TAVILY_PROXY_LOG_LEVEL and 1 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Tavily's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| TAVILY_API_KEYS | The TAVILY_API_KEYS tool exposed by this server. |
| TAVILY_MCP_URL | The TAVILY_MCP_URL tool exposed by this server. |
| TAVILY_PROXY_LOG_LEVEL | The TAVILY_PROXY_LOG_LEVEL tool exposed by this server. |
| TAVILY_RESET_GRACE_SECONDS | Tavily 说明月度额度在每月第一天重置，但 Usage API 不提供精确重置时刻。本工具会在 下个月 UTC 1 日 00:00 后等待该缓冲时间，再检查旧 Key 是否恢复额度。 |
{
"mcpServers": {
"tavily": {
"command": "npx",
"args": ["-y", "tavily-proxy-mcp"],
"env": {
"TAVILY_API_KEYS": "tvly-key1,tvly-key2,tvly-key3"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TAVILY_API_KEYS | Credential the server authenticates with. | Yes |
| TAVILY_PROXY_LOG_LEVEL | Configuration value read at startup. | Optional |
| TAVILY_MCP_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.