google-growth
Google Ads Keyword Planner, Tag Manager, Analytics and Search Console in one MCP process.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/kremnyi--google-growth-mcp)HTML
<a href="/listings/kremnyi--google-growth-mcp"><img src="/api/listings/kremnyi--google-growth-mcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
**Claude Code.** Load the directory for one session:
claude --plugin-dir /path/to/google-growth-mcp
For 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.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/plugin.json · Manifest · 15 lines
- {
- "name": "google-growth",
- "displayName": "Google Growth MCP",
- "version": "0.2.0",
- "description": "Google Ads Keyword Planner, Tag Manager, Analytics and Search Console in one MCP process.",
- "author": { "name": "Bohdan Kremnyi" },
- "license": "MIT",
- "keywords": ["google", "analytics", "seo", "gtm", "keyword-planner"],
- "mcpServers": {
- "google_growth": {
- "command": "node",
- "args": ["${CLAUDE_PLUGIN_ROOT}/scripts/server.mjs"]
- }
- }
- }
README.md · README · 121 lines
- # Google Growth MCP
- One Node.js MCP server for four Google products. It has no npm dependencies.
- | Tool prefix | Product | Access |
- | --- | --- | --- |
- | `ads_` | Google Ads Keyword Planner | Read-only |
- | `ga4_` | Google Analytics 4 | Read-only |
- | `search_console_` | Google Search Console | Read-only |
- | `gtm_` | 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.
- ## 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:
- ```sh
- claude --plugin-dir /path/to/google-growth-mcp
- ```
- For 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:
- ```json
- {
- "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:
- 1. `GOOGLE_GROWTH_CONFIG_DIR`
- 2. `$XDG_CONFIG_HOME/google-growth`
- 3. `~/.config/google-growth`
- | File | Content | Source |
- | --- | --- | --- |
- | `oauth-client.json` | The OAuth client. Use the file that you download from Google Cloud, or `{"client_id": "...", "client_secret": "..."}`. | You |
- | `google-ads-keyword-planner-api.json` | `{"developer_token": "...", "customer_id": "...", "login_customer_id": "..."}`. Necessary for Ads only. `login_customer_id` is optional. | You |
- | `config.json` | Optional settings. See `config.example.json`. | You |
- | `google-ads-keyword-planner.json`, `google-analytics.json`, `google-search-console.json`, `google-tag-manager.json` | OAuth tokens, one for each service. | The authorization scripts |
- An environment variable overrides the value in a file.
- | Variable | Replaces |
- | --- | --- |
- | `GOOGLE_GROWTH_CONFIG_DIR` | The configuration directory |
- | `GOOGLE_GROWTH_CLIENT_ID`, `GOOGLE_GROWTH_CLIENT_SECRET` | `oauth-client.json` |
- | `GOOGLE_GROWTH_LOGIN_HINT` | `login_hint` in `config.json`. The Google account that the consent screen selects. |
- | `GOOGLE_GROWTH_SEARCH_CONSOLE_SITE` | `search_console_site_url` in `config.json`. The property that the tools use when a call has no `site_url`, for example `sc-domain:example.com`. |
- | `GOOGLE_GROWTH_ADS_DEVELOPER_TOKEN`, `GOOGLE_GROWTH_ADS_CUSTOMER_ID`, `GOOGLE_GROWTH_ADS_LOGIN_CUSTOMER_ID` | `google-ads-keyword-planner-api.json` |
- 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:
- ```sh
- node services/ads/auth.mjs
- node services/ga4/auth.mjs
- node services/search_console/auth.mjs
- node services/gtm/auth.mjs
- ```
- Each 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 | `adwords` |
- | GA4 | `analytics.readonly` |
- | Search Console | `webmasters.readonly` |
- | GTM | `tagmanager.readonly`, `tagmanager.edit.containers`, `tagmanager.edit.containerversions`, `tagmanager.publish` |
- Each `<prefix>_auth_status` tool shows if its service is connected.
- ## Tests
- ```sh
- 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 service
- ```
- ## Security
- - The token files have mode `0600`, in a directory with mode `0700`.
- - Do not put the configuration directory in a repository.
- - The `auth_status` tools do not show secrets.
- ## License
- MIT. See `LICENSE`.
Version history
v0.2.011/21/2026
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.