To connect Google Merchant Center to Claude, open Settings, then Connectors in Claude, search PaidSync, click Connect, and sign in with your PaidSync login (OAuth 2.0). Then authorize Merchant Center in the PaidSync dashboard. Claude gets 16 Merchant Center tools to audit your feed, triage disapprovals, and fix product data from chat. Every write is held for your approval before it runs.
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 two-minute setup, the Merchant Center to Claude connect page has it. This page is for the day after setup, when you want the feed actually fixed.
Under the hood, PaidSync's Merchant Center group runs on Google's Merchant API, the successor to the Content API for Shopping, which Google retired on August 18, 2026. Tools built on the old Content API stopped working on that date. These did not.
Go to paidsync.ai/signup and sign up with Google or email. You land on the free plan. No credit card.
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.
In claude.ai or the Claude Desktop app, open Settings, then Connectors, search PaidSync and click Connect, then sign in with your PaidSync login. That OAuth sign-in is what lets Claude apply changes. Connectors work on every Claude plan, including Free, which allows one custom connector. Using Claude Code? Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then type /mcp inside a session to sign in.
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 task after that runs against that account until you switch.
PaidSync ships 470+ tools across 14 platforms. The Merchant Center group is 16 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, register_gcp_developer | Authorize, pick the merchant ID, check account health, register the API access once if the automatic step failed |
| 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 tasks a month, no card.
Get started for free See pricingThree workflows cover most of what Shopping advertisers actually need from Merchant Center. Each maps to specific tools, so you can verify what ran.
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.
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.
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.
merchant_create_link requests 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.get_product_performance reads Merchant Center Reports, which run one to two days behind. For same-day spend questions, use the Google Ads reporting tools instead.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 MCPs. Google's Google Ads MCP server is strictly read-only, 3 tools, self-hosted, and has no Merchant Center tools. The Merchant API MCP Access Service (merchantapi.googleapis.com/mcp) is in alpha with 14 tools, read-mostly with limited writes, listed under May 2026. Neither writes product data with an approval step in front of it. Checked September 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.
Working in the terminal? Claude Code connects to the same PaidSync server with one command:
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcpStart a session, type /mcp, pick paidsync, and sign in with your PaidSync login in the browser window that opens. Claude Code stores the OAuth token for you. No key is pasted anywhere. The Claude Code setup page covers the shared .mcp.json for teams and a headless audit run.
Create a free PaidSync account at paidsync.ai/signup and click Connect Google Merchant Center in the dashboard to authorize via Google OAuth. Then in Claude open Settings, then Connectors, search PaidSync, click Connect, and sign in with your PaidSync login. Setup takes about five minutes and needs no code. The free plan is $0 with 15 tasks a month.
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.
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.
Yes, in alpha. Google lists a Merchant API MCP Access Service at merchantapi.googleapis.com/mcp under May 2026, with 14 tools, read-mostly with limited writes. Google's separate Google Ads MCP server is strictly read-only, 3 tools, self-hosted, and has no Merchant Center tools. PaidSync ships a 16-tool Merchant Center group on Google's Merchant API, with approval-gated product and feed writes, next to Google Ads, GA4, and GTM in the same session. Checked September 2026.
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.
The PaidSync free plan is $0 with 15 tasks a month, enough to connect and run a small audit. Pro starts at $99 a month for 600 tasks, with 1,200 tasks 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