tavily-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tavily_searchA | Search the public web with Tavily. Defaults to Basic Search (1 API credit). Advanced Search costs 2 credits and must be explicitly selected. Automatic parameter selection is disabled to prevent an unexpected upgrade to Advanced. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The single tool has a clear and unique purpose.
The tool name 'tavily_search' follows a consistent verb_noun pattern. With only one tool, naming consistency is trivially maintained.
The server has a single tool, which feels thin for a typical MCP server. It is borderline appropriate for a narrowly focused search server, but could benefit from additional related tools.
The tool covers the core web search capability well, including basic and advanced search options. However, it lacks other potentially useful Tavily features like extract or crawl endpoints, making it slightly incomplete for a full Tavily integration.