Google Researcher MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CUSTOM_SEARCH_ID | Yes | Google Custom Search Engine ID (cx parameter) | |
| GOOGLE_CUSTOM_SEARCH_API_KEY | Yes | Google Custom Search API key from Google Cloud Console |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_searchA | Search the web using Google Custom Search API. Returns a list of URLs with titles and snippets. When to use:
When to use search_and_scrape instead:
Caching: Results cached for 30 minutes. |
| scrape_pageA | Extract text content from a URL. Automatically handles: web pages (static + JavaScript-rendered), YouTube videos (extracts transcript), and documents (PDF, DOCX, PPTX). When to use:
When to use search_and_scrape instead:
Content size control:
Preview mode benefits:
Caching: Results cached for 1 hour. |
| search_and_scrapeA | Search Google AND retrieve content from top results in one call. Returns combined, deduplicated content with source attribution. When to use:
When to use other tools instead:
Content size control:
Caching: Search results cached for 30 minutes, scraped pages for 1 hour. |
| google_image_searchA | Search for images using Google Custom Search API. Returns image URLs, thumbnails, dimensions, and source page URLs. When to use:
Key parameters:
Caching: Results cached for 30 minutes. |
| google_news_searchA | Search for recent news articles with freshness filters and date sorting. When to use:
When to use scrape_page instead:
Key parameters:
Caching: Results cached for 30 minutes. |
| sequential_searchA | Track multi-step research progress across multiple API calls. When to use:
When to use search_and_scrape instead:
Key principle: You do the reasoning; this tool tracks state. It persists across API calls so you can build on previous steps. Example flow:
|
| academic_searchA | Search academic papers using Google Custom Search API. When to use:
Features:
Academic sources: arXiv, PubMed, IEEE, Nature, Springer, ResearchGate, JSTOR, and more. Caching: Results cached for 30 minutes. |
| patent_searchA | Search patents using Google Custom Search API (site:patents.google.com). When to use:
Features:
Important limitation: Google Custom Search doesn't index ALL patents. For comprehensive company patent research:
Search types:
Caching: Results cached for 30 minutes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| comprehensive-research | |
| fact-check | |
| summarize-url | |
| news-briefing | |
| patent-portfolio-analysis | |
| competitive-analysis | |
| literature-review | |
| technical-deep-dive | |
| due-diligence-background |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent-searches | List of recent search queries executed on this server |
| server-config | Current server configuration (non-sensitive values) |
| cache-stats | Cache performance metrics and current state |
| event-stats | Event store performance metrics |
| tool-stats | Per-tool execution metrics including call counts, success rates, and latency |
| current-research-session | Current sequential search research session state |
| resource-cache-stats | Statistics for resource_link content cache |
TDQS
Scored across 8 tools
Each tool targets a distinct type of content or action: academic papers, images, news, general web, patents, page scraping, combined search+scrape, and progress tracking. Their purposes are clearly differentiated by name and description, leaving little ambiguity.
Most tools follow a descriptive pattern (e.g., academic_search, google_news_search, patent_search), but there are minor inconsistencies: scrape_page and search_and_scrape break the 'type_search' pattern, and sequential_search uses an adjective. Overall, names are clear and mostly consistent.
With 8 tools, the server is well-scoped for a research assistant. It covers essential search types and content extraction without being overwhelming. Each tool adds distinct value, and the count feels appropriate for the domain.
The tool set covers the major facets of web research: various search verticals (web, academic, news, images, patents), page scraping, combined search+scrape, and even a research progress tracker. There are no obvious gaps; it provides a comprehensive workflow.