Google AI Search MCP
Provides AI-powered search and documentation tools using Google's Gemini API, enabling real-time web search queries, technical documentation analysis, code snippet retrieval, and technology comparisons with search grounding.
Integrates with Google Cloud's Vertex AI to provide AI-powered search and documentation tools, including web search grounding, technical explanations, code analysis, and architecture pattern recommendations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google AI Search MCP explain how to implement server-side rendering in Next.js 14"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google AI Search MCP
This project implements a Model Context Protocol (MCP) server that provides a comprehensive suite of Google AI-powered search and documentation tools specifically designed to help AI coders overcome LLM knowledge gaps and information limitations.
Implementation notes
Provider selection and credentials are resolved at runtime, so a tool being listed does not prove that its upstream provider is configured or reachable. Treat model-produced comparisons, architecture guidance, and security analysis as material to verify against the cited primary sources rather than deterministic findings.
For a source-linked comparison of the design pressures across this project and six other public MCP implementations, see What building seven MCP servers taught me about production MCP.
Related MCP server: Google Cloud Docs MCP Server
Features
Provides access to Google AI models (Vertex AI and Gemini API) via specialized MCP tools.
Focuses on real-time information retrieval and documentation-based analysis.
Supports web search grounding for current information that LLMs lack.
Configurable model ID, temperature, streaming behavior, max output tokens, and retry settings via environment variables.
Uses streaming API by default for potentially better responsiveness.
Includes basic retry logic for transient API errors.
Minimal safety filters applied (
BLOCK_NONE) to reduce potential blocking (use with caution).
Tools Provided
Core Search & Documentation Tools
answer_query_websearch: Developer-focused natural language queries with automatic technical detection, enhanced search methodology, and comprehensive code formatting using Google AI with real-time search results.explain_topic_with_docs: Streamlined technical explanations with improved debugging scenarios, synthesizing information from official documentation with reduced verbosity and enhanced troubleshooting guidance.get_doc_snippets: Enhanced code snippet retrieval with progressive complexity examples, advanced search patterns, version-specific targeting, and comprehensive context for technical queries from official documentation.generate_project_guidelines: Generates comprehensive structured project guidelines documents based on specified technologies, using web search for current best practices and industry standards.
Advanced Analysis Tools
code_analysis_with_docs: Evidence-based code analysis with standardized citations, severity categorization, and actionable recommendations by comparing code against official documentation best practices.technical_comparison: Produces technology comparisons across requested criteria using current search context where available. Verify quantitative or market claims against the cited primary sources.architecture_pattern_recommendation: Produces architecture options, tradeoffs, and implementation considerations for a described use case. Validate the recommendation against the system's actual constraints before adopting it.
(Note: Input/output schemas for each tool are defined in their respective files within src/tools/ and exposed via the MCP server.)
Prerequisites
Node.js (v18+)
Bun (
npm install -g bun)Google Cloud Project with Billing enabled (if using Vertex AI).
Vertex AI API enabled in the GCP project (if using Vertex AI).
Google Cloud Authentication configured in your environment (Application Default Credentials via
gcloud auth application-default loginis recommended, or a Service Account Key) OR Gemini API key.
Setup & Installation
Clone/Place Project: Ensure the project files are in your desired location.
Install Dependencies:
bun installConfigure Environment:
Create a
.envfile in the project root (copy.env.example).Set the required and optional environment variables as described in
.env.example.Set
AI_PROVIDERto either"vertex"or"gemini".If
AI_PROVIDER="vertex",GOOGLE_CLOUD_PROJECTis required.If
AI_PROVIDER="gemini",GEMINI_API_KEYis required.
Build the Server:
bun run buildThis compiles the TypeScript code to
build/index.js.
Usage (Standalone / NPX)
The package is published to npm and can be run directly with npx:
# Ensure required environment variables are set (e.g., GOOGLE_CLOUD_PROJECT or GEMINI_API_KEY)
bunx google-ai-search-mcpAlternatively, install it globally:
bun install -g google-ai-search-mcp
# Then run:
google-ai-search-mcpNote: Running standalone requires setting necessary environment variables (like GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_LOCATION, GEMINI_API_KEY, authentication credentials if not using ADC) in your shell environment before executing the command.
Docker
Build the local container image:
docker build -t google-ai-search-mcp .Run with the Gemini API provider:
docker run --rm -i \
-e AI_PROVIDER=gemini \
-e GEMINI_API_KEY \
google-ai-search-mcpFor Vertex AI, pass AI_PROVIDER=vertex, GOOGLE_CLOUD_PROJECT, and optionally
GOOGLE_CLOUD_LOCATION. Application Default Credentials must also be available
inside the container, normally through a read-only credential mount. Do not bake
API keys or service-account files into the image.
Running with Cline
Configure MCP Settings: Add/update the configuration in your Cline MCP settings file (e.g.,
.roo/mcp.json). You have two primary ways to configure the command:Option A: Using Node (Direct Path - Recommended for Development)
This method uses
nodeto run the compiled script directly. It's useful during development when you have the code cloned locally.{ "mcpServers": { "google-ai-search-mcp": { "command": "node", "args": [ "/full/path/to/your/google-ai-search-mcp/build/index.js" // Use absolute path or ensure it's relative to where Cline runs node ], "env": { // --- General AI Configuration --- "AI_PROVIDER": "vertex", // "vertex" or "gemini" // --- Required (Conditional) --- "GOOGLE_CLOUD_PROJECT": "YOUR_GCP_PROJECT_ID", // Required if AI_PROVIDER="vertex" // "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY", // Required if AI_PROVIDER="gemini" // --- Optional Model Selection --- "VERTEX_MODEL_ID": "gemini-2.5-pro", // If AI_PROVIDER="vertex" (Example override) "GEMINI_MODEL_ID": "gemini-2.5-pro", // If AI_PROVIDER="gemini" // --- Optional AI Parameters --- "GOOGLE_CLOUD_LOCATION": "us-central1", // Specific to Vertex AI "AI_TEMPERATURE": "0.0", "AI_USE_STREAMING": "true", "AI_MAX_OUTPUT_TOKENS": "65536", // Default from .env.example "AI_MAX_RETRIES": "3", "AI_RETRY_DELAY_MS": "1000", // --- Optional Vertex Authentication --- // "GOOGLE_APPLICATION_CREDENTIALS": "/path/to/your/service-account-key.json" // If using Service Account Key for Vertex }, "disabled": false, "alwaysAllow": [ // Add tool names here if you don't want confirmation prompts // e.g., "answer_query_websearch" ], "timeout": 3600 // Optional: Timeout in seconds } // Add other servers here... } }Important: Ensure the
argspath points correctly to thebuild/index.jsfile. Using an absolute path might be more reliable.
Option B: Using NPX (Requires Package Published to npm)
This method uses
npxto automatically download and run the server package from the npm registry. This is convenient if you don't want to clone the repository.{ "mcpServers": { "google-ai-search-mcp": { "command": "bunx", // Use bunx "args": [ "-y", // Auto-confirm installation "google-ai-search-mcp" // The npm package name ], "env": { // --- General AI Configuration --- "AI_PROVIDER": "vertex", // "vertex" or "gemini" // --- Required (Conditional) --- "GOOGLE_CLOUD_PROJECT": "YOUR_GCP_PROJECT_ID", // Required if AI_PROVIDER="vertex" // "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY", // Required if AI_PROVIDER="gemini" // --- Optional Model Selection --- "VERTEX_MODEL_ID": "gemini-2.5-pro", // If AI_PROVIDER="vertex" (Example override) "GEMINI_MODEL_ID": "gemini-2.5-pro", // If AI_PROVIDER="gemini" // --- Optional AI Parameters --- "GOOGLE_CLOUD_LOCATION": "us-central1", // Specific to Vertex AI "AI_TEMPERATURE": "0.0", "AI_USE_STREAMING": "true", "AI_MAX_OUTPUT_TOKENS": "65536", // Default from .env.example "AI_MAX_RETRIES": "3", "AI_RETRY_DELAY_MS": "1000", // --- Optional Vertex Authentication --- // "GOOGLE_APPLICATION_CREDENTIALS": "/path/to/your/service-account-key.json" // If using Service Account Key for Vertex }, "disabled": false, "alwaysAllow": [ // Add tool names here if you don't want confirmation prompts // e.g., "answer_query_websearch" ], "timeout": 3600 // Optional: Timeout in seconds } // Add other servers here... } }Ensure the environment variables in the
envblock are correctly set, either matching.envor explicitly defined here. Remove comments from the actual JSON file.
Restart/Reload Cline: Cline should detect the configuration change and start the server.
Use Tools: You can now use the comprehensive list of Google AI-powered search and documentation tools via Cline.
Development
Watch Mode:
bun run watchBuild:
bun run buildInspector:
bun run inspector
License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
7 toolsanswer_query_websearchB
Answers a natural language query using the configured Vertex AI model (gemini-2.5-pro) enhanced with Google Search results for up-to-date information. Requires a 'query' string.
Inputs: query (required).
architecture_pattern_recommendationA
Suggests architecture patterns for specific use cases based on industry best practices. Provides implementation examples and considerations for the recommended patterns. Includes diagrams and explanations of pattern benefits and tradeoffs. Uses the configured Vertex AI model (gemini-2.5-pro) with Google Search. Requires 'requirements' and 'tech_stack'.
Inputs: tech_stack (required), requirements (required), industry, existing_architecture.
code_analysis_with_docsA
Analyzes code snippets by comparing them with best practices from official documentation found via web search. Identifies potential bugs, performance issues, and security vulnerabilities. Uses the configured Vertex AI model (gemini-2.5-pro) with Google Search. Requires 'code', 'language', and 'analysis_focus'.
Inputs: code (required), language (required), analysis_focus (required), version, +1 more.
explain_topic_with_docsA
Provides a detailed explanation for a query about a specific software topic by synthesizing information primarily from official documentation found via web search. Focuses on comprehensive answers, context, and adherence to documented details. Uses the configured Vertex AI model (gemini-2.5-pro) with Google Search. Requires 'topic' and 'query'.
Inputs: query (required), topic (required).
generate_project_guidelinesA
Generates a structured project guidelines document (e.g., Markdown) based on a specified list of technologies and versions (tech stack). Uses web search to find the latest official documentation, style guides, and best practices for each component and synthesizes them into actionable rules and recommendations. Uses the configured Vertex AI model (gemini-2.5-pro) with Google Search. Requires 'tech_stack'.
Inputs: tech_stack (required).
get_doc_snippetsB
Provides precise, authoritative code snippets or concise answers for technical queries by searching official documentation. Focuses on delivering exact solutions without unnecessary explanation. Uses the configured Vertex AI model (gemini-2.5-pro) with Google Search. Requires 'topic' and 'query'.
Inputs: query (required), topic (required), version, include_examples.
technical_comparisonA
Compares multiple technologies, frameworks, or libraries based on specific criteria. Provides detailed comparison tables with pros/cons and use cases. Includes version-specific information and compatibility considerations. Uses the configured Vertex AI model (gemini-2.5-pro) with Google Search. Requires 'technologies' and 'criteria'.
Inputs: criteria (required), technologies (required), format, use_case.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Most tools have distinct purposes, but answer_query_websearch and explain_topic_with_docs overlap semantically enough that an agent may hesitate between them. The shared boilerplate descriptions also reduce clarity across several tools.
Several tools follow a verb_object pattern, but code_analysis_with_docs, technical_comparison, and architecture_pattern_recommendation are noun-phrase names. This mixed convention is still readable but not consistently applied.
Seven tools is a well-scoped count for a domain-specific AI search and documentation assistant. Each tool covers a meaningful high-level task without unnecessary redundancy or bloat.
The toolset covers Q&A, documentation explanation, snippets, code analysis, comparisons, architecture planning, and guideline generation. A raw search or retrieval tool is absent, but not a major gap given the AI-assisted focus.
Maintenance
Related MCP Connectors
Versioned documentation registry and semantic search for AI tools and coding assistants.
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…
Provides tools for searching Google Workspace documentation and much more.
Search your knowledge bases from any AI assistant using hybrid RAG.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceProvides curated documentation access via the Gemini API, enabling users to query and interact with technical docs effectively by overcoming context and search limitations.14-
- AlicenseAqualityDmaintenanceEnables AI assistants to search and access Google Cloud Platform documentation in real-time, supporting 20+ GCP services with natural language queries and smart content extraction.4MIT
- AlicenseNot gradedqualityNot gradedmaintenanceCrawls documentation websites and provides semantic search capabilities over the content through vector embeddings, enabling natural language queries of technical documentation.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search and retrieve information from large technical documentation (OpenAPI specs, markdown) via intelligent chunking and semantic search.MIT