Google Search MCP Server
Related Servers
Alternatives to Google Search MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenancePerforms comprehensive web searches by combining Google search with advanced content extraction using Mozilla's Readability algorithm.22 npm2MIT
- FlicenseBqualityDmaintenanceEnables web searching and content scraping through Google Custom Search API. Provides tools to search the internet, extract webpage content, and automatically scrape search results for comprehensive information gathering.3-
- AlicenseNot gradedqualityDmaintenanceEnables web searching through Google, DuckDuckGo, and Bing using a headless Chrome browser, returning structured results with titles, URLs, and snippets. Also supports fetching and extracting text content from any webpage.14MIT
- AlicenseBqualityDmaintenanceEnables web search through DuckDuckGo and webpage content fetching with intelligent text extraction. Features built-in rate limiting and LLM-optimized result formatting for seamless integration with language models.2MIT
- AlicenseNot gradedqualityCmaintenanceProvides web search with content extraction, YouTube subtitles, and optional LLM summarization for AI assistants.Apache 2.0
- FlicenseBqualityDmaintenanceEnables web search and content extraction using Google's search engine, with customizable parameters for result count, content type, time range, and domain filtering.2-
TDQS
Scored across 3 tools
The tools have overlapping purposes that could cause misselection. Both deep_search and deep_search_news perform similar comprehensive searches with full content extraction, differing mainly in search type (general vs. news), while google_search is a simpler alternative. An agent might struggle to choose between deep_search and deep_search_news for news-related queries, as their descriptions suggest functional overlap.
The tool names follow a consistent snake_case pattern throughout, with clear and descriptive verbs (deep_search, deep_search_news, google_search). The naming is predictable and readable, making it easy for an agent to understand the tool set's structure without confusion.
With only 3 tools, the server feels thin for a Google Search domain, which typically involves more varied operations like filtering, pagination, or specialized searches (e.g., by date or region). While the tools cover basic search needs, the count is borderline for comprehensive search functionality, potentially limiting agent capabilities.
There are significant gaps in the tool surface for a Google Search server. Missing operations include advanced filtering options, image or video search handling beyond basic mentions, pagination support, and error handling tools. The server focuses on content retrieval but lacks tools for refining or managing search results, which could lead to agent failures in complex tasks.