
Google Surf Mcp
io.github.HarimxChoiPublished by GitHub account HarimxChoiv1.1.6Updated Nov 7, 2026
Web, academic and code search with graph RAG, data lineage, ontology and cross-project schema links.
Overview
Searches the web, Google Scholar and code repositories, extracts pages and PDFs, and files results into a local knowledge graph for later retrieval.
- What you can do
- Search the web and run parallel searches, optionally reading results in the same call
- Find paper metadata on Google Scholar
- Extract content from a known URL, PDF or repository
- Search and manage local project memory: save records, index approved folders, export graphs
- Inspect search and local runtime health
- Organize sources into a typed knowledge graph with evidence, lineage and cross-project links
- When to use it
- Useful when an assistant needs live web, paper or code research and you want the findings kept in a local, searchable knowledge base across projects, rather than re-searching each time.
- Requirements
- Runs locally via npx; needs Node.js 22.12+ and Chrome or Chromium for browser search. No API key required by default. Optional: SEARCH_API for SearchApi provider or fallback, GITHUB_TOKEN for higher GitHub limits, ANTHROPIC_API_KEY or ORCAROUTER_API_KEY for LLM selector repair. First indexing may download a local embedding model.
Installation
In SourceWeft
- Open Google Surf Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
google-surf-mcp
English | Korean
Google Surf MCP searches the web, papers, and codebases, then uses Auto Ontology to organize what you read into a local knowledge graph. Start without an API key or a separate database server, and build a personal knowledge base from connected sources and project records.
[npm version] [npm downloads] [ci] [MCP Toplist] [google-surf-mcp MCP server]
Sponsored by SearchApi
[Integrated project knowledge graph]
Core features
- Search and read: Find web pages, papers, PDFs, GitHub repositories, and indexed local code. Tree-sitter links files, code symbols, imports, and function calls.
- Auto Ontology: Organize sources and project records into a typed knowledge graph with evidence and data lineage.
- Cross-project search: Find stored sources across selected projects using exact-match, keyword, semantic, and graph retrieval, with RRF fusion and a shared reranker.
- Explore and export: Browse PKM, lineage, and ontology views; export HTML, PNG, JSON, Graphviz DOT, and Neo4j import bundles.
Stack: TypeScript, Chrome/Playwright, LiteParse, Tree-sitter, SurrealDB, Multilingual E5, and Graphology. Architecture
Quick start
Requires Node.js 22.12+ and Chrome or Chromium for browser search. CI covers Node 22 and 24 on Linux and Windows.
Register the server in your MCP client:
Restart the client. Auto Ontology is enabled by default; the local embedding model may be downloaded when you first index content.
For search and extraction without the database or embedding model, set SURF_RESEARCH=false in the server environment.
Client setup, local installation, and SearchApi configuration
Search
- Search through system Chrome without an API key
- Dedicated logged-out profile; your personal Chrome profile is never read or copied
- Multi-strategy SERP parsing with geometric verification
- Removal of sponsored results and knowledge panels
- CAPTCHA detection and environment-specific recovery
- Parser self-healing and context fallback
Browser search is the default. SearchApi is an optional primary provider or fallback; it requires your own account, key, and credits.
Supported AI providers and gateways
- OrcaRouter (free models available)
Optional LLM-assisted repair and OrcaRouter setup
Tools
Seven tools are available with Auto Ontology enabled:
Providing project_id to web search does not make it local-only. Use project_memory_search for stored knowledge.
Tool parameters, limits, follow-up reads, and repeatable source collection
Google Surf Auto Ontology
Search and extraction results are saved automatically. Plans, experiments, failures, and decisions are linked when your agent records them through project_memory.
Projects stay separate by default. Selected projects can link knowledge using matching DOIs, repository URLs, or explicitly registered aliases; original records are not merged or moved.
Create a standalone graph explorer for one project:
The HTML explorer includes PKM, lineage, and ontology views with PNG/JSON downloads. DOT and Neo4j exports are also available.
The feature was renamed from Research to Auto Ontology; existing SURF_RESEARCH* settings, project_memory* tools, CLI names, and storage paths still work.
Ontology, lineage, code indexing, and export details
Benchmark
Live web result ranking on 32 held-out queries:
Evaluation conditions, retrieval results, and resource measurements
Documentation
Source: README.md at commit 6faa98d
Tools
0Version history
4- v1.1.6LatestNov 7, 2026
- v1.1.5Oct 30, 2026
- v1.1.4Oct 20, 2026
- v1.1.3Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts