pickfit

BrowseMCP servers

google-surf-mcp

MCP server that stores Google search, papers, and code in a local knowledge graph.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js >=22.12.0
  • System packages: Google Chrome or Chromium for browser mode
  • Keys or accounts: SearchApi key for optional primary/fallback search
  1. install google-surf-mcp globally via npm

    npm install -g google-surf-mcp

Check that it works

npx -y google-surf-mcp@latest hooks status --host codex 2>&1

The output should contain “installed”.

First thing to try

npx -y google-surf-mcp@latest hooks status --host codex 2>&1

Add it to your agent

claude mcp add google-surf-mcp -- google-surf-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "google-surf-mcp": {
      "command": "google-surf-mcp",
      "args": []
    }
  }
}

Add npx -y google-surf-mcp@latest as an MCP server in your MCP client, then call the health tool to confirm it is running.

What it does

  • Search the web, papers, and code
    Not tested
  • Extract text from HTML and PDF documents
    Not tested
  • Save results to project memory
    Not shown working
  • Analyze and export the local knowledge graph
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Needs the network

Good for

  • Find new information on the web
  • Run several new web queries
  • Search only previously stored research and project memory
  • Compare new web results with stored project knowledge

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Needed the network
  • Checked on 31 Oct 2026
  • Version 1.1.5

An MCP client handshake over stdio listed 7 tools, and a call to health returned a result.

Differences the test machine hit

  • README: npx google-surf-mcp launches via npx
    In the test: installed globally with npm install -g google-surf-mcp so binary is on PATH without network for replay
  • README: Chrome/Chromium required for browser mode
    In the test: box has no Chrome; server starts and reports Chrome not found but still completes handshake and local tools work

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.