Google Search74 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your API key for Google Search74 API |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | The Google Search74 API endpoint allows users to perform a Google search query and retrieve relevant results based on the provided input. This endpoint is ideal for applications that require automated search capabilities, such as content aggregation, market research, or keyword analysis. ### Key Features: 1. Search Functionality: Execute a search query on Google and retrieve results. 2. Limit Results: Specify the maximum number of results to be returned. 3. Related Keywords: Optionally include related keywords in the response for deeper insights. ### Parameters: - query (string): The search term or keyword to query on Google. For example, "Nike". - limit (integer): The maximum number of search results to return. For example, |
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 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clear and unambiguous.
The single tool name 'search' is a verb, consistent with itself. There is no inconsistency to evaluate.
One tool for a focused search server is reasonable. While it is on the low end of typical tool counts, the scope is narrow and adequately served by a single endpoint.
The tool covers the core search functionality with parameters for query, limit, and related keywords. It is complete for the stated purpose of performing Google searches.