Google Merchant Center

Open Settings → Integrations and click Connecton the Google Merchant Center card. You'll be redirected to a Google consent screen requesting one scope:

• https://www.googleapis.com/auth/content — Merchant API v1 read + write access for every Merchant Center account the consenting Google user can see.

Approve, and Google sends you back to ShopMCP with a refresh token we encrypt and store per-workspace.

The Merchant API — unlike GA4 or Google Ads — won't let any GCP project call it until the project is explicitly registered as a developer against one of your Merchant Center accounts. Google has no UI for this, so ShopMCP does it for you:

• After OAuth, if registration is missing, the picker shows an inline form.
• Enter any Merchant Center account ID you own (top-right of merchants.google.com) and click Register. One registration covers every account the same Google user has access to.
• Google then takes up to ~5 minutes to propagate. Click Try again.

After OAuth, ShopMCP fetches every Merchant Center account your Google user can see, plus every sub-account under any MCAs you have access to, and groups them in a multi-select picker.

• Standalone accounts— single Merchant Center accounts with no children. Pick one and you're done.
• MCAs (Multi-Client Accounts) — agency containers. Picking the MCA itself connects the top-level account. You can also tick individual sub-accounts to expose each one as its own connection row.

By default, only read tools are registered — list products, pull reports, render issue help, etc. To allow the LLM to upsert products, manage inventories, create promotions, trigger issue-resolution actions, or update data sources, flip the Allow writes toggle on the Merchant Center card in the settings page.

Writes still respect your Merchant Center role — Google's permission model applies even with the scope granted. An auth_forbidden error with a 403 means the Google user needs Admin (or Standard with Shopping Ads access) inside Merchant Center itself.

The connection card now shows Connectedwith the Merchant Center account name. Now go ask your LLM whatever you'd normally open Merchant Center for — the prompts below are a starting point grouped by common workflows.

• Run a feed health overview — show me every account issue and how many products are disapproved per reason.
• Why is product SKU-123 disapproved, and what's the exact fix?
• Which item-level issues are affecting the most revenue right now?
• Summarise every disapproval on our account grouped by destination country.
• Request a manual review for the policy disapproval on offer IDs 42 and 43. (write tools on)

• Run a pricing opportunity audit — match-competitor vs raise-for-margin vs apply-suggestion buckets.
• Which SKUs does Google suggest lowering prices on, and by how much is projected lift per suggestion?
• How do our prices compare to the market benchmark in the UK across our top 50 products?
• Score our competitive position in the “running shoes” category this month vs last month.
• Which competitor domains outrank us in paid Shopping results, and where do they overlap with our products?

• Give me the top 20 best-selling products in the US for our category this week.
• Which best-selling brands are we not carrying that we should consider?
• Cross-reference best sellers with our current inventory — which top items are out of stock right now?
• Compare demand for our category in Australia vs New Zealand over the last month.

• What were our Shopping clicks, impressions, and conversions last week, broken down by brand?
• Show me the 20 products with the highest impressions but the worst conversion rate.
• Give me my morning dashboard — yesterday vs the 28-day average, new disapprovals overnight, biggest movers.
• How is engagement on our store links and image search trending month over month?

The following prompts only work when Allow writes is toggled on.

• Update the availability of SKUs in this CSV to “in stock” and raise their price by 5%.
• Create a 15% discount promotion called “Spring Sale” valid April 15–30 on all products in the “outerwear” type.
• Set regional inventory for SKU-123 to 50 units in California at $39.99.
• Trigger a fresh fetch of our main product feed data source.
• Subscribe us to notifications for product-status changes on the US destination.

• List every user with access to our Merchant Center account and their role.
• Which programs are enabled on this account — Shopping Ads, Free Listings, Buy on Google, LIA?
• Show my shipping services and which countries they cover.
• Am I close to any Merchant API quota limit right now?
• Explain price insights eligibility — why does SKU-42 not have a suggestion?

The Google account you authorise needs at least Standard access on every Merchant Center account you want to expose, and Admin if you plan to enable write tools or manage users via the API.

• “No Merchant Center accounts found”— the Google user you chose doesn't have access to any Merchant Center account. Ask a Merchant Center admin to invite you, then restart the connect flow.
• Price insights return no suggestions for some products — Google only generates suggestions for products with enough serving history. Ask your LLM to explain price insights eligibility for specific SKUs.
• MCA sub-accounts missing from the picker — the Google user may have Admin on the MCA but not on its sub-accounts. Grant sub-account access in Merchant Center, then reload the picker.
• Hitting 429 rate limits — ask your LLM to check the Merchant API quotaand it'll show you which group is saturated. Narrow your date range, lower result limits, or split batched writes across a longer window.
• Write prompts come back with “I can't do that”— toggle Allow writes on the settings page. There's a ~45-second cache on the tool list, so your next question will pick up the new capabilities.