Skip to main content
Glama
jspv

Google Search MCP Server

by jspv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_CXYesYour Custom Search Engine ID
GOOGLE_API_KEYYesYour Google Custom Search 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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Google Programmable Search (CSE) via MCP.

Parameters:
    q: Query string. Trimmed; required.
    num: Number of results to return (1..10; clamped).
    start: 1-based index for pagination start (clamped to >=1).
    siteSearch: Limit results to a site (or domain) per CSE rules.
    siteSearchFilter: "i" to include or "e" to exclude `siteSearch`.
    safe: SafeSearch level: "off" or "active".
    gl: Geolocation/country code.
    hl: UI language.
    lr: Language restrict (e.g., "lang_en").
    useSiteRestrict: Use the siterestrict endpoint variant.
    dateRestrict: Time filter (e.g., "d7", "m3", "y1").
    exactTerms, orTerms, excludeTerms: Query modifiers.
    cxOverride: Override the configured CSE ID (avoid echoing to clients).
    lean_fields: If True, request a smaller response via fields projection.

Returns:
    A dict with keys: provider, query (sanitized), searchInfo, nextPage,
    latency_ms, results (normalized), raw (subset), trace (q hash).

Raises:
    ValueError: For invalid parameter values (e.g., unsupported safe).
    RuntimeError: For Google API errors or network failures.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single 'search' tool has a clearly defined and distinct purpose that cannot be mistaken for any other tool in this server.

Naming Consistency5/5

The naming is trivially consistent as there is only one tool named 'search'. This follows a simple verb pattern and there are no other tools to create inconsistency or mixed conventions.

Tool Count2/5

A single tool is too few for a server named 'Google Search MCP Server', which suggests broader search functionality. While the tool is feature-rich, the server lacks complementary tools like image_search, news_search, or advanced filtering tools that would make the set more complete and appropriate for the domain.

Completeness2/5

The server is severely incomplete for a Google Search domain. It only provides a general web search tool, missing obvious gaps such as image search, video search, news search, or specialized search types that agents would expect from a comprehensive search interface. This will likely cause agent failures when trying to perform common search-related tasks beyond basic web queries.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources