by fabien-desablens
Integrate Google Web Search API with auto key rotation, quota control, advanced filters, and site-specific queries for p
Searches the web using Google Custom Search API and extracts clean content from any webpage. Requires Google API key and search engine ID setup.
Google Search is a community-built MCP server published by fabien-desablens that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate Google Web Search API with auto key rotation, quota control, advanced filters, and site-specific queries for p It is categorized under search web.
You can install Google Search in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Google Search is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
Google Search has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Google Search for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Google Search surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated Google Search against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Google Search is the kind of server we cite when onboarding engineers to host + tool permissions.
Google Search is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Google Search benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Google Search reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Google Search is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Google Search against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 74
A Model Context Protocol (MCP) server that provides Google Search functionality with automatic API key rotation and intelligent quota management.
<a href="https://glama.ai/mcp/servers/@Fabien-desablens/google-search-mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@Fabien-desablens/google-search-mcp/badge" alt="Google Search Server MCP server" /> </a># Install the package globally
npm install -g @kyaniiii/google-search-mcp
# Run interactive setup
google-search-setup
This will:
git clone https://github.com/Fabien-desablens/google-search-mcp.git
cd google-search-mcp
npm install
npm run build
npm run setup
# Remove the package
npm uninstall -g @kyaniiii/google-search-mcp
# Remove from Claude Code
claude mcp remove google-search
# Remove configuration file (if desired)
npm run clean
Note: Configuration file (~/.google-search-mcp.json) is always preserved during updates and uninstallation to protect your API keys. Use npm run clean only if you want to completely remove your configuration.
The setup tool creates a global configuration file at:
%USERPROFILE%\.google-search-mcp.json~/.google-search-mcp.jsonThis file contains:
{
"keys": [
{
"id": "key_1",
"apiKey": "AIzaSy...",
"searchEngineId": "abc123...",
"dailyUsage": 45,
"dailyLimit": 100,
"lastReset": "2024-07-30",
"isActive": true
}
],
"lastUpdated": "2024-07-30T15:30:00Z",
"version": "1.0.0"
}
⚠️ Important: If you manually edit the configuration file (~/.google-search-mcp.json), you must restart Claude Desktop for the changes to take effect.
* to search the entire webAfter running the setup, the server is automatically configured in Claude Code. You can immediately use it:
User: "Search for latest AI news from this week"
Claude: I'll search for the latest AI news using Google Search...
The server exposes a google_search tool with these parameters:
query (string): Search querynum (number): Number of results (1-10, default: 5)start (number): Starting index for resultssafe (string): SafeSearch level ('off', 'active')lr (string): Language restriction (e.g., 'lang_en', 'lang_fr')gl (string): Geolocation (country code: 'us', 'fr', 'uk')dateRestrict (string): Time period ('d1', 'w1', 'm1', 'y1')fileType (string): File type filter ('pdf', 'doc', 'ppt')siteSearch (string): Search specific sitesiteSearchFilter (string): Include ('i') or exclude ('e') sitecr (string): Country restriction ('countryUS', 'countryFR')exactTerms (string): Exact phrase to includeexcludeTerms (string): Terms to excludeorTerms (string): Alternative terms (OR search)sort (string): Sort by date ('date')searchType (string): Search type ('image' for image search){
"query": "artificial intelligence news"
}
{
"query": "machine learning",
"num": 10,
"lr": "lang_en",
"gl": "us",
"dateRestrict": "m1",
"fileType": "pdf"
}
{
"query": "typescript tutorial",
"siteSearch": "stackoverflow.com",
"siteSearchFilter": "i"
}
The server provides real-time quota information in each response:
{
"results": [...],
"metadata": {
"quotaStatus": {
"totalUsed": 15,
"totalLimit": 300,
"keysStatus": [
{
"id": "key_1",
"used": 15,
"limit": 100,
"remaining": 85,
"active": true
}
]
}
}
}
The server gracefully handles various error scenarios:
# Development mode with auto-reload
npm run dev
# Build for production
npm run build
# Start server
npm start
# Setup configuration
npm run setup
google-search-mcp/
├── src/
│ ├── index.ts # Entry point
│ ├── server.ts # MCP server setup
│ ├── config.ts # Configuration wrapper
│ ├── global-config.ts # Global config manager
│ └── tools/
│ └── search.ts # Search implementation
├── build/ # Compiled JavaScript
├── setup.js # Interactive setup tool
└── package.json
Contributions are welcome! Please:
MIT License - see LICENSE file for details
For issues, questions, or contributions, please visit: https://github.com/Fabien-desablens/google-search-mcp
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.