Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_GROWTH_CLIENT_IDNoReplaces the client_id in oauth-client.json.
GOOGLE_GROWTH_CONFIG_DIRNoThe configuration directory. The first set of GOOGLE_GROWTH_CONFIG_DIR, $XDG_CONFIG_HOME/google-growth, or ~/.config/google-growth is used.
GOOGLE_GROWTH_LOGIN_HINTNoReplaces login_hint in config.json. The Google account that the consent screen selects.
GOOGLE_GROWTH_CLIENT_SECRETNoReplaces the client_secret in oauth-client.json.
GOOGLE_GROWTH_ADS_CUSTOMER_IDNoReplaces customer_id in google-ads-keyword-planner-api.json.
GOOGLE_GROWTH_ADS_DEVELOPER_TOKENNoReplaces developer_token in google-ads-keyword-planner-api.json.
GOOGLE_GROWTH_SEARCH_CONSOLE_SITENoReplaces search_console_site_url in config.json. The Search Console property used when a call has no site_url, for example sc-domain:example.com.
GOOGLE_GROWTH_ADS_LOGIN_CUSTOMER_IDNoReplaces login_customer_id in google-ads-keyword-planner-api.json. Optional.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Google Ads Keyword Planner, GA4, Search Console and Google Tag Manager share one process and retain separate OAuth tokens. Ads, GA4 and Search Console expose read-only tools. List GA4 accounts before choosing a property unless its ID is supplied. Search Console has no default property; list sites before choosing one. Before EVERY GTM write, deletion, version creation or publish, show the exact change and obtain explicit user confirmation in the current request. Publishing needs its own confirmation after reviewing the version. Never administer GTM users/accounts or delete containers. Set user_confirmed only for a specifically approved action; it is not blanket permission.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ads_auth_statusA

Check Google Ads OAuth, developer-token, and customer-ID readiness without revealing secrets.

ads_list_accessible_customersA

List Google Ads customer resource names directly accessible to the authenticated user.

ads_generate_keyword_ideasB

Generate read-only Keyword Planner ideas and historical metrics from seed keywords, a page URL, or both.

ads_generate_historical_metricsC

Return read-only Keyword Planner search volume, monthly volume, competition, and bid ranges for supplied keywords.

gtm_auth_statusA

Check whether the local Google Tag Manager OAuth connection is configured and which scopes were granted.

gtm_list_accountsA

List GTM accounts available to the authenticated Google account.

gtm_list_containersB

List containers in one GTM account.

gtm_list_workspacesC

List workspaces in one GTM container.

gtm_list_entitiesC

List tags, triggers, or variables in a GTM workspace.

gtm_get_entityB

Get one GTM tag, trigger, or variable including its fingerprint and configuration.

gtm_list_version_headersA

List GTM container version headers, including published and previous versions.

gtm_get_versionB

Get a GTM container version and all of its entities.

gtm_create_workspaceB

Create a GTM workspace. Requires explicit user confirmation in the current request.

gtm_sync_workspaceB

Sync a GTM workspace to the latest container version. Requires explicit user confirmation.

gtm_create_entityA

Create a GTM tag, trigger, or variable in a workspace. Requires explicit user confirmation.

gtm_update_entityA

Update a GTM tag, trigger, or variable. Read it first and preserve its fingerprint. Requires explicit user confirmation.

gtm_delete_entityA

Delete a GTM tag, trigger, or variable from a workspace. Requires explicit confirmation of this exact deletion.

gtm_delete_workspaceB

Delete a GTM workspace. Requires explicit confirmation of this exact deletion.

gtm_create_versionA

Create a GTM container version from a workspace. This consumes the workspace and requires explicit confirmation.

gtm_publish_versionA

Publish a specific GTM container version. Requires separate explicit confirmation after reviewing the version.

ga4_auth_statusA

Check whether the local read-only Google Analytics OAuth connection is configured.

ga4_list_account_summariesA

List every Google Analytics account and GA4 property available to the authenticated account.

ga4_get_metadataB

List dimensions and metrics available to Google Analytics Data API reports for a GA4 property.

ga4_run_reportC

Run a read-only GA4 report for a date range using named dimensions and metrics.

ga4_run_realtime_reportC

Run a read-only GA4 realtime report using named dimensions and metrics.

search_console_auth_statusB

Check whether the local read-only Search Console OAuth connection is configured.

search_console_list_sitesA

List Search Console properties available to the authenticated Google account and their permission levels.

search_console_search_analyticsC

Query Google Search performance metrics for a Search Console property.

search_console_list_sitemapsB

List submitted sitemaps for a Search Console property.

search_console_inspect_urlA

Read Google's indexed status for one URL under a Search Console property.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 30 tools

Disambiguation4/5

Tools are grouped by product prefix and mostly target distinct resources or actions, so an agent can usually choose correctly. Minor ambiguity exists across repeated auth-status tools and the two Keyword Planner tools (keyword ideas vs. historical metrics), but descriptions clarify them well.

Naming Consistency5/5

All tools use snake_case with a consistent product-prefixed pattern such as ads_, gtm_, ga4_, and search_console_. Actions are predictable within each group (list_, get_, create_, update_, delete_, run_, auth_status), making names easy to scan and infer.

Tool Count4/5

Thirty tools is heavy for a single MCP server, but the surface spans four distinct Google products, each with its own auth and resource lifecycle. The count is above the ideal 3–15 range but defensible given the multi-product scope, with only GTM feeling somewhat expansive.

Completeness4/5

The surface covers core workflows across all four products: Ads auth and keyword research, GTM full lifecycle from workspace creation to publishing, GA4 reporting, and Search Console analytics and inspection. Gaps are minor by comparison, such as no Ads campaign management or Search Console sitemap submission, but these are outside the mostly read-only/GTM-operational scope.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues