Enhanced Google Search MCP
The Enhanced Google Search MCP server provides advanced, anonymized Google web search capabilities with comprehensive customization options.
Core Features:
Advanced search queries with support for complex syntax, quotes, operators, and filters
Configurable results with 1-10 result limits, language/region settings, safe search levels ('off', 'moderate', 'strict'), and time range filtering ('hour', 'day', 'week', 'month', 'year')
Enhanced anonymization using rotating user agents, dynamic headers, and randomized session IDs
Anti-detection capabilities with random delays, parameter variation, and comprehensive error handling
Robust reliability featuring smart retry logic, automatic rate limit handling, and multiple HTML parsing strategies
MCP integration compatible with Claude Desktop and other MCP clients
Comprehensive testing with validation suite for real-world scenarios
Provides enhanced Google search capabilities with advanced query support, configurable results filtering by language/region/time, and anti-detection features for web scraping
Click on "Install 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., "@Enhanced Google Search MCPfind recent AI research papers from the past month"
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.
Enhanced Google Search MCP Server
ā ļø EXPERIMENTAL PROJECT - USE AT YOUR OWN RISK
This is an experimental Google search MCP server that uses web scraping techniques. Please be aware of the following:
Rate Limiting: Google may block or rate-limit requests from this server
Reliability: Search results may be inconsistent due to Google's anti-scraping measures
š RECOMMENDED ALTERNATIVES
For production use, we strongly recommend using official search APIs or established MCP servers:
DuckDuckGo MCP Servers: More reliable and ToS-compliant alternatives
Bing Search API: Microsoft's official search API with MCP integration
Google Custom Search API: Google's official search API (requires API key)
SearXNG MCP: Privacy-focused meta-search engine integration
Use this experimental server only if you understand the risks and limitations.
A powerful Model Context Protocol (MCP) server that provides enhanced Google search capabilities with advanced anonymization and anti-detection features.
Features
š Enhanced Search Capabilities
Advanced Query Support: Handle complex search queries with quotes, operators, and filters
Configurable Results: Limit results (1-10), set language, region, safe search, and time range
Multiple Parsing Strategies: Robust result extraction with fallback mechanisms
š”ļø Advanced Anonymization
Realistic Browser Fingerprinting: Rotating user agents that mimic real browsers (Chrome, Firefox, Safari, Edge)
Dynamic Headers: Randomized Accept-Language, Accept-Encoding, and security headers
Session Randomization: Unique session IDs and request fingerprints
Request Timing: Random delays to avoid detection patterns
š Reliability Features
Smart Retry Logic: Exponential backoff with jitter for failed requests
Rate Limit Handling: Automatic detection and graceful handling of rate limits
Error Recovery: Comprehensive error handling with user-friendly messages
Timeout Management: Configurable timeouts with proper error reporting
š§ Technical Improvements
Multiple Result Selectors: Adapts to Google's changing HTML structure
URL Cleaning: Proper handling of Google's redirect URLs
Content Validation: Ensures all results have valid URLs and content
Comprehensive Logging: Detailed logging for debugging and monitoring
Related MCP server: G-Search MCP
Installation
Installing via Smithery
To install google-search-mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @kongyo2/google-search-mcp --client claudeManual Installation
npm installUsage
Development Mode
Start the server in development mode with interactive CLI:
npm run devProduction Mode
Start the server for production use:
npm run startTesting
Run the comprehensive test suite:
npm run testFor continuous testing during development:
npm run test:watchMCP Tool: search
The server provides a single, powerful search tool with the following parameters:
Parameters
query(required): Search query to executelimit(optional): Maximum number of results (1-10, default: 5)language(optional): Language code (e.g., 'en', 'es', 'fr', 'de', 'ja')region(optional): Region code (e.g., 'us', 'uk', 'ca', 'au')safeSearch(optional): Filter level ('off', 'moderate', 'strict')timeRange(optional): Time filter ('hour', 'day', 'week', 'month', 'year')
Example Usage
{
"name": "search",
"arguments": {
"query": "Model Context Protocol MCP",
"limit": 5,
"language": "en",
"region": "us",
"safeSearch": "moderate",
"timeRange": "week"
}
}Configuration with Claude Desktop
Add this configuration to your Claude Desktop MCP settings:
{
"mcpServers": {
"enhanced-google-search": {
"command": "npx",
"args": ["tsx", "/path/to/your/project/src/server.ts"]
}
}
}Architecture
Core Components
UserAgentGenerator: Creates realistic browser fingerprints
RequestAnonymizer: Handles request anonymization and timing
SearchParameterBuilder: Constructs optimized search parameters
ResultParser: Robust HTML parsing with multiple strategies
Anti-Detection Features
Browser Fingerprint Rotation: Cycles through realistic user agents
Header Randomization: Varies request headers to avoid patterns
Timing Randomization: Adds random delays between requests
Session Management: Generates unique session identifiers
Parameter Variation: Adds random search parameters
Error Handling
The server provides comprehensive error handling for:
Rate limiting by Google
Network timeouts and connectivity issues
Access denied/blocked requests
Invalid or empty responses
Parsing failures with fallback strategies
Development
Project Structure
src/
āāā server.ts # Main MCP server implementation
āāā search.ts # Enhanced search functionality
āāā search.test.ts # Comprehensive test suite
āāā types.ts # TypeScript type definitionsCode Quality
The project includes:
TypeScript: Full type safety and IntelliSense support
ESLint: Code linting with TypeScript rules
Prettier: Consistent code formatting
Vitest: Fast and reliable testing framework
Scripts
npm run build: Compile TypeScript to JavaScriptnpm run start: Start the server in production modenpm run dev: Start in development mode with CLInpm run test: Run the test suitenpm run test:watch: Run tests in watch modenpm run lint: Check code quality and typesnpm run format: Format code with Prettier
Testing
The test suite covers:
Basic search functionality
Parameter validation and handling
Language and region filtering
Safe search and time range filters
Complex query handling
Error scenarios and edge cases
URL validation and result formatting
All tests use real Google search requests to ensure functionality works in practice.
Contributing
Fork the repository
Create a feature branch
Make your changes with tests
Run
npm run lintandnpm run testSubmit a pull request
License
MIT License - see LICENSE file for details.
Available Tools
1 toolsearchARead-only
Search the web using Google with enhanced anonymization and anti-detection features. Supports advanced filtering options.
| Name | Required | Description | Default |
|---|---|---|---|
| language | No | Language code for results (e.g., 'en', 'es', 'fr', 'de', 'ja') | |
| limit | No | Maximum number of results to return (1-10, default: 5) | |
| query | Yes | Search query to execute | |
| region | No | Region code for localized results (e.g., 'us', 'uk', 'ca', 'au') | |
| safeSearch | No | Safe search filter level | |
| timeRange | No | Time range filter for recent results |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true and openWorldHint=true, covering safety and scope. The description adds valuable context beyond this by disclosing 'enhanced anonymization and anti-detection features,' which are behavioral traits not captured in annotations, though it lacks details on rate limits or specific anonymization methods.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose and key features without waste. Every word contributes to understanding, making it appropriately sized and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (6 parameters, no output schema), the description is minimal but adequate with annotations covering safety. It lacks details on output format or error handling, making it incomplete for full agent guidance but passable as a basic search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all 6 parameters. The description adds no specific meaning beyond the schema, only vaguely referencing 'advanced filtering options' without detailing which parameters or how they work, meeting the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose as 'Search the web using Google' with a specific verb ('Search') and resource ('the web'), and mentions enhanced features like anonymization and anti-detection. However, since there are no sibling tools, it cannot differentiate from alternatives, preventing a perfect score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It mentions 'advanced filtering options' but does not specify contexts or limitations, leaving usage unclear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
search
TDQS
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is clearly defined as web searching with specific features.
Since there is only one tool named 'search', it inherently follows a consistent pattern with itself. There are no deviations or mixing of conventions to evaluate, making it perfectly consistent.
A single tool for an 'Enhanced Google Search MCP' feels too minimal for the apparent scope, as web searching often involves related operations like refining queries or handling results. This thin surface may limit agent capabilities in this domain.
The tool surface is severely incomplete for web searching; it only offers a basic search function without supporting operations such as filtering results, pagination, or accessing cached pages. This creates significant gaps that could lead to agent failures in complex tasks.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server for Google search results via SERP API
All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP (Model Context Protocol) server that provides Google search capabilities and webpage content analysis tools. This server enables AI models to perform Google searches and analyze webpage content programmatically.27256ISC
- AlicenseBqualityFmaintenanceA powerful MCP server that enables parallel Google searching with multiple keywords simultaneously, providing structured results while handling CAPTCHAs and simulating user browsing patterns.198272MIT
- AlicenseAqualityCmaintenanceAn MCP server that provides Google Search functionality with automatic API key rotation and intelligent quota management, enabling natural language search queries with advanced filtering options.1241MIT
- FlicenseAqualityDmaintenanceMCP server that provides automated Google search capabilities, allowing query execution, result limiting, and optional related keywords retrieval.1-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kongyo2/Google-Search-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server