MCP Web Research Server

Created By
mzxraia year ago
MCP web research server (give Claude real-time info from the web)
Overview

what is MCP Web Research Server?

MCP Web Research Server is a Model Context Protocol (MCP) server that enables real-time information retrieval from the web for the AI model Claude, making research tasks more efficient.

how to use MCP Web Research Server?

To use the MCP Web Research Server, start by installing the Claude Desktop app and configuring it to integrate with the MCP server. Import a prebuilt prompt or interactively communicate with Claude while sending prompts that require web research.

key features of MCP Web Research Server?

  • Google search integration for instant query results
  • Page content extraction for in-depth analysis
  • Tracking of research sessions including visited pages and queries
  • Capability to capture and access screenshots of web pages

use cases of MCP Web Research Server?

  1. Conducting in-depth online research on current events
  2. Extracting information from various webpages for academic studies
  3. Capturing screenshots and documenting research progress

FAQ from MCP Web Research Server?

  • What platforms does it support?

It primarily supports macOS; Linux support is not confirmed yet.

  • Is it free to use?

Yes, it is open-source and freely available on GitHub.

  • Are there any known issues?

Yes, as it is pre-alpha code, users might encounter bugs, and they should check the logs in Claude Desktop for troubleshooting.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mzxrai
Star
258
Language
JavaScript
License
MIT 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)

2 days ago