A Model Context Protocol server that provides search capabilities using a Google CSE (custom search engine).
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mcp-google-cse": {
"args": [
"-y",
"@Richard-Weiss/mcp-google-cse"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@Richard-Weiss/mcp-google-cse' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @Richard-Weiss/mcp-google-cse against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in search
Web and local search using Brave Search API
The official MCP server implementation for the Perplexity API Platform
Production ready MCP server with real-time search, extract, map & crawl.
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
MCP Security Weekly
Get CVE alerts and security updates for Mcp Google Cse and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
search_term (string, required): The search term to search for, equaling the query parameter q in the usual Google search.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.Creating a custom search engine is comparatively easy, completely free and can be done in under 5 minutes.
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.
When using uv no specific installation is needed. We will
use uvx to directly run mcp-google-cse.
Alternatively you can install mcp-google-cse via pip:
pip install mcp-google-cse
After installation, you can run it as a script using:
python -m mcp-google-cse