gtm-mcp-server 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -88,9 +88,19 @@ The package is published publicly to the npm registry.
|
|
|
88
88
|
|
|
89
89
|
3. Create an OAuth client in Google Cloud:
|
|
90
90
|
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
91
|
+
1. Go to [Google Cloud Console](https://console.cloud.google.com/) and select (or create) the project tied to your GTM access.
|
|
92
|
+
2. Left sidebar → **APIs & Services** → **Credentials**.
|
|
93
|
+
3. If you haven't already, enable the **Tag Manager API**: **APIs & Services** → **Library** → search "Tag Manager API" → **Enable**.
|
|
94
|
+
4. Still under **Credentials** → **Create Credentials** (top of page) → **OAuth client ID**.
|
|
95
|
+
5. If prompted, configure the **OAuth consent screen** first (External or Internal, whichever your Google Workspace allows) — app name and your email are enough for a test app; you don't need to submit it for verification.
|
|
96
|
+
6. Back on the **Create OAuth client ID** form:
|
|
97
|
+
- Application type: `Web application`
|
|
98
|
+
- Name: anything recognizable, e.g. `gtm-mcp-server`
|
|
99
|
+
- Authorized JavaScript origins: leave empty
|
|
100
|
+
- Authorized redirect URIs: `http://localhost:3000/oauth/google/callback`
|
|
101
|
+
7. Click **Create** — a dialog shows your **Client ID** and **Client Secret**. Copy both now (you can always re-open them later from the Credentials list, but the Secret is only shown in full on creation and on a later "download JSON"/reset).
|
|
102
|
+
|
|
103
|
+
**Team note:** the Client ID/Secret identify the *app*, not a specific person — they're the same for everyone on the team. Create this once; don't repeat this step per developer.
|
|
94
104
|
|
|
95
105
|
4. Add the OAuth client values to `.env`:
|
|
96
106
|
|
|
@@ -122,6 +132,8 @@ The package is published publicly to the npm registry.
|
|
|
122
132
|
|
|
123
133
|
8. Restart the server.
|
|
124
134
|
|
|
135
|
+
**Sharing this with a team that uses ONE shared Google account:** the refresh token (step 6-7) is tied to whichever Google account completes the consent screen — not to the person running the browser. If the whole team already logs into GTM with one shared account, only ONE teammate needs to do steps 3-7 once. The resulting `GTM_OAUTH_CLIENT_ID`, `GTM_OAUTH_CLIENT_SECRET` and `GTM_OAUTH_REFRESH_TOKEN` can then be copied into everyone's own `.mcp.json` as-is — nobody else needs to repeat the OAuth flow. This only applies when the account really is shared; if each teammate has their own individual Google account (even with the same GTM permissions), each of them needs their own refresh token from their own sign-in (steps 6-7), though they can all reuse the same Client ID/Secret from step 3.
|
|
136
|
+
|
|
125
137
|
## Create Tags
|
|
126
138
|
|
|
127
139
|
By default the server is read-only. To create tags, set:
|