Tavily Search MCP Server

Created By
apappascsa year ago
An MCP server implementation that integrates the Tavily Search API, providing optimized search capabilities for LLMs.
Overview

What is Tavily Search MCP Server?

Tavily Search MCP Server is an implementation that integrates the Tavily Search API, providing optimized search capabilities specifically designed for Large Language Models (LLMs).

How to use Tavily Search MCP Server?

To use the Tavily Search MCP Server, you need to clone the repository, install the necessary dependencies, and configure it with your Tavily API key. You can run the server using Node.js or Docker.

Key features of Tavily Search MCP Server?

  • Web Search: Perform optimized web searches for LLMs with customizable parameters.
  • Content Extraction: Extracts relevant content from search results for better quality and size.
  • Optional Features: Include images, descriptions, and LLM-generated answers in the results.
  • Domain Filtering: Control which domains to include or exclude in search results.

Use cases of Tavily Search MCP Server?

  1. Enhancing search capabilities for AI-driven applications.
  2. Providing tailored search results for specific topics or domains.
  3. Integrating with other LLMs to improve information retrieval.

FAQ from Tavily Search MCP Server?

  • Can I use Tavily Search MCP Server without an API key?

No, you need a Tavily API key to access the search functionalities.

  • Is there a free tier available for the Tavily API?

Yes, Tavily offers a free tier for users to get started.

  • How do I run the server using Docker?

You can build and run the Docker container using the provided commands in the setup guide.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
apappascs
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago