Merchant Center MCP — find the products that can't sell.
A disapproved product is unsellable inventory that still costs you to carry. Connect Merchant Center and ask, in plain language, what's broken in the feed — account issues, product statuses and per-product diagnostics with the actual fix spelled out.
What the Google Merchant Center MCP is
The Offloda Merchant Center MCP is a read-only feed-health connector between Google Merchant Center and any MCP-capable AI client. It answers the question that shopping accounts quietly fail on: which products are actually eligible to serve, and why the rest aren't. Multi-account, so an agency running several storefronts sees each one separately.
What you can do
Analyze
Account-level health and aggregate product status — how much of the catalogue is actually servable right now, not how many rows were uploaded.
Diagnose
Per-product issues with rendered fix guidance — what's wrong, on which product, and what to change.
Prioritize
Sort the broken by what it's costing you, so a hundred disapprovals become the ten worth fixing this afternoon.
Report
Feed health beside Shopping spend in the same branded client report, so the conversation is about revenue, not row counts.
Governed writes for Google Merchant Center
There are none here — this connector cannot write to Merchant Center at all. The governed loop starts once a diagnosis becomes an action somewhere else: a Shopping campaign change, a product-page fix, a budget shift. Those pass through the same dry-run → confirm gate as everything else in Offloda.
Connects with
Google Merchant Center is one sensor in the same governed workspace — these are the plays it unlocks with the rest of your stack.
Google Ads
Shopping campaigns can only serve products the feed approves. Read spend and feed health together and a flat Shopping week usually explains itself — the budget was fine, the catalogue wasn't.
ExploreGoogle Analytics
Match what's eligible to serve against what actually converts. A product that's disapproved and a product that nobody buys need very different responses.
ExploreSearch Console
Product pages have to be crawlable before they can be a good feed entry. When both flag the same URLs, the fix is on the site, not in the feed.
ExploreSite Health
Feed rejections often trace to the page behind the product — a certificate problem or a slow template. Check the site before rewriting the feed.
ExploreAccount health · aggregate product status · account-level issues · per-product diagnostics with fix guidance · multi-account support.
All governed; all tenant-scoped.
Security
OAuth connection — Offloda never sees your password. Tokens are scoped and encrypted at rest. Every tenant is isolated; one client's data is never visible to another. No AI keys in the browser. Every action is written to an immutable audit log.
For agencies
Connect each client's Google Merchant Center under its own tenant. Your team sees only the accounts they're scoped to. Clients experience it as your product — your brand, your domain. Add Google Merchant Center to a client in minutes, not a migration.
vs. a raw Google Merchant Center MCP
A raw Merchant Center integration returns Google's issue codes and leaves the translation to you. Offloda renders the diagnosis as guidance, keeps every account in its own tenant, and puts feed health in the same chat as the Shopping campaigns spending against it — so the question 'why is Shopping down' gets one answer instead of three tabs.
Frequently asked questions
Can Offloda fix the feed automatically?
No. The Merchant Center connector is read-only by design — it tells you exactly what's wrong and what to change, and the change happens in your feed or your store platform. It diagnoses; it doesn't reach into your catalogue.
Does it work with more than one Merchant Center account?
Yes. Each account connects separately, so an agency running several storefronts — or a retailer with more than one — keeps them distinct rather than merged into one number.
What kind of issues does it surface?
Account-level problems that suppress everything, and product-level problems that kill individual items — with the diagnostic rendered as guidance rather than an opaque code you have to go look up.
Do I need this if Shopping is already running?
That's usually exactly when it matters. Shopping campaigns keep spending against whatever subset of the catalogue is still eligible, so a feed slowly rotting is invisible in the campaign report — it just looks like softer performance.
Google Merchant Center MCP — governed, white-label, yours.
Runs on your LLM subscription · Writes paused by default · Tenant-isolated