Labsco
kshern logo

MCP Tavily

β˜… 10

from kshern

Advanced web search and content extraction using the Tavily API.

πŸ”₯πŸ”₯πŸ”₯πŸ”₯βœ“ VerifiedAccount requiredAdvanced setup
#automation#git#search#monitoring#news

MCP Tavily

smithery badge

δΈ­ζ–‡ζ–‡ζ‘£

A Model Context Protocol (MCP) server implementation for Tavily API, providing advanced search and content extraction capabilities.

Features

  • Multiple Search Tools:
    • search: Basic search functionality with customizable options
    • searchContext: Context-aware search for better relevance
    • searchQNA: Question and answer focused search
  • Content Extraction: Extract content from URLs with configurable options
  • Rich Configuration Options: Extensive options for search depth, filtering, and content inclusion

Usage with MCP

Add the Tavily MCP server to your MCP configuration:

{
  "mcpServers": {
    "tavily": {
      "command": "npx",
      "args": ["-y", "@mcptools/mcp-tavily"],
      "env": {
        "TAVILY_API_KEY": "your-api-key"
      }
    }
  }
}

Note: Make sure to replace your-api-key with your actual Tavily API key. You can also set it as an environment variable TAVILY_API_KEY before running the server.

API Reference

Search Tools

The server provides three search tools that can be called through MCP:

// Tool name: search
{
  query: "artificial intelligence",
  options: {
    searchDepth: "advanced",
    topic: "news",
    maxResults: 10
  }
}
// Tool name: searchContext
{
  query: "latest developments in AI",
  options: {
    topic: "news",
    timeRange: "week"
  }
}
// Tool name: searchQNA
{
  query: "What is quantum computing?",
  options: {
    includeAnswer: true,
    maxResults: 5
  }
}

Extract Tool

// Tool name: extract
{
  urls: ["https://example.com/article1", "https://example.com/article2"],
  options: {
    extractDepth: "advanced",
    includeImages: true
  }
}

Search Options

All search tools share these options:

interface SearchOptions {
  searchDepth?: "basic" | "advanced";    // Search depth level
  topic?: "general" | "news" | "finance"; // Search topic category
  days?: number;                         // Number of days to search
  maxResults?: number;                   // Maximum number of results
  includeImages?: boolean;               // Include images in results
  includeImageDescriptions?: boolean;    // Include image descriptions
  includeAnswer?: boolean;               // Include answer in results
  includeRawContent?: boolean;           // Include raw content
  includeDomains?: string[];            // List of domains to include
  excludeDomains?: string[];            // List of domains to exclude
  maxTokens?: number;                    // Maximum number of tokens
  timeRange?: "year" | "month" | "week" | "day" | "y" | "m" | "w" | "d"; // Time range for search
}

Extract Options

interface ExtractOptions {
  extractDepth?: "basic" | "advanced";   // Extraction depth level
  includeImages?: boolean;               // Include images in results
}

Response Format

All tools return responses in the following format:

{
  content: Array<{
    type: "text",
    text: string
  }>
}

For search results, each item includes:

  • Title
  • Content
  • URL

For extracted content, each item includes:

  • URL
  • Raw content
  • Failed URLs list (if any)

Error Handling

All tools include proper error handling and will throw descriptive error messages if something goes wrong.

Debugging with MCP Inspector

For development and debugging, we recommend using MCP Inspector, a powerful development tool for MCP servers.

The Inspector provides a user interface for:

  • Testing tool calls
  • Viewing server responses
  • Debugging tool execution
  • Monitoring server state

Support

For any questions or issues: