To connect Google Merchant Center to Claude, sign up for PaidSync.ai (free), authorize Merchant Center in the PaidSync dashboard via OAuth, add https://mcp.paidsync.ai/mcp as a custom connector under Settings, then Connectors, and sign in with your PaidSync login. Setup takes under 5 minutes. Once connected, Claude can audit your product feed, list every disapproved product with reasons, find missing GTINs, run Shopping diagnostics, check account health, and audit how Merchant Center is linked to your Google Ads Shopping campaigns. PaidSync is one of the only MCP servers that ships Google Merchant Center support, alongside Google Ads, Meta, LinkedIn, TikTok, GTM, and GA4. 610+ tools across 14 platforms, one connection. Free plan is $0 with 15 tasks a month. Pro starts at $99 for 600 tasks, with options up to $199 for 4,000 tasks, and Team plans start at $249.
No exports. No tab-switching between Merchant Center, Ads, and a spreadsheet. Ask Claude what's wrong with your feed, and Claude answers with live data.
In MCP terms, PaidSync is a Google Merchant Center MCP server. The same https://mcp.paidsync.ai/mcp endpoint gives Claude, Claude Code and ChatGPT a 16-tool Merchant Center group that reads your product feed and writes to it.
Why this matters
Most MCP servers ship Google Ads and Meta and stop there. PaidSync is one of the few that ships Google Merchant Center. That gap is the moat for any Shopping advertiser. The disapproved-product audit, the GTIN check, the Shopping campaign linking diagnostic. All of it lives inside one chat with Claude.
If you sell physical products and run Google Shopping, this is the integration that saves you a Wednesday morning every week.
The entire setup takes under 5 minutes. No coding, no config files.
Go to paidsync.ai/signup and create your account with Google or email. You land on the free plan with 15 tasks a month at $0. No credit card needed.
From the PaidSync dashboard, click Connect Google Merchant Center. Sign in with the Google account that owns your Merchant Center and authorize PaidSync via OAuth. If you operate multiple Merchant Center accounts under a Multi-Client Account (MCA), the OAuth flow lists every account you can access. Your credentials never touch Claude and are not stored by PaidSync.
In claude.ai or the Claude Desktop app, open Settings, then Connectors, search PaidSync and click Connect. For Claude Code, Cursor, or any client without a directory, add the server URL instead:
https://mcp.paidsync.ai/mcpUsing Claude Code instead? Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then type /mcp inside a session to sign in. Details in the Claude Code section below.
Click Connect and 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.
Open a new Claude chat. Try "List every disapproved product in my Merchant Center and tell me why" to confirm the connection is live. From there Claude has full visibility into your product feed and Shopping account health.
PaidSync ships 610+ tools across 14 platforms. The Merchant Center group is 16 of them, split across four jobs. They run 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.
| 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, and 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 products by clicks and conversions, and map the feed sources |
| Write product data | merchant_insert_product, merchant_delete_product, merchant_create_supplemental_feed | Upsert corrected products, remove dead products, and layer price and title overrides without touching the primary feed |
| Google Ads linking | merchant_create_link, merchant_list_links, merchant_delete_link | Link Merchant Center to the Google Ads account that runs Shopping and Performance Max |
Claude's own confirmation prompt is the human check before a write runs. Merchant Center writes have no dry-run preview and apply on the first call, and deleting a product or removing a Google Ads link needs no confirm flag, so keep Claude's confirmation prompt on for write tools. You can revoke the session from the PaidSync dashboard at any time.
Real prompts you can run the moment you finish setup. PaidSync exposes the Merchant Center API surface that actually matters for Shopping ops.
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.Three things make PaidSync the practical choice for ecommerce operators running Shopping on Claude.
Merchant Center coverage is rare. Most MCP servers stop at Google Ads and Meta. PaidSync ships the Merchant Center surface as one of 14 platforms. That alone makes it the right call for any Shopping advertiser working with Claude.
Feed audit plus campaign audit in one chat. A typical Shopping audit means hopping between Merchant Center, Google Ads, and a spreadsheet. With PaidSync, Claude pulls product status, Shopping campaign performance, and Ads-side waste in the same thread. The handoff disappears.
One MCP URL, 14 platforms. Merchant Center, Google Ads (152 tools), Meta Ads (83 tools), LinkedIn Ads (34 tools), TikTok Ads, GTM (39 tools), and GA4 (25+ tools). 610+ tools, one connection. Claude can move from a feed diagnostic to a Google Ads Performance Max audit to a GA4 funnel report without switching context.
A Google Merchant Center MCP server is what lets an assistant such as Claude or ChatGPT read your product feed and change it. These are the routes that exist, checked September 2026.
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 read-only, has 3 tools, is 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.
PaidSync. The 16-tool Merchant Center group above, with reads and writes on the feed itself, plus the Google Ads, GA4 and GTM groups in the same session, on the one server Claude, Claude Code and ChatGPT connect to. 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.
Fast path. Already decided? Connect Google Merchant Center to Claude in 2 minutes, then come back here for the prompts.
No. Claude has no first-party Merchant Center integration. PaidSync is the bridge. PaidSync is one of the only MCP servers on the market that exposes Google Merchant Center tools, which makes it the practical way to give Claude access to your product feed and Shopping diagnostics.
Claude can list disapproved products and explain why, surface missing or invalid GTINs, find products with low click potential, run Shopping feed diagnostics, pull product status by country, audit Shopping campaign linking, and check Merchant Center account health. Claude confirms write actions before running them.
Largely yes. Most MCP servers cover Google Ads and Meta and stop there. PaidSync ships Google Merchant Center as one of its 14 connected platforms, which means a product feed audit and a Google Ads Shopping campaign audit happen in the same chat. That breadth is the moat.
Yes. The free plan gives you 15 tasks a month at $0. Pro starts at $99 per month for 600 tasks, with options for 1,200 tasks at $149 and 4,000 tasks at $199. Team plans start at $249 per month for 5 seats and 6,000 shared tasks. No credit card required to start.
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 product data with merchant_insert_product, which upserts the corrected product, or layers an override with merchant_create_supplemental_feed. The corrected product re-enters Google's review, so final approval is Google's decision. A fix that belongs in the source feed is still best made in your ecommerce platform.
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 read-only, has 3 tools, is self-hosted and has no Merchant Center tools. PaidSync ships a 16-tool Merchant Center group on Google's Merchant API, with product and feed writes, next to Google Ads, GA4 and GTM in the same session. Checked September 2026.
Over MCP, Claude's own confirmation prompt is the human check on writes. Merchant Center writes have no dry-run preview and apply on the first call, and deleting a product or removing a Google Ads link needs no confirm flag, so that prompt is the only check. Keep it on for write tools. Authorization runs through Google OAuth, your credentials never touch Claude, and you can revoke the session at any time from the PaidSync dashboard.
Yes. The same PaidSync MCP URL works in Claude Desktop, Claude.ai, ChatGPT, Perplexity, Gemini, Cursor, Windsurf, and Claude Code. Set up PaidSync once and reuse it across every AI client you use.
Connect Google Merchant Center to Claude today. Free plan is $0 with 15 tasks a month.
Try PaidSync Free Book a Demo