Skip to main content
Glama
online111111

Tavily Search MCP Server

by online111111
README.md
# Tavily Search MCP Server

A Model Context Protocol (MCP) server for the [Tavily Search API](https://tavily.com/) with automatic multi-key fallback. Built with FastMCP.

## Features

- πŸ”„ **Multi-key auto fallback** β€” automatically rotates through `TAVILY_API_KEY_1`, `TAVILY_API_KEY_2`, etc. when rate-limited
- 🌐 **Web search** β€” `tavily_search` for general web search
- πŸ“„ **Content extraction** β€” `tavily_extract` to get content from URLs
- πŸ—ΊοΈ **Crawl & Map** β€” `tavily_crawl` / `tavily_map` for website structure
- πŸ”¬ **Deep Research** β€” `tavily_research_create` / `tavily_research_get` for AI-powered research
- πŸ“Š **Usage tracking** β€” `tavily_usage` to check API quota

## Quick Start

```json
{
  "mcpServers": {
    "tavily-search": {
      "command": "uvx",
      "args": ["tavily-search-mcp-server"]
    }
  }
}
```

## Environment Variables

| Variable | Required | Description |
|----------|----------|-------------|
| `TAVILY_API_KEY_1` | Yes | Primary Tavily API key |
| `TAVILY_API_KEY_2..5` | No | Fallback keys for auto-rotation |

The server automatically discovers `TAVILY_API_KEY_*` env vars and falls back through them on 429 errors. Also supports single `TAVILY_API_KEY` for backward compatibility.

## Available Tools

| Tool | Description |
|------|-------------|
| `tavily_search` | Search the web with configurable depth, topic, time range |
| `tavily_extract` | Extract content from one or more URLs |
| `tavily_crawl` | Crawl a website with depth/breadth control |
| `tavily_map` | Map website structure |
| `tavily_search_context` | Search with raw content results |
| `tavily_research_create` | Create a deep research task |
| `tavily_research_get` | Get research task status/results |
| `tavily_usage` | Check API usage/quota |

## License

MIT

TDQS

B3.3/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search, search with context, crawl, extract, map, research creation, research retrieval, and usage monitoring. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the consistent 'tavily_<verb>' pattern, using clear action verbs like search, crawl, extract, map, research_create, research_get, and usage. No mixing of conventions.

Tool Count5/5

8 tools is appropriate for a web search and research service, covering core operations without being excessive or insufficient.

Completeness4/5

The tool surface covers search, crawling, extraction, site mapping, research tasks, and usage monitoring. Minor gap: no tool to list or cancel research tasks, but core workflows are covered.

Maintenance

ActivityInactive
ResponsivenessNo issues