Google Search MCP
Performs Google searches and extracts results while bypassing anti-bot mechanisms, providing real-time search capabilities with support for multiple languages and regions.
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., "@Google Search MCPfind recent developments 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.
Google Search MCP
Model Context Protocol server for google search. A Playwright-based Model Context Protocol (MCP) tool that bypasses search engine anti-bot mechanisms, performs Google searches, and extracts results, providing real-time search capabilities for AI assistants like Claude and Cursor.
Features
Anti-Bot Bypass: Uses browser fingerprint spoofing and real user behavior simulation to avoid detection
Automatic CAPTCHA Handling: Switches to headed mode when encountering CAPTCHAs, allowing users to complete verification
State Persistence: Saves browser session state to reduce the need for repeated verification
Adaptability: Uses multiple selector combinations to adapt to changes in Google search pages
MCP Integration: Implements the Model Context Protocol for easy integration with AI assistants
Multi-language Support: Supports search results in different languages and regions
Related MCP server: Playread
Using with Cursor
Installation - Globally
Run the MCP server using npx:
npx -y @mcp-server/google-search-mcp@latestIn your Cursor IDE
Go to
Cursor Settings>MCPClick
+ Add New MCP ServerFill in the form:
Name:
google-search(or any name you prefer)Type:
commandCommand:
npx -y @mcp-server/google-search-mcp@latest
Installation - Project-specific
Add an .cursor/mcp.json file to your project:
{
"mcpServers": {
"google-search": {
"command": "npx",
"args": [
"-y",
"@mcp-server/google-search-mcp@latest"
]
}
}
}Development
yarn installBuild the project
yarn buildUsage
Running as an MCP Server
yarn startUsing with MCP Inspector
To debug the server, you can use the MCP Inspector:
# First build the project
yarn build
# Start the MCP Inspector and server
npx @modelcontextprotocol/inspector node dist/index.jsParameters
The search tool accepts the following parameters:
query(required): Search query stringlimit(optional): Number of search results to return, default is 10timeout(optional): Search operation timeout in milliseconds, default is 60000language(optional): Language for search results, e.g., zh-CN, en-US, default is zh-CNregion(optional): Region for search results, e.g., cn, com, co.jp, default is cn
How It Works
The tool uses Playwright to control a Chromium browser to perform Google searches
It avoids bot detection through browser fingerprint spoofing and real user behavior simulation
When encountering CAPTCHA verification, it automatically switches to headed mode for user completion
It extracts search results and returns them in a structured format
It saves browser state for reuse in subsequent searches
Advanced Configuration
Browser State File
By default, the browser state is saved in the .google-search-browser-state.json file in the user's home directory. You can modify this path through parameters.
Language and Region Settings
You can specify the language and region for search results through parameters:
// English (US) search results
"language": "en-US", "region": "com"
// Japanese search results
"language": "ja-JP", "region": "co.jp"
// Chinese (Simplified) search results
"language": "zh-CN", "region": "cn"Notes
On first use, if you encounter CAPTCHA verification, the system will automatically switch to headed mode for you to complete the verification
After verification, the system will save the state file, making subsequent searches smoother
Overly frequent search requests may trigger Google's rate limiting mechanisms
This tool is for learning and research purposes only, please comply with Google's terms of service
License
MIT
Disclaimer
This tool is for learning and research purposes only. When using this tool to access Google or other search engines, please comply with relevant terms of service and legal regulations. The author is not responsible for any issues resulting from the use of this tool.
Available Tools
1 toolsearchD
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | 搜索查询字符串 | |
| limit | No | 返回的搜索结果数量,默认为10 | |
| timeout | No | 搜索操作的超时时间(毫秒),默认为60000 | |
| language | No | 搜索结果的语言,例如 zh-CN, en-US 等,默认为 zh-CN | |
| region | No | 搜索结果的地区,例如 cn, com, co.jp 等,默认为 cn |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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
- First observed
search
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search' has a distinct and clear purpose by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'search' follows a simple, clear verb pattern.
One tool is too few for a server named 'Google Search MCP', which suggests a domain that might benefit from more functionality (e.g., advanced search options, filtering, or result management). A single tool feels thin and under-scoped for such a purpose.
The server is severely incomplete for a search domain. With only a basic 'search' tool and no description, it lacks obvious features like pagination, filtering by date or type, or handling search results, which are essential for effective search operations.
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
Search Google straight from your AI agent. Web results, images, videos, news, products, scholarly ar
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
Scrape Google search results with SERP data, ads, and knowledge panels
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform real-time Google searches with anti-bot protection. Bypasses search engine restrictions using advanced browser automation to extract search results locally without requiring paid API services.7MIT
- AlicenseNot gradedqualityFmaintenanceEnables Google search automation and web content extraction using Playwright. Performs Google searches and fetches main content from web pages, returning structured results in JSON format.25MIT
- AlicenseBqualityDmaintenanceExposes Playwright-powered automation tools to AI assistants for navigating web pages, interacting with elements, and extracting structured data. It features specialized scrapers for Indeed and Google Search, along with stealth mode to bypass bot detection.30ISC
- AlicenseNot gradedqualityFmaintenanceProvides real-time Google search capabilities to AI assistants like Claude, bypassing anti-scraping mechanisms.14621MIT
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/modelcontextprotocol-servers/google-search-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server