Google Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CSE_ID | Yes | Your Custom Search Engine (CSE) ID | |
| GOOGLE_API_KEY | Yes | Your Google API key |
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": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_searchB | Performs a Google Programmable Search (CSE) query. Returns a JSON list of results, each containing a URL, title, snippet, and pagemap. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Web Search | Answers questions and finds information using Google Search. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined and distinct.
The single tool name 'google_search' follows a clear and descriptive pattern (service_action), consistent with common conventions.
One tool is minimal for a search server. While it serves the basic purpose, a more comprehensive set (e.g., configuration, metadata) would be expected for a full-featured server.
The server only provides search functionality, missing obvious operations like managing search engines or retrieving result details. This gap limits the agent's ability to perform complete workflows.