Listed from the MCP registry; nobody on Odel publishes it.
MCP server for Google Custom Search: web and image search via a Programmable Search Engine.
Runs on your machine from its package; the steps are below.

At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y mcp-google-custom-search
MCP client config
{
"mcpServers": {
"google-custom-search-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-google-custom-search"
]
}
}
}English | Русский
A1 Google Custom Search MCP lets an AI app search the web and images in plain language through your Programmable Search Engine. Ask for pages, narrow by language, country, date or site, page through results and pull image files with thumbnails.
It uses the Google Custom Search JSON API with your Google Cloud API key. You decide what the engine covers — a handful of sites or the entire web — and the server makes the limits of the JSON API explicit instead of implying that every search task is possible.
X-Goog-Api-Key header and never appears in a URL.Start with a read-only question:
Find recent articles about passkey adoption from the last month and summarize the top three results.
Connect the server · Explore use cases · Open technical documentation
You: Find recent articles about passkey adoption, English only, from the last month.
Assistant: Runs one search through your engine and shows each result's title, link and snippet. Nothing changes — every tool is read-only.
You: Show the next page.
Assistant: Continues from the
next_startcursor and shows results 11–20 of the same query.You: Now find large press photos on the same topic.
Assistant: Switches to image search and returns image files with their dimensions, thumbnails and the pages that host them.
You need Node.js 20+, a Google Cloud API key with the Custom Search API enabled and a Programmable Search Engine id (cx).
In the app: open Settings → MCP servers, select Add server, choose STDIO, enter the command npx -y mcp-google-custom-search@latest and environment variables GOOGLE_CUSTOM_SEARCH_API_KEY, GOOGLE_CUSTOM_SEARCH_ENGINE_ID, then select Save and Restart.
From the command line:
codex mcp add google-custom-search \
--env GOOGLE_CUSTOM_SEARCH_API_KEY=your_api_key \
--env GOOGLE_CUSTOM_SEARCH_ENGINE_ID=your_engine_id \
-- npx -y mcp-google-custom-search@latest
codex mcp list
claude mcp add \
--env GOOGLE_CUSTOM_SEARCH_API_KEY=your_api_key \
--env GOOGLE_CUSTOM_SEARCH_ENGINE_ID=your_engine_id \
--transport stdio --scope user google-custom-search \
-- npx -y mcp-google-custom-search@latest
claude mcp list
The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
{
"mcpServers": {
"google-custom-search": {
"command": "npx",
"args": ["-y", "mcp-google-custom-search@latest"],
"env": {
"GOOGLE_CUSTOM_SEARCH_API_KEY": "your_api_key",
"GOOGLE_CUSTOM_SEARCH_ENGINE_ID": "your_engine_id"
}
}
}
}
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-custom-search": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-custom-search@latest"],
"env": {
"GOOGLE_CUSTOM_SEARCH_API_KEY": "your_api_key",
"GOOGLE_CUSTOM_SEARCH_ENGINE_ID": "your_engine_id"
}
}
}
}
Run MCP: Open User Configuration and add:
{
"servers": {
"google-custom-search": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-custom-search@latest"],
"env": {
"GOOGLE_CUSTOM_SEARCH_API_KEY": "${input:custom_search_api_key}",
"GOOGLE_CUSTOM_SEARCH_ENGINE_ID": "${input:custom_search_engine_id}"
}
}
},
"inputs": [
{ "type": "promptString", "id": "custom_search_api_key", "description": "Google Cloud API key", "password": true },
{ "type": "promptString", "id": "custom_search_engine_id", "description": "Programmable Search Engine id (cx)" }
]
}
Check it with MCP: List Servers.
docs.python.org — or everywhere except a site you distrust.fields to trim the response, lowRange/highRange, hq.pagemap.cx id — the configured default or a per-call engine_id. The engine's configuration decides coverage: a list of specific sites, or the entire web when "Search the entire web" is enabled.next_start/previous_start cursors for paging. total_results is Google's estimate and can shrink while paging.start + num - 1 must stay ≤ 100). The server rejects a wider window before the request — the API would answer 400 after burning a quota unit.400.A corrected_query in the response is a spelling suggestion only — the results are still for the original query. And this is Programmable Search, not Google Search Console: the API cannot report how your own site is indexed or ranked.
| Operation | What happens | Confirmation boundary |
|---|---|---|
Web search (search) | Reads search results from your engine | No change |
Image search (search_images) | Reads image results from your engine | No change |
Raw API request (raw_request) | GET against any Custom Search API path | No change — the API has no write endpoint |
Every tool carries the read-only annotation, the escape hatch included. The Custom Search JSON API is a single GET endpoint with no writes, so the only thing a call spends is a unit of your daily quota.
Google Custom Search authenticates with an API key; no OAuth and no scopes are involved.
cx). Enable Search the entire web for open-web search and Image search for the image tool.Treat the API key as a password. The server sends it in the X-Goog-Api-Key header, never in a URL, so logged or echoed URLs cannot leak it.
| Variable | Required | Description |
|---|---|---|
GOOGLE_CUSTOM_SEARCH_API_KEY | Yes | Google Cloud API key with the Custom Search API enabled. Secret. |
GOOGLE_CUSTOM_SEARCH_ENGINE_ID | Recommended | Default Programmable Search Engine id (cx); tools accept a per-call engine_id override. |
GOOGLE_CUSTOM_SEARCH_API_BASE | No | Custom Search API base URL override. |
GOOGLE_CUSTOM_SEARCH_TIMEOUT_MS | No | Per-request timeout; default 30000 ms. |
GOOGLE_CUSTOM_SEARCH_MAX_RETRIES | No | Transient-error retries (429/5xx/network); default 3. |
Without credentials the server still starts and completes the MCP handshake; the first tool call explains exactly which variables to set. The one malformed setup is an engine id without an API key — the key cannot be supplied per call, so both must be set together.
#; a value from your request can appear in it if the error text contains it. Set ASKADS_TELEMETRY=0 to opt out.429, the server backs off honoring Retry-After; because the whole API is idempotent GETs, 5xx and network errors are retried too, while 400/403 fail fast.Found a bug or need a scenario? Create an issue or write in Telegram.
You made it to the end!