Data · Local MCP server
Google Surf MCP
Web, academic and code search with graph RAG, data lineage, ontology and cross-project schema links.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.HarimxChoi/google-surf-mcp- Version
- 1.1.3
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-10
- Updated
- 2026-09-10
- Publisher
- HarimxChoi (GitHub)
- Repository
- github.com/HarimxChoi/google-surf-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | google-surf-mcp | 1.1.3 | stdio |
How to connect Google Surf MCP
Google Surf MCP runs locally from a Node.js package published to the npm registry: google-surf-mcp version 1.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y google-surf-mcp@1.1.3. It reads these environment variables: SEARCH_API (secret), SURF_SEARCH_PROVIDER, SURF_SCHOLAR_PROVIDER, SURF_BROWSER_ENGINE, CHROME_PATH, SURF_PROFILE_ROOT, SURF_RESEARCH, SURF_RETRIEVAL_MODE, SURF_RESEARCH_ROOT, SURF_RESEARCH_VECTOR_MODEL, SURF_RESEARCH_VECTOR_LOW_MEMORY, SURF_RESEARCH_VECTOR_THREADS, SURF_RESEARCH_REPO_AUTO, SURF_RESEARCH_REPO_AUTO_MAX_MB, SURF_RESEARCH_REPO_AUTO_MAX_FILES, SURF_RESEARCH_BROKER_IDLE_MS, SURF_RESEARCH_READ_CONCURRENCY, SURF_RESEARCH_QUERY_TIMEOUT_MS, GITHUB_TOKEN (secret) and SURF_LOCALE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"google-surf-mcp": {
"command": "npx",
"args": [
"-y",
"google-surf-mcp@1.1.3"
],
"env": {
"SEARCH_API": "<secret>",
"SURF_SEARCH_PROVIDER": "<value>",
"SURF_SCHOLAR_PROVIDER": "<value>",
"SURF_BROWSER_ENGINE": "<value>",
"CHROME_PATH": "<value>",
"SURF_PROFILE_ROOT": "<value>",
"SURF_RESEARCH": "<value>",
"SURF_RETRIEVAL_MODE": "<value>",
"SURF_RESEARCH_ROOT": "<value>",
"SURF_RESEARCH_VECTOR_MODEL": "<value>",
"SURF_RESEARCH_VECTOR_LOW_MEMORY": "<value>",
"SURF_RESEARCH_VECTOR_THREADS": "<value>",
"SURF_RESEARCH_REPO_AUTO": "<value>",
"SURF_RESEARCH_REPO_AUTO_MAX_MB": "<value>",
"SURF_RESEARCH_REPO_AUTO_MAX_FILES": "<value>",
"SURF_RESEARCH_BROKER_IDLE_MS": "<value>",
"SURF_RESEARCH_READ_CONCURRENCY": "<value>",
"SURF_RESEARCH_QUERY_TIMEOUT_MS": "<value>",
"GITHUB_TOKEN": "<secret>",
"SURF_LOCALE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Google Search ConsoleMCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection. | Local · stdio |
| Google Search Console MCPMCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites. | Local · stdio |
| Google Search Console MCPRead-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools. | Local · stdio |
| Google Search data for agents1 Google Search endpoints. Pay per call in USDC via x402. | Remote · HTTP |
| Google Trends (via Apify)Google Trends data for AI agents: interest over time, regions, rising queries and trending searches. | Remote · HTTP |
| Google Trends APIGoogle Trends search interest over time with growth metrics. Free key at trendsapi.ai. | Remote · HTTP |
| Google Trends Scraper (orbots) - Apify ActorGoogle Trends trending searches, volume estimates & trend duration. Not affiliated with Google LLC. | Remote · HTTP |
| Google Web SearchGoogle Web Search: Google Web Search API. Search the world’s information, including webpages. | Remote · HTTP |