MCP Web Search Tool

Created By
gabrimatica year ago
A MCP server providing real-time web search capabilities to any AI model.
Overview

What is MCP Web Search Tool?

The MCP Web Search Tool is a powerful Model Context Protocol (MCP) server that provides real-time web search capabilities to AI models, enabling them to access up-to-date information from various sources.

How to use MCP Web Search Tool?

To use the MCP Web Search Tool, clone the repository from GitHub, install the necessary dependencies, configure your environment variables, and start the server. You can also integrate it with the Claude Desktop app for enhanced functionality.

Key features of MCP Web Search Tool?

  • Real-Time Information Access: Allows AI assistants to retrieve current information from the web.
  • Pluggable Search Providers: Modular design for easy integration with different search engines.
  • Structured Output Format: Provides search results in a clean JSON format.
  • Smart Query Handling: Automatically categorizes queries for context-aware responses.

Use cases of MCP Web Search Tool?

  1. Retrieving live sports scores and updates.
  2. Accessing the latest news articles and trends.
  3. Providing real-time weather information.
  4. Enhancing AI assistants with current data for better user interaction.

FAQ from MCP Web Search Tool?

  • What programming languages are required?

Node.js (v16.x or newer) and npm (v7.x or newer) are required to run the tool.

  • Is there a cost to use the MCP Web Search Tool?

The tool is open-source and free to use, but you need a Brave Search API key for web access.

  • Can I integrate it with other applications?

Yes! The tool is designed to be modular and can be integrated with various applications, including the Claude Desktop app.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gabrimatic
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Voyei

2 hours ago
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