MCP Webresearch MCP Server

MCP server for web research

Local serverstdio

What is the MCP Webresearch MCP server?

MCP Webresearch MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for web research.

What you get

Bring real-time info into Claude and easily research any topic.

  • Google search integration
  • Webpage content extraction
  • Research session tracking (list of visited pages, search queries, etc.)
  • Screenshot capture

What the assistant can call

Once MCP Webresearch is connected, these are the calls the assistant has available:

  • Arguments — { query: string }
  • Tools — 1. search_google - Performs Google searches and extracts results - Arguments: { query: string }
  • Prompts — The Prompts tool exposed by this server
  • Resources — We expose two things as MCP resources: (1) captured webpage screenshots, and (2) the research session
  • Screenshots — When you take a screenshot, it's saved as an MCP resource. You can access captured screenshots in Claude Desktop via the Paperclip icon
  • Suggestions — For the best results, if you choose not to use the agentic-research prompt when doing your research, it may be helpful to suggest high-quality

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

Choosing this one

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Webresearch's toolset — Arguments, Tools, Prompts and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mzxrai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp webresearch mcp server does with a few real requests.

Available tools

ToolWhat it does
Arguments{ query: string }
Tools1. search_google - Performs Google searches and extracts results - Arguments: { query: string }
PromptsThe Prompts tool exposed by this server.
ResourcesWe expose two things as MCP resources: (1) captured webpage screenshots, and (2) the research session.
ScreenshotsWhen you take a screenshot, it's saved as an MCP resource. You can access captured screenshots in Claude Desktop via the Paperclip icon.
SuggestionsFor the best results, if you choose not to use the agentic-research prompt when doing your research, it may be helpful to suggest high-quality sources for Claude to use when researching general topics. For example, you c

How to install the MCP Webresearch MCP server

{
  "mcpServers": {
    "webresearch": {
      "command": "npx",
      "args": ["-y", "@mzxrai/mcp-webresearch@latest"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

Example prompts to try

  • Use MCP Webresearch to Arguments.
  • Use MCP Webresearch to Tools.
  • Use MCP Webresearch to Prompts.

Frequently asked questions

It connects MCP Webresearch to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Arguments, Tools, Prompts, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Webresearch directly.