MCP Google Server
Provides web search capabilities using Google Custom Search API, allowing querying the entire web or specific sites and returning structured results with title, link, and snippet.
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., "@MCP Google Serversearch for recent advancements in quantum computing"
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.
mcp-google-server A MCP Server for Google Custom Search and Webpage Reading
A Model Context Protocol server that provides web search capabilities using Google Custom Search API and webpage content extraction functionality.
Setup
Getting Google API Key and Search Engine ID
Create a Google Cloud Project:
Go to Google Cloud Console
Create a new project or select an existing one
Enable billing for your project
Enable Custom Search API:
Go to API Library
Search for "Custom Search API"
Click "Enable"
Get API Key:
Go to Credentials
Click "Create Credentials" > "API Key"
Copy your API key
(Optional) Restrict the API key to only Custom Search API
Create Custom Search Engine:
Enter the sites you want to search (use www.google.com for general web search)
Click "Create"
On the next page, click "Customize"
In the settings, enable "Search the entire web"
Copy your Search Engine ID (cx)
Related MCP server: MCP Server for Google Search
Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchFeatures
Search Tool
Perform web searches using Google Custom Search API:
Search the entire web or specific sites
Control number of results (1-10)
Get structured results with title, link, and snippet
Webpage Reader Tool
Extract content from any webpage:
Fetch and parse webpage content
Extract page title and main text
Clean content by removing scripts and styles
Return structured data with title, text, and URL
Installation
Installing via Smithery
To install Google Custom Search Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @adenot/mcp-google-search --client claudeTo use with Claude Desktop, add the server config with your Google API credentials:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"google-search": {
"command": "npx",
"args": [
"-y",
"@adenot/mcp-google-search"
],
"env": {
"SMARTSEARCH_ENDPOINT": "your-endpoint-here",
"SMARTSEARCH_AK": "your-ak-here"
}
}
}
}Usage
Search Tool
{
"name": "search",
"arguments": {
"query": "your search query",
"num": 5 // optional, default is 5, max is 10
}
}Webpage Reader Tool
{
"name": "read_webpage",
"arguments": {
"url": "https://example.com"
}
}Example response from webpage reader:
{
"title": "Example Domain",
"text": "Extracted and cleaned webpage content...",
"url": "https://example.com"
}Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Available Tools
2 toolsread_webpageA
Fetch and extract text content from a webpage
Inputs: url (required).
searchC
Perform a web search query
Inputs: query (required), num.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: read_webpage fetches and extracts text from a specific URL, while search performs a web search query. There is no overlap or ambiguity between these functions, making it easy for an agent to select the appropriate tool.
Both tools follow a consistent verb-based naming pattern (read_webpage, search) with clear, descriptive names. They use snake_case uniformly, and the verbs accurately reflect their actions without deviation.
With only 2 tools, the server feels thin for a 'Google Server' domain, which typically involves broader functionality like email, calendar, or drive operations. While the tools are useful, the count is too low to adequately cover the implied scope, suggesting an incomplete or narrowly focused implementation.
Given the server name 'MCP Google Server', there are significant gaps in coverage, such as missing tools for Google services like Gmail, Calendar, Drive, or authentication. The current tools only handle web-related tasks, making the surface severely incomplete for the expected domain.
Related MCP Connectors
Web search API and MCP server for developers building AI agents.
A Model Context Protocol server for Wix AI tools
MCP server for Google search results via SERP API
Free web search for AI agents. No API key required. Hosted MCP in active development.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to perform web searches using Google's Custom Search API through a standardized interface.147MIT
- FlicenseAqualityCmaintenanceA Model Context Protocol server that provides web search capabilities using Google Custom Search API and webpage content extraction functionality.26 npm2-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform web searches using Google Search API, returning up to 20 search results in JSON format.2Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server providing web search capabilities using Google Custom Search API and webpage content extraction functionality.2MIT