A
licenseNot graded
qualityD
maintenanceA proxy MCP server for Tavily search and extract APIs with support for multiple API keys, random rotation, and bearer token authentication.
MIT
tavily-pool-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tavily-pool-mcpsearch for latest developments in artificial intelligence"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
tavily-pool-mcp
A local Model Context Protocol server that exposes a Tavily search tool and rotates across multiple Tavily API keys.
Features
Exposes
tavily_searchas an MCP toolRotates across multiple Tavily API keys
Retries with another key on
401,403, or429Works with OpenCode and other MCP-compatible clients
Related MCP server: AIE7-MCP
Requirements
Node.js 18+
Tavily API keys
Install
npm installConfiguration
Set TAVILY_API_KEYS as a space, comma, or semicolon separated list:
export TAVILY_API_KEYS="tvly-dev-key-1 tvly-dev-key-2 tvly-dev-key-3"On Windows PowerShell:
$env:TAVILY_API_KEYS="tvly-dev-key-1 tvly-dev-key-2 tvly-dev-key-3"Run
npm startnpm start starts a stdio MCP server, so the terminal will wait for MCP input. This is expected.
OpenCode Config
Add this to your OpenCode opencode.json:
{
"mcp": {
"tavily-pool": {
"type": "local",
"enabled": true,
"command": ["node", "C:/path/to/tavily-pool-mcp/src/index.mjs"],
"environment": {
"TAVILY_API_KEYS": "{env:TAVILY_API_KEYS}"
}
}
}
}Tool
tavily_search
Arguments:
query: search querymax_results: 1-20, default 5search_depth:basicoradvanced, defaultbasicinclude_answer: boolean, default falseinclude_raw_content: boolean, default false
Security
Do not commit real API keys. Use environment variables or a secret manager.
License
MIT
Available Tools
1 tooltavily_searchC
Search the web using Tavily. This MCP rotates across multiple API keys.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| max_results | No | ||
| search_depth | No | basic | |
| include_answer | No | ||
| include_raw_content | No |
TDQS
C2.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description mentions a behavioral trait: 'rotates across multiple API keys', which is beyond the (missing) annotations. However, it omits other important details like rate limits, costs, or result format, which would be expected for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is succinct with two sentences. The first sentence clearly states the core purpose, and the second adds a key behavioral detail. No extraneous information is present.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 5 parameters, no output schema, and no annotations, the description is too minimal. The agent lacks information about return values, pagination, or how to interpret results, making it insufficient for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema coverage is low (20%), with only 'query' having a description. The description adds no information about parameters such as max_results, search_depth, include_answer, or include_raw_content, leaving the agent without guidance on their meaning or usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Search' and the resource 'web using Tavily', which is a specific search engine. The purpose is unambiguous, and since there are no sibling tools, differentiation is not required.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives or when not to use it. The description only implies usage for web searches, but lacks exclusion criteria or context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
B3.4/5.0
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion or overlap.
Naming Consistency5/5
The single tool follows a clear verb_noun pattern (tavily_search), which is consistent and predictable.
Tool Count3/5
One tool is on the low end but reasonable for a focused search service; it is borderline but not inappropriate.
Completeness5/5
The search tool fully covers the server's purpose of web search; no obvious missing operations.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Serper MCP — wraps the Serper Google Search API (serper.dev)
Related MCP Servers
- FlicenseAqualityDmaintenanceMCP server that provides web search capabilities using the Tavily API.3
- AlicenseBqualityDmaintenanceMCP server providing search, extract, map, and crawl tools powered by Tavily for real-time web data access.414MIT
- FlicenseNot gradedqualityCmaintenanceAn experimental MCP server that provides web search capabilities using the Tavily API. Still in progress, not production-ready.
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yanjin734-ltsm/TAVILY_POOL_MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server