MCP Server for Google Search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Your Google Cloud API key for the 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 |
|---|---|
| google_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 clearly distinct purposes: one performs web searches, the other extracts text from a specific URL. There is no overlap or ambiguity.
Both tool names follow the same verb_noun pattern with snake_case (google_search, read_webpage), making them predictable and consistent.
With only two tools, the set is minimal but covers the core search workflow. It avoids unnecessary bloat, though additional search variants could be justified.
The surface covers the basic search-then-read workflow. Missing features like pagination or filtered searches are minor gaps, but the essential path is complete.