Connect Google Merchant Center to Claude (2026 Guide)
To connect Google Merchant Center to Claude, create a free PaidSync account, authorize Merchant Center via Google OAuth in the PaidSync dashboard, then add your personal PaidSync MCP server URL to Claude's Connectors or Claude Desktop. Setup takes about five minutes and needs no code. Once connected, Claude gets 15 Merchant Center tools that audit your feed, triage disapprovals, and fix product data from chat.
This guide covers the working session, not just the setup. What Claude can read, what it can write, the exact tool names it calls, and the two things the Merchant Center group deliberately does not do. If you only need the Claude Desktop config snippet, the setup quickstart has it. This page is for the day after setup, when you want the feed actually fixed.
What You Need Before You Start
- A Google Merchant Center account, standalone or under a Multi-Client Account. The Google login you authorize with must have access to it.
- A Claude plan that supports connectors (claude.ai) or Claude Desktop. Claude Code works too.
- A PaidSync account. The free plan is $0 with 15 tool calls a month, enough to connect and run a first audit. Pro starts at $99 a month for 600 calls.
Under the hood, PaidSync's Merchant Center group runs on Google's Merchant API, the successor to the Content API for Shopping, which Google sunsets on August 18, 2026. Tools built on the old Content API stop working after that date. These do not.
The Connect Flow in Four Steps
1Create a PaidSync account
Go to paidsync.ai/signup and sign up with Google or email. You land on the free plan. No credit card.
2Authorize Merchant Center
In the PaidSync dashboard, click Connect Google Merchant Center and approve the Google OAuth prompt. If you manage several accounts under an MCA, the flow lists every merchant ID you can access. Your Google credentials go to Google, not to Claude and not into PaidSync's storage.
3Add PaidSync to Claude
Copy your personal MCP server URL from the dashboard. On claude.ai, paste it under Settings, then Connectors. In Claude Desktop, add it to claude_desktop_config.json. The quickstart shows the exact JSON block.
4Pick the account Claude works on
In your first chat, ask Claude to list your merchant accounts. It calls list_merchant_accounts, shows every ID, and binds the one you choose with set_active_merchant_account. Every tool call after that runs against that account until you switch.
The 15 Merchant Center Tools Claude Gets
PaidSync ships 430+ tools across 13 platforms. The Merchant Center group is 15 of them, split across four jobs.
| Job | Tools | What Claude does with them |
|---|---|---|
| Connect and bind | connect_merchant_center, merchant_auth_status, list_merchant_accounts, set_active_merchant_account, get_merchant_account_status | Authorize, pick the merchant ID, check account health |
| Read and audit | list_products, list_product_issues, get_product_performance, merchant_list_data_sources | Walk the catalog, pull disapprovals and warnings, rank SKUs by clicks and conversions, map the feed sources |
| Write product data | merchant_insert_product, merchant_delete_product, merchant_create_supplemental_feed | Upsert corrected products, remove dead SKUs, layer price and title overrides without touching the primary feed |
| Google Ads linking | merchant_create_link, merchant_list_links, merchant_delete_link | Wire Merchant Center to the Google Ads account that runs Shopping and Performance Max |
Every write is approval-gated. Claude shows a dry-run preview of what would change before anything changes, and destructive calls like deleting a product require explicit confirmation. You can revoke the session from the PaidSync dashboard at any time.
Connect Merchant Center to Claude in about five minutes. Free plan, 15 calls a month, no card.
Get started for free See pricingWhat to Ask Claude Once Connected
Three workflows cover most of what Shopping advertisers actually need from Merchant Center. Each maps to specific tools, so you can verify what ran.
Feed audit
Claude pages through list_products, cross-references list_product_issues, and ranks the result against get_product_performance. The output is a priority list sorted by revenue at risk, not an alphabetical dump. On a large catalog this uses many paginated calls, which is why heavy audits fit the Pro plan better than Free.
Disapproval triage
list_product_issues returns each issue with its code, severity, destination (shopping_ads versus free_listings), affected country, Google's resolution instructions, and a documentation link. That last distinction matters. A disapproval that only hits free listings is a different fire than one blocking paid Shopping. Claude sorts them so you fix the paid blockers first.
Product data fixes
merchant_insert_product is an upsert. A product with the same offer ID, content language, and feed label is replaced whole, and the corrected product immediately re-enters Google's review pipeline. For temporary changes like sale pricing or title tests, merchant_create_supplemental_feed layers overrides on top of the primary feed without editing it, so the override lifts off cleanly when the sale ends.
What This Does Not Do
Honest limits, so you plan around them
- Campaigns are not in this group. Shopping and Performance Max campaigns are built and managed through PaidSync's Google Ads tools, not the Merchant Center tools. The merchant group feeds the data; the campaign work happens on the Google Ads side of the same session. See connecting Google Ads to Claude.
- Link approval stays human.
merchant_create_linkrequests the Merchant Center to Google Ads link, but a Google Ads admin must approve it inside the Google Ads UI before Shopping ads serve. Claude cannot approve it for you. - Google decides approvals. A corrected product re-enters review when upserted. Claude fixes the data; it cannot force Google to approve it.
- Performance data lags.
get_product_performancereads Merchant Center Reports, which run one to two days behind. For same-day spend questions, use the Google Ads reporting tools instead.
How This Compares to Doing It in the UI
Merchant Center UI. Fine for one product. The Diagnostics tab shows issues, but cross-referencing them against performance means exporting to a spreadsheet and joining by hand.
Official Google MCP. Google's open-source MCP server (announced October 7, 2025) covers Google Ads API queries only and is read-only. The repository has no Merchant Center product, feed, or disapproval tools as of August 2026.
PaidSync through Claude. Reads and writes on the feed itself, plus the Google Ads, GA4, and GTM groups in the same session. One conversation goes from "what is disapproved" to "it is fixed and resubmitted" without an export.
Frequently Asked Questions
How do I connect Google Merchant Center to Claude?
Create a free PaidSync account at paidsync.ai/signup, click Connect Google Merchant Center in the dashboard and authorize via Google OAuth, then add your personal PaidSync MCP server URL to Claude's Connectors on claude.ai or to Claude Desktop's config file. Setup takes about five minutes and needs no code. The free plan is $0 with 15 tool calls a month.
Can Claude fix disapproved products in Merchant Center?
Yes, in two steps. Claude runs list_product_issues to pull every disapproval with its issue code, severity, destination, country, and Google's resolution instructions. Then it fixes the underlying product data with merchant_insert_product, which upserts the corrected product. The corrected product re-enters Google's review pipeline, so final approval is Google's decision, not Claude's. Writes are approval-gated with a dry-run preview before anything changes.
Can Claude create Shopping campaigns with the Merchant Center tools?
No. The Merchant Center group manages product data, feeds, and account links. Shopping and Performance Max campaigns are built and managed through PaidSync's Google Ads tools in the same session. The merchant_create_link tool wires Merchant Center to Google Ads, and a Google Ads admin must approve that link inside the Google Ads UI before Shopping ads can serve.
Is there an official Merchant Center MCP server from Google?
Not as of August 2026. Google's official open-source MCP server, announced October 7, 2025, covers Google Ads API queries only and is read-only. Its GitHub repository exposes query tools and makes no mention of Merchant Center products, feeds, or disapprovals. PaidSync ships a 15-tool Merchant Center group built on Google's Merchant API.
Is it safe to give Claude write access to my product feed?
Writes are approval-gated. Every mutation supports a dry-run preview so you see exactly what would change before it does, and destructive operations like deleting a product or removing a Google Ads link require explicit confirmation. Authorization runs through Google OAuth, your credentials never touch Claude, and you can revoke the session at any time from the PaidSync dashboard.
How much does it cost to connect Merchant Center to Claude?
The PaidSync free plan is $0 with 15 tool calls a month, enough to connect and run a small audit. Pro starts at $99 a month for 600 tool calls, with 1,200 calls at $149 and 4,000 at $199. Team plans start at $249 a month. A full catalog audit on a large feed uses paginated calls, so heavy use fits Pro better than Free.
Your feed has issues you have not seen yet. Ask Claude to find them.
Connect Merchant Center free Browse free PPC tools