Version 2.0 is here

What is Google Search MCP Server?

An MCP (Model Context Protocol) server that provides Google search capabilities and webpage content analysis tools. It enables AI models to perform Google searches, extract webpage content, and analyze results programmatically.

How to use Google Search MCP Server?

Install Node.js dependencies, build TypeScript, and configure your Google API credentials (GOOGLE_API_KEY, GOOGLE_SEARCH_ENGINE_ID) in the MCP settings file. Start the server with npm run start. Invoke tools like google_search, extract_webpage_content, or extract_multiple_webpages via any MCP client.

Key features of Google Search MCP Server

• Google Custom Search integration with advanced filters and pagination
• Webpage content extraction in Markdown, HTML, or plain text
• Batch analysis of multiple webpages in a single request
• Automatic result categorization and content summarization
• Optimized, human-readable search result responses
• MCP-compliant interface with caching for performance

Use cases of Google Search MCP Server

• Searching the web for current information and returning structured results
• Extracting and summarizing article content from a URL
• Comparing information from multiple sources simultaneously
• Filtering search results by site, language, date, or exact terms
• Paginating through large result sets programmatically

FAQ from Google Search MCP Server

What prerequisites are needed?

Node.js v16 or higher, a Google Cloud Platform account, a Custom Search Engine ID, and a Google API Key.

How do I configure the server?

Set environment variables GOOGLE_API_KEY and GOOGLE_SEARCH_ENGINE_ID, then add the server configuration to your MCP settings file (e.g., cline_mcp_settings.json) with the stdio transport type.

What tools are available?

Three tools: google_search (with optional filters and pagination), extract_webpage_content (single URL), and extract_multiple_webpages (batch URLs). All support auto-approval in MCP settings.

What happens if my API credentials are invalid?

The server returns detailed error messages for missing or invalid API credentials, failed search requests, invalid URLs, and network connectivity issues.

Where does the data live?

Search results and webpage content are fetched live from Google and the target websites. The server caches responses locally to reduce API calls, but no data is stored permanently.