WebSearch-MCP

Created By
mnhlta year ago
[Self-hosted] A Model Context Protocol (MCP) server implementation that provides a web search capability over stdio transport. This server integrates with a WebSearch Crawler API to retrieve search results.
Overview

What is WebSearch-MCP?

WebSearch-MCP is a self-hosted Model Context Protocol (MCP) server that provides web search capabilities over stdio transport, integrating with a WebSearch Crawler API to retrieve real-time search results.

How to use WebSearch-MCP?

To use WebSearch-MCP, install it via npm or Smithery, configure the crawler service, and integrate it with your AI client applications to perform web searches.

Key features of WebSearch-MCP?

  • Real-time web search capabilities for AI assistants.
  • Integration with a Crawler API for retrieving search results.
  • Customizable configuration through environment variables.

Use cases of WebSearch-MCP?

  1. Enabling AI models to fetch up-to-date information from the web.
  2. Assisting in research by providing relevant search results.
  3. Enhancing AI applications with real-time data retrieval.

FAQ from WebSearch-MCP?

  • Can WebSearch-MCP be used with any AI model?

Yes! It can be integrated with any AI model that supports the Model Context Protocol.

  • Is WebSearch-MCP easy to set up?

Yes! It provides detailed installation and configuration instructions.

  • What are the prerequisites for running WebSearch-MCP?

You need Docker and Docker Compose to set up the crawler service.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mnhlt
Star
8
Language
JavaScript
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