Google Growth MCP
Provides read-only access to Google Ads Keyword Planner for keyword research and planning.
Provides read-only access to Google Analytics 4 data for reporting and analysis.
Provides read-only access to Google Search Console data for search performance and site insights.
Provides read and write access to Google Tag Manager, including controlled changes with explicit summaries and user confirmation, plus separate approval for publishing. Account administration, user administration, and container deletion tools are not included.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Growth MCP get keyword ideas for 'cold brew coffee' with monthly search volume"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Growth MCP
One Node.js MCP server for four Google products. It has no npm dependencies.
Tool prefix | Product | Access |
| Google Ads Keyword Planner | Read-only |
| Google Analytics 4 | Read-only |
| Google Search Console | Read-only |
| Google Tag Manager | Read and write |
The four services run in one process. Each service has its own OAuth token and its own scopes.
Google Tag Manager safety
Each GTM change needs an exact change summary and
user_confirmed: true.Publishing needs a separate approval.
There are no tools for account administration, user administration, or container deletion.
Related MCP server: gsc-mcp
Requirements
Node.js 24 or later.
A Google Cloud project with an OAuth client of the type "Desktop app".
These APIs enabled in that project, for the services that you use: Google Analytics Data API, Google Analytics Admin API, Google Search Console API, Tag Manager API, Google Ads API.
For Keyword Planner only: a Google Ads developer token.
Install
Claude Code. Load the directory for one session:
claude --plugin-dir /path/to/google-growth-mcpFor a permanent installation, add the directory to a plugin marketplace.
Codex. The manifest is .codex-plugin/plugin.json. Add the directory to a Codex plugin marketplace.
Other MCP clients. Start the server on stdio:
{
"mcpServers": {
"google_growth": {
"command": "node",
"args": ["/absolute/path/to/google-growth-mcp/scripts/server.mjs"]
}
}
}The root .mcp.json uses a relative path for Codex. Claude Code replaces that entry with the google_growth entry in .claude-plugin/plugin.json, which uses ${CLAUDE_PLUGIN_ROOT}. Keep the two entries under the same server name.
Configuration
The source contains no account data. All settings come from one configuration directory or from environment variables.
The configuration directory is the first of these that is set:
GOOGLE_GROWTH_CONFIG_DIR$XDG_CONFIG_HOME/google-growth~/.config/google-growth
File | Content | Source |
| The OAuth client. Use the file that you download from Google Cloud, or | You |
|
| You |
| Optional settings. See | You |
| OAuth tokens, one for each service. | The authorization scripts |
An environment variable overrides the value in a file.
Variable | Replaces |
| The configuration directory |
|
|
|
|
|
|
|
|
Set the variables in the environment of the server process, for example in the env block of your MCP client configuration.
Authorization
Authorize each service that you use:
node services/ads/auth.mjs
node services/ga4/auth.mjs
node services/search_console/auth.mjs
node services/gtm/auth.mjsEach script prints a Google URL. Open the URL in a browser and approve the request. The script then saves the token in the configuration directory.
Service | Scopes |
Ads |
|
GA4 |
|
Search Console |
|
GTM |
|
Each <prefix>_auth_status tool shows if its service is connected.
Tests
npm test # tools, protocol, and GTM guards; no credentials necessary
node scripts/test.mjs --live # read-only requests to the Google APIs
node scripts/test.mjs --live --refresh # also tests the refresh token of each serviceSecurity
The token files have mode
0600, in a directory with mode0700.Do not put the configuration directory in a repository.
The
auth_statustools do not show secrets.
License
MIT. See LICENSE.
Available Tools
30 toolsads_auth_statusARead-onlyIdempotent
Check Google Ads OAuth, developer-token, and customer-ID readiness without revealing secrets.
Inputs: no named parameters.
ads_generate_historical_metricsCRead-onlyIdempotent
Return read-only Keyword Planner search volume, monthly volume, competition, and bid ranges for supplied keywords.
Inputs: keywords (required), customer_id, language_id, geo_target_ids, +4 more.
ads_generate_keyword_ideasBRead-onlyIdempotent
Generate read-only Keyword Planner ideas and historical metrics from seed keywords, a page URL, or both.
Inputs: url, keywords, page_size, page_token, +5 more.
ads_list_accessible_customersARead-onlyIdempotent
List Google Ads customer resource names directly accessible to the authenticated user.
Inputs: no named parameters.
ga4_auth_statusA
Check whether the local read-only Google Analytics OAuth connection is configured.
Inputs: no named parameters.
ga4_get_metadataB
List dimensions and metrics available to Google Analytics Data API reports for a GA4 property.
Inputs: property_id (required).
ga4_list_account_summariesA
List every Google Analytics account and GA4 property available to the authenticated account.
Inputs: no named parameters.
ga4_run_realtime_reportC
Run a read-only GA4 realtime report using named dimensions and metrics.
Inputs: metrics (required), property_id (required), limit, order_bys, +5 more.
ga4_run_reportC
Run a read-only GA4 report for a date range using named dimensions and metrics.
Inputs: metrics (required), end_date (required), start_date (required), property_id (required), +9 more.
gtm_auth_statusARead-onlyIdempotent
Check whether the local Google Tag Manager OAuth connection is configured and which scopes were granted.
Inputs: no named parameters.
gtm_create_entityA
Create a GTM tag, trigger, or variable in a workspace. Requires explicit user confirmation.
Inputs: entity (required), entity_type (required), change_summary (required), user_confirmed (required), +1 more.
gtm_create_versionADestructive
Create a GTM container version from a workspace. This consumes the workspace and requires explicit confirmation.
Inputs: name (required), change_summary (required), user_confirmed (required), workspace_path (required), +1 more.
gtm_create_workspaceB
Create a GTM workspace. Requires explicit user confirmation in the current request.
Inputs: name (required), change_summary (required), container_path (required), user_confirmed (required), +1 more.
gtm_delete_entityADestructive
Delete a GTM tag, trigger, or variable from a workspace. Requires explicit confirmation of this exact deletion.
Inputs: entity_path (required), change_summary (required), user_confirmed (required), fingerprint.
gtm_delete_workspaceBDestructive
Delete a GTM workspace. Requires explicit confirmation of this exact deletion.
Inputs: change_summary (required), user_confirmed (required), workspace_path (required).
gtm_get_entityBRead-onlyIdempotent
Get one GTM tag, trigger, or variable including its fingerprint and configuration.
Inputs: entity_path (required).
gtm_get_versionBRead-onlyIdempotent
Get a GTM container version and all of its entities.
Inputs: version_path (required).
gtm_list_accountsARead-onlyIdempotent
List GTM accounts available to the authenticated Google account.
Inputs: no named parameters.
gtm_list_containersBRead-onlyIdempotent
List containers in one GTM account.
Inputs: account_path (required).
gtm_list_entitiesCRead-onlyIdempotent
List tags, triggers, or variables in a GTM workspace.
Inputs: entity_type (required), workspace_path (required).
gtm_list_version_headersARead-onlyIdempotent
List GTM container version headers, including published and previous versions.
Inputs: container_path (required).
gtm_list_workspacesCRead-onlyIdempotent
List workspaces in one GTM container.
Inputs: container_path (required).
gtm_publish_versionADestructive
Publish a specific GTM container version. Requires separate explicit confirmation after reviewing the version.
Inputs: version_path (required), change_summary (required), user_confirmed (required), fingerprint.
gtm_sync_workspaceB
Sync a GTM workspace to the latest container version. Requires explicit user confirmation.
Inputs: change_summary (required), user_confirmed (required), workspace_path (required).
gtm_update_entityA
Update a GTM tag, trigger, or variable. Read it first and preserve its fingerprint. Requires explicit user confirmation.
Inputs: entity (required), entity_path (required), change_summary (required), user_confirmed (required).
search_console_auth_statusB
Check whether the local read-only Search Console OAuth connection is configured.
Inputs: no named parameters.
search_console_inspect_urlA
Read Google's indexed status for one URL under a Search Console property.
Inputs: inspection_url (required), site_url, language_code.
search_console_list_sitemapsB
List submitted sitemaps for a Search Console property.
Inputs: site_url, sitemap_index.
search_console_list_sitesA
List Search Console properties available to the authenticated Google account and their permission levels.
Inputs: no named parameters.
search_console_search_analyticsC
Query Google Search performance metrics for a Search Console property.
Inputs: end_date (required), start_date (required), site_url, row_limit, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 30 tools
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.
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.
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.
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
Related MCP Connectors
Hosted MCP server for marketing agencies: connect Google Ads, GA4, Search Console, Meta, LinkedIn and more to Claude or ChatGPT. Pull reports and make changes via OAuth login, no setup.
Read and edit GA4, Search Console and Google Tag Manager from any MCP client. 29 tools.
GA4, Google Ads and Search Console in Claude. Read-only OAuth, multi-account for agencies.
Hosted Google Ads MCP for Claude and ChatGPT. Preview every write. No developer token.
Related MCP Servers
- AlicenseBqualityBmaintenanceProduction-grade MCP server for the Google Tag Manager API v2 with read-only GA4 (Admin + Data API) tooling. 107 tools covering the full GTM surface, including server-side containers. Ships read-only: writes, publishes, and deletes are each gated behind separate opt-in flags, every mutation requires per-call confirmation, and a dry-run mode simulates changes. Includes container audits203663 npm3MIT
- AlicenseBqualityCmaintenanceA production-oriented, read-only Google Search Console MCP server and TypeScript SDK for Claude, Cursor, VS Code, and other MCP clients. Query real Search Console data, inspect indexed URLs, review sitemaps, compare periods, and surface transparent SEO opportunities without handing private data to a third-party SaaS.20MIT
- AlicenseAqualityCmaintenanceUnifies Google Ads, Tag Manager, Search Console, and GA4 into a single MCP server, enabling reporting, monitoring, campaign/tag/property creation, and live mutations with dry-run safety.94Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query read-only Google Search Console, GA4, Google Ads, and Workspace data through a single MCP endpoint, alongside a matching CLI. Sign-in happens once so the agent never sees Google tokens.MIT