Marketing MCP — Client Registry

Google account access (preferred)

Connect the Google account that already has client access. Search Console and GA4 will prefer this account over the service account.

Checking Google account connection…

Use the agency Google account that already sees the client properties, e.g. kwsltdmarketing@gmail.com. This avoids needing to add the service account to Search Console properties.

Preferred for GSC and GA4 discovery/reporting. Service account remains as fallback.

Google Ads access

Connect the Google account with MCC / client Ads access. Required for campaigns, keywords, and PMax search term tools.

Checking Google Ads connection…

Sign in with kwsltdmarketing@gmail.com (or whichever account manages client Google Ads). Reconnect here whenever health check shows invalid_grant. Token is stored on this server and overrides stale secrets automatically.

CLI fallback: pnpm auth:google-ads then pnpm auth:google-ads:sync-secrets

GA4 service account access

Bulk-add the MCP service account as Viewer at the GA4 account level — one grant per account covers all properties under it (including new ones). Andrew runs this once per client GA4 account instead of clicking through every property.

Loading service account email…

Sign in with the Google account that has Manage Users on client GA4 accounts. Client accounts you cannot manage will show as failed — ask the client owner to run this or grant access manually.

Google Cloud setup (fixes redirect_uri_mismatch):

APIs & Services → Credentials → OAuth 2.0 Client → type must be Web application (not Desktop)
Add every URI below to Authorized redirect URIs:

Active redirect for this session: …

CLI: pnpm ga4:grant-access · OAuth client: …

Image generation (Nano Banana)

Generate an image with Google Gemini and host it on Bunny CDN. Returns a public URL you can paste anywhere.

Checking image generation config…

Prompt

MCP endpoint: … · auth header x-api-key (defaults to admin password unless IMAGE_MCP_API_KEY is set).

Secrets cache

The server caches secrets on disk at boot. If you added/changed a key on the secrets server (e.g. Ahrefs, Google Ads developer token) it won't apply until this cache refreshes. Use this button instead of restarting the container — it also auto-refreshes every 3 minutes on its own.

Idle.

Note: existing MCP sessions (already-connected Claude tabs) keep their old tool list — reconnect/start a new session after refreshing to see updated tools.

Google Ads customer ID

This is the 10-digit account number for the client's Google Ads account. The MCP uses it to pull campaigns, keywords, and performance data.

Format rule: Enter digits only — no dashes.
UI shows 680-308-4761 → you enter 6803084761

Method 1 — From Google Ads UI (easiest)

Go to ads.google.com and sign in.
Click the account picker (top-right corner — shows account name or ID).
Find the client account you want (not your MCC/manager unless that's the target).
Look for the number under the account name — format like 123-456-7890.
Remove the dashes and paste here: 1234567890.

Method 2 — From the URL

Open the client's Google Ads account in your browser.
Check the URL — it often contains ocid= or authuser= with a customer parameter.
Or go to Settings → Account settings — the Customer ID is listed there.

MCC (manager) vs client account — which ID to use?

Client account ID — use this field for each client in the registry. One client = one customer ID.
MCC / manager ID — configured once in server .env as GOOGLE_ADS_LOGIN_CUSTOMER_ID (not here). Your MCC is already set to 6803084761 (House Digital).
If you manage many accounts under one MCC, each client gets their own customer ID here — the MCP lists all accessible accounts via agency_list_clients.

How to verify it's correct

Save the client in this admin UI.
In Cursor, run MCP tool agency_reload_clients.
Run agency_set_active_client with the client name.
Run google_ads_get_campaigns — if campaigns return, the ID is correct.

Example: House Digital → 6803084761

GA4 property ID

Numeric ID for the client's Google Analytics 4 property (not the measurement ID G-XXXX).

Go to analytics.google.com.
Click Admin (gear icon, bottom-left).
Make sure the correct Property is selected in the top column.
Click Property details (or Property settings).
Copy Property ID — numbers only, e.g. 123456789.

Service account access required: Add the MCP service account as a Viewer on each GA4 property (Admin → Property access management).

Bulk setup: Use the GA4 service account access card above — Andrew signs in once and grants Viewer on every property he can manage.

Example: 987654321

Search Console site URL (GSC)

Must match exactly how the property appears in Search Console — format depends on property type.

Go to search.google.com/search-console.
Open the property picker (top-left) and select the client's site.
Copy the property string exactly as shown:

Domain property (covers all subdomains): sc-domain:example.com
URL-prefix property: https://www.example.com/ (include https and trailing slash)

Service account access required: Search Console → Settings → Users and permissions → add the same service account email with Restricted or Full access.

Domain: sc-domain:housedigital.co.uk
URL prefix: https://www.housedigital.co.uk/

Meta ad account ID

Format: act_ followed by numbers.

Go to Meta Business Suite or Ads Manager.
Open Ads Manager for the client.
Click Settings (or hamburger menu → All tools → Advert account settings).
Find Ad account ID — e.g. 123456789.
Enter as act_123456789 (with the act_ prefix).

Meta tools only work when META_ACCESS_TOKEN is set in server .env.

Example: act_987654321

Domain

Root domain for the client — used by Ahrefs tools and to help match accounts.

Enter without https:// — just example.com
No trailing slash
Use the primary marketing domain

Example: housedigital.co.uk

Registry key

Internal slug used by the MCP to identify this client. Auto-generated from the name when you type.

Lowercase, hyphens instead of spaces
Never change after creation (used as Firestore document ID)
Example: "Acme Corp UK" → acme-corp-uk

After saving — sync with Cursor MCP

Changes save to Firestore instantly from this UI.
In Cursor chat, ask the AI to run agency_reload_clients OR restart the MCP server.
Then: agency_set_active_client with the client name.
All platform tools will use that client's IDs automatically.

Save alias / override

Client name *

Optional preferred name shown in MCP and the discovered client list

Registry key *

Auto-generated from name — do not change after create

Domain

Google Ads customer ID

10 digits, no dashes — see field guide for step-by-step

GA4 property ID

GSC site URL

Meta ad account ID

Tags (comma separated)

Notes

Discovered client directory

Name	Key	Source	Ads ID	GA4	GSC	Tags

Marketing MCP Admin

Client Registry

Google account access (preferred)

Google Ads access

GA4 service account access

Image generation (Nano Banana)

Secrets cache

Google Ads customer ID

GA4 property ID

Search Console site URL (GSC)

Meta ad account ID

Domain

Registry key

After saving — sync with Cursor MCP

Save alias / override

Discovered client directory