Tavily MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Set to "production" for production deployment (optional) | |
| TAVILY_API_KEY | Yes | Your Tavily API key (required) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchB | Search the web using Tavily API. Returns relevant search results with content snippets. |
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 between tools. The single tool 'web_search' has a clearly defined and distinct purpose, making it impossible for an agent to misselect between non-existent alternatives.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'web_search' follows a clear verb_noun pattern, but with no other tools to compare against, there can be no inconsistency in the set.
A single tool is too few for a server named 'Tavily MCP Server', which implies broader web search capabilities. While 'web_search' covers the core function, typical search servers might include tools for advanced queries, filtering, or result analysis, making this feel thin and limited in scope.
The tool surface is severely incomplete for a web search domain. It lacks obvious gaps such as tools for refining searches (e.g., by date or source), handling pagination, or accessing cached content, which could lead to agent failures when trying to perform comprehensive search tasks.