tavily-search MCP server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Tavily-Search MCP Server?

Tavily-Search MCP Server is a project that utilizes the Tavily API to perform web searches based on user-defined queries, returning results in a structured format.

how to use Tavily-Search MCP Server?

To use the server, clone the repository, configure the necessary settings in the Claude Desktop configuration file, and restart the application. You can then issue search commands through Claude Desktop.

key features of Tavily-Search MCP Server?

  • Integration with the Tavily API for search functionality.
  • Ability to specify search depth (basic or advanced).
  • Returns search results including AI-generated responses, URIs, and titles.

use cases of Tavily-Search MCP Server?

  1. Performing detailed searches for events or information.
  2. Utilizing AI responses to enhance search results.
  3. Running in local environments using Docker for broader compatibility.

FAQ from Tavily-Search MCP Server?

  • What is required to run the server?

You need to have the Claude Desktop application and a valid Tavily API key.

  • Can I run this server on operating systems other than Windows or MacOS?

Yes! You can set it up using Docker Compose for other operating systems.

  • How do I view the logs?

Logs are stored in the specified directory within the Claude application data folder.

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

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago