MCP Google Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Your Google API key for Custom Search API | |
| GOOGLE_SEARCH_ENGINE_ID | Yes | Your Google Custom Search Engine ID (cx) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Perform a web search query |
| read_webpageA | Fetch and extract text content from a webpage |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one fetches content from a specific URL, the other performs web searches. There is no overlap or ambiguity.
The naming pattern is inconsistent: 'read_webpage' uses verb_noun with an underscore, while 'search' is a single verb without a noun or underscore. This lack of uniformity could confuse agents.
With only 2 tools, the server is minimal but still covers two core web operations. The count is at the low end of what's reasonable for a focused server, but not necessarily inappropriate.
The set provides basic web search and page reading, which covers common use cases. However, it lacks features like filtering search results, handling pagination, or extracting specific elements, leaving minor gaps.