Web Search MCP Server

Created By
matemiroa year ago
A Model Context Protocol (MCP) server that provides a web search tool using the Tavily API. This server enables AI models to search the internet and retrieve up-to-date information.
Overview

What is the Web Search MCP Server?

The Web Search MCP Server is a Model Context Protocol (MCP) server that utilizes the Tavily API to provide a web search tool, enabling AI models to search the internet and retrieve up-to-date information.

How to use the Web Search MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, configure your Tavily API key in a .env file, and run the server using the command uv run web_search_server.py.

Key features of the Web Search MCP Server?

  • Real-time web search capabilities using the Tavily API.
  • Customizable search parameters including search topic, depth, maximum results, and time range filtering.

Use cases of the Web Search MCP Server?

  1. Integrating real-time search capabilities into AI chatbots.
  2. Enabling AI models to access current information during conversations.
  3. Conducting research with customizable search parameters.

FAQ from the Web Search MCP Server?

  • What programming language is required?

Python 3.13+ is required to run the server.

  • Do I need an API key?

Yes, you need to sign up at tavily.com to obtain a Tavily API key.

  • Can I customize the search parameters?

Yes, the server allows customization of search topics, depth, and other parameters.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
matemiro
Star
0
Language
Python
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