MCP.so
ログイン

Tavily Search MCP Server

@apappascs

Tavily Search MCP Server について

An MCP server implementation that integrates the Tavily Search API, providing optimized search capabilities for LLMs.

基本情報

カテゴリ

検索

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

apappascs

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "tavily-search-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "@apappascs/tavily-search-mcp-server",
        "--client",
        "claude"
      ]
    }
  }
}

ツール

1

Execute web searches using the Tavily Search API.

概要

What is Tavily Search MCP Server?

Tavily Search MCP Server is an MCP server implementation that integrates the Tavily Search API, providing optimized web search capabilities for large language models.

How to use Tavily Search MCP Server?

Clone the repository, install dependencies, build the project, and configure your Tavily API key in the Claude Desktop MCP configuration file. Use the tavily_search tool to execute web searches with optional parameters like search depth, topic, domain filtering, and result inclusion of images or raw content.

Key features of Tavily Search MCP Server

  • Web search optimized for LLMs
  • Content extraction from search results
  • Optional images, image descriptions, and LLM-generated answers
  • Domain filtering (include or exclude domains)
  • Control over search depth, topic, and time range

Use cases of Tavily Search MCP Server

  • Enhancing LLM responses with real-time web data
  • Aggregating news articles with time range filtering
  • Extracting relevant content from search results for analysis
  • Filtering searches by specific domains for focused research
  • Including images and descriptions for rich information retrieval

FAQ from Tavily Search MCP Server

Do I need a Tavily API key?

Yes, a Tavily API key is required. Obtain one from the Tavily dashboard after signing up.

What are the runtime dependencies?

Node.js is required for npm-based usage; Docker is also supported. The server can run via stdio or SSE transport.

Where does the search data come from?

All data is fetched from the Tavily Search API. No search results are stored locally.

What transports are supported?

The server supports both stdio (default) and SSE transport, configurable in the Claude Desktop configuration or via the TRANSPORT environment variable when using Docker.

Is there any limit on the number of results?

The max_results parameter defaults to 5 and can be increased, but actual limits depend on your Tavily API plan (a free tier is available).

コメント

「検索」の他のコンテンツ