Chrome Google SearchCAUTION
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
MCP tool for Google search and webpage content extraction using Chrome browser. Works with Claude to enable Google search and content fetching capabilities.
Quick Installation
- Configure Claude Desktop
- Open Claude Desktop on Mac
- Go to Claude > Settings > Developer > Edit Config
- Add the following to your config file:
{
"mcpServers": {
"mcp-chrome-google-search": {
"command": "npx",
"args": [
"-y",
"@cmann50/mcp-chrome-google-search"
]
}
}
}- Restart Claude Desktop
- First Time Setup
- Grant Accessibility Permissions
- On first run, approve macOS accessibility permissions prompt
- Navigate to: System Preferences > Security & Privacy > Privacy > Accessibility
- Add and enable permissions for your terminal app
- Enable Chrome JavaScript from Apple Events
- Open Chrome
- Navigate to: View > Developer > Allow JavaScript from Apple Events
- One-time setup only
Once configured, Claude will be able to perform Google searches and extract webpage content through Chrome when you make requests.
Key Advantages
- Free to search google
- Opens and small windows and uses your chrome browser, so should not get blocked
- Since it is using your Chrome window it can access authenticated content. Claude can just open the URL in your browser.
Platform Support
- ✅ macOS
- ❌ Windows (not supported)
- ❌ Linux (not supported)
Requirements
- macOS
- Google Chrome
- Node.js 20 or higher
Alternative Installation Methods
NPX Installation
npx mcp-chrome-google-search
Custom Installation
- Checkout from git
- Run
npm run build - Add to Claude config (use absolute path):
{
"google-tools": {
"command": "node",
"args": [
"/your/checkout/path/mcp/mcp-chrome-google-search/dist/index.js"
]
}
}8b88e5f28465OBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-chrome-google-search -- npx -y @cmann50/[email protected]
{
"mcpServers": {
"mcp-chrome-google-search": {
"command": "npx",
"args": [
"-y",
"@cmann50/[email protected]"
]
}
}
}Exposed tools (2)
2 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
web-search | read | Search webpages and get a specific page of results (each page has ~10 results). Optionally filter by site and timeframe. |
web_fetch | read | Extract readable text content from a webpage using Chrome browser automation.\n\nKey Features:\n- Returns main content text and optionally links |
Trust audit
CAUTIONgrade B · trust 85/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (4 observation(s))
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (7)
<a id="js-link-box-fa" href="//fa.wikipedia.org/" title="Fārsi — ویکیپدیا — دانشنامهٔ آزاد" class="link-box" data-slogan="دانشنامهٔ آزاد">
import { runOsascript } from '../../utils/osascript.js';import { buildGoogleSearchUrl } from '../../utils/url.js';import type { SearchParams, SearchResult } from '../../types/search.js';import { runOsascript } from '../../utils/osascript.js';import {getWebContent} from '../../src/toolsImpl/webFetchTool';@modelcontextprotocol/sdk, @types/cheerio, cheerio, zod, @types/jest, @types/node, jest, ts-jest
Gates applied: no_behavioural_pass.
8b88e5f28465full audit observations/trust-audit/mcp-server/cmann50__chrome-google-search.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 8b88e5f28465 | CAUTION | B | 85 | first audit |
Questions
What tools does Chrome Google Search expose?
2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Chrome Google Search safe to connect to an agent?
With care. The audit graded it B (85/100) and found 7 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does Chrome Google Search need?
No credential environment variables were found in its source, so it appears to need none.
How does Chrome Google Search run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @cmann50/mcp-chrome-google-search at 1.0.6.
How current is this page?
The grade is for one exact copy of the source (8b88e5f28465), read on 2026-10-09. The repository is watched and re-audited when it changes.