MCP server for Google search via warm Chrome profile. No API key.
MCP server for Google search via warm Chrome profile. No API key. That is what the google mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
One MCP replaces three: search + URL fetcher + academic-paper extractor.
The server publishes 1 tool. What each one is for:
Response — content, title, excerpt, length, is_pdf, page_count, extraction_quality. Failures return { error }, never throwConfiguration is passed through the environment: CHROME_PATH, ANTHROPIC_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
google-surf-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Google's toolset — Response — is a fair guide to whether it matches your workflow. It is maintained by harimchoi; 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.
| Tool | What it does |
|---|---|
| Response | content, title, excerpt, length, is_pdf, page_count, extraction_quality. Failures return { error }, never throw. |
{
"mcpServers": {
"google-surf": {
"command": "npx",
"args": ["-y", "google-surf-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHROME_PATH | Filesystem location the server is allowed to use. | Optional |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.