Skip to content
Back to search

google-growth

SkillWorks with Claude CodeGitHub

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.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kremnyi--google-growth-mcp/badge.svg)](/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

i

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
  1. {
  2. "name": "google-growth",
  3. "displayName": "Google Growth MCP",
  4. "version": "0.2.0",
  5. "description": "Google Ads Keyword Planner, Tag Manager, Analytics and Search Console in one MCP process.",
  6. "author": { "name": "Bohdan Kremnyi" },
  7. "license": "MIT",
  8. "keywords": ["google", "analytics", "seo", "gtm", "keyword-planner"],
  9. "mcpServers": {
  10. "google_growth": {
  11. "command": "node",
  12. "args": ["${CLAUDE_PLUGIN_ROOT}/scripts/server.mjs"]
  13. }
  14. }
  15. }
README.md · README · 121 lines
  1. # Google Growth MCP
  2. One Node.js MCP server for four Google products. It has no npm dependencies.
  3. | Tool prefix | Product | Access |
  4. | --- | --- | --- |
  5. | `ads_` | Google Ads Keyword Planner | Read-only |
  6. | `ga4_` | Google Analytics 4 | Read-only |
  7. | `search_console_` | Google Search Console | Read-only |
  8. | `gtm_` | Google Tag Manager | Read and write |
  9. The four services run in one process. Each service has its own OAuth token and its own scopes.
  10. ## Google Tag Manager safety
  11. - Each GTM change needs an exact change summary and `user_confirmed: true`.
  12. - Publishing needs a separate approval.
  13. - There are no tools for account administration, user administration, or container deletion.
  14. ## Requirements
  15. - Node.js 24 or later.
  16. - A Google Cloud project with an OAuth client of the type "Desktop app".
  17. - 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.
  18. - For Keyword Planner only: a Google Ads developer token.
  19. ## Install
  20. **Claude Code.** Load the directory for one session:
  21. ```sh
  22. claude --plugin-dir /path/to/google-growth-mcp
  23. ```
  24. For a permanent installation, add the directory to a plugin marketplace.
  25. **Codex.** The manifest is `.codex-plugin/plugin.json`. Add the directory to a Codex plugin marketplace.
  26. **Other MCP clients.** Start the server on stdio:
  27. ```json
  28. {
  29. "mcpServers": {
  30. "google_growth": {
  31. "command": "node",
  32. "args": ["/absolute/path/to/google-growth-mcp/scripts/server.mjs"]
  33. }
  34. }
  35. }
  36. ```
  37. 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.
  38. ## Configuration
  39. The source contains no account data. All settings come from one configuration directory or from environment variables.
  40. The configuration directory is the first of these that is set:
  41. 1. `GOOGLE_GROWTH_CONFIG_DIR`
  42. 2. `$XDG_CONFIG_HOME/google-growth`
  43. 3. `~/.config/google-growth`
  44. | File | Content | Source |
  45. | --- | --- | --- |
  46. | `oauth-client.json` | The OAuth client. Use the file that you download from Google Cloud, or `{"client_id": "...", "client_secret": "..."}`. | You |
  47. | `google-ads-keyword-planner-api.json` | `{"developer_token": "...", "customer_id": "...", "login_customer_id": "..."}`. Necessary for Ads only. `login_customer_id` is optional. | You |
  48. | `config.json` | Optional settings. See `config.example.json`. | You |
  49. | `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 |
  50. An environment variable overrides the value in a file.
  51. | Variable | Replaces |
  52. | --- | --- |
  53. | `GOOGLE_GROWTH_CONFIG_DIR` | The configuration directory |
  54. | `GOOGLE_GROWTH_CLIENT_ID`, `GOOGLE_GROWTH_CLIENT_SECRET` | `oauth-client.json` |
  55. | `GOOGLE_GROWTH_LOGIN_HINT` | `login_hint` in `config.json`. The Google account that the consent screen selects. |
  56. | `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`. |
  57. | `GOOGLE_GROWTH_ADS_DEVELOPER_TOKEN`, `GOOGLE_GROWTH_ADS_CUSTOMER_ID`, `GOOGLE_GROWTH_ADS_LOGIN_CUSTOMER_ID` | `google-ads-keyword-planner-api.json` |
  58. Set the variables in the environment of the server process, for example in the `env` block of your MCP client configuration.
  59. ## Authorization
  60. Authorize each service that you use:
  61. ```sh
  62. node services/ads/auth.mjs
  63. node services/ga4/auth.mjs
  64. node services/search_console/auth.mjs
  65. node services/gtm/auth.mjs
  66. ```
  67. 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.
  68. | Service | Scopes |
  69. | --- | --- |
  70. | Ads | `adwords` |
  71. | GA4 | `analytics.readonly` |
  72. | Search Console | `webmasters.readonly` |
  73. | GTM | `tagmanager.readonly`, `tagmanager.edit.containers`, `tagmanager.edit.containerversions`, `tagmanager.publish` |
  74. Each `<prefix>_auth_status` tool shows if its service is connected.
  75. ## Tests
  76. ```sh
  77. npm test # tools, protocol, and GTM guards; no credentials necessary
  78. node scripts/test.mjs --live # read-only requests to the Google APIs
  79. node scripts/test.mjs --live --refresh # also tests the refresh token of each service
  80. ```
  81. ## Security
  82. - The token files have mode `0600`, in a directory with mode `0700`.
  83. - Do not put the configuration directory in a repository.
  84. - The `auth_status` tools do not show secrets.
  85. ## License
  86. MIT. See `LICENSE`.

Version history

  • v0.2.011/21/2026

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.