Integrates with Google Custom Search Engine API to enable web searches for fact-checking, research, and content generati...
Created byApr 23, 2025
Google Custom Search Engine MCP Server
A Model Context Protocol server that provides search capabilities using a CSE (custom search engine). This server enables LLMs to provide a regular google search term and returns the found search results.
The tool only returns the results itself and not the content, the tool should be combined with other servers like mcp-server-fetch to extract the content from the search results.
You may also combine it with other tools to enable some kind of "deep search" or tool chaining in general.
The free quota is 100 searches (1 tool call == 1 search) per day, if you don't want to set up billing and this is insufficient for your use case, you should consider using another server.
google_search - Searches the custom search engine using the search term and returns a list of results containing the title, link and snippet of each result.
Environment variables
API_KEY (required): The API key for the custom search engine.
ENGINE_ID (required): The engine ID for the custom search engine.
SERVICE_NAME (required/optional): The name of the service, leave empty if you haven't changed the name (customsearch).
COUNTRY_REGION (optional): Restricts search results to documents originating in a particular country. See Country Parameter Values for valid values.
GEOLOCATION (optional, default "us"): The geolocation of the end-user performing the search. See Geolocation Parameter Values for valid values.
RESULT_LANGUAGE (optional, default "lang_en"): The language of the search results. See CSE Query parameters, lr for valid values.
RESULT_NUM (optional, default 10): The number of search results to return. Range from 1-10.
CSE Setup
Creating a custom search engine is comparatively easy, completely free and can be done in under 5 minutes.
Create a new search engine and give it any name, the name doesn't correlate to SERVICE_NAME.
Select "Search the entire web" if you want a normal Google Search experience.
Click on "Create" and copy the engine id from the js code, or hit customize and get it from the overview.
You can optionally customize the search engine to your liking.
With the default quota, you will get 100 searches per day for free. A tool call only costs 1 search, even if you get 10 results for example.
Installation
Using uv (recommended)
When using `uv` no specific installation is needed. We will
use `uvx` to directly run mcp-google-cse.
Using PIP
Alternatively you can install mcp-google-cse via pip:
After installation, you can run it as a script using:
Installing via Smithery
To install Google Custom Search Engine for Claude Desktop automatically via Smithery:
Configuration
Configure for Claude app
Add to your claude_desktop_config.json:
Using uvx (use this if you don't know which one to choose)
Using pip installation
Running locally
Example result
google_search("What is MCP after:2024-11-01")
Result:
Note: Code block was split into 2 parts due to size limits.
Google Custom Search Engine MCP Server
A Model Context Protocol server that provides search capabilities using a CSE (custom search engine). This server enables LLMs to provide a regular google search term and returns the found search results.
The tool only returns the results itself and not the content, the tool should be combined with other servers like mcp-server-fetch to extract the content from the search results.
You may also combine it with other tools to enable some kind of "deep search" or tool chaining in general.
The free quota is 100 searches (1 tool call == 1 search) per day, if you don't want to set up billing and this is insufficient for your use case, you should consider using another server.
google_search - Searches the custom search engine using the search term and returns a list of results containing the title, link and snippet of each result.
Environment variables
API_KEY (required): The API key for the custom search engine.
ENGINE_ID (required): The engine ID for the custom search engine.
SERVICE_NAME (required/optional): The name of the service, leave empty if you haven't changed the name (customsearch).
COUNTRY_REGION (optional): Restricts search results to documents originating in a particular country. See Country Parameter Values for valid values.
GEOLOCATION (optional, default "us"): The geolocation of the end-user performing the search. See Geolocation Parameter Values for valid values.
RESULT_LANGUAGE (optional, default "lang_en"): The language of the search results. See CSE Query parameters, lr for valid values.
RESULT_NUM (optional, default 10): The number of search results to return. Range from 1-10.
CSE Setup
Creating a custom search engine is comparatively easy, completely free and can be done in under 5 minutes.