How to connect Google Merchant Center to Claude, in order: open PaidSync.ai in Claude's connector directory and click Connect, sign in to PaidSync.ai (free, no credit card) and press Approve, then ask Claude to connect your Merchant Center account. No API key is needed and setup takes under 5 minutes; Claude can then 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. Google runs an official Merchant Center MCP server in alpha since May 2026, limited to reads and low-risk changes such as creating data sources (13 tools). PaidSync gives you 16 Merchant Center tools next to your Google Ads Shopping campaigns in one chat, and can insert, update and delete products, add supplemental feeds and link Google Ads when you ask. 630+ tools across 14 platforms, one connection. Free plan is $0 with 100 tasks a month, worth $50. Pro starts at $99 for 1,000 tasks, with options up to $199 for 6,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
Google runs an official Merchant Center MCP server in alpha since May 2026, limited to reads and low-risk changes such as creating data sources (13 tools). PaidSync gives you 16 Merchant Center tools next to your Google Ads Shopping campaigns in one chat, and can insert, update and delete products, add supplemental feeds and link Google Ads when you ask. 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.
How to Connect Google Merchant Center to Claude in 3 Steps
The entire setup takes under 5 minutes. No coding, no config files, and no API key, because Claude connects with a PaidSync sign-in (OAuth).
Before you start
- Any Claude plan works, including Free, and there is nothing to install.
- Signing in with Google? There is no separate sign-up. You pick Continue with Google in step 2, and your free PaidSync account (100 tasks a month, no credit card) is created when you press Approve.
- Prefer an email and password? Create the account at paidsync.ai/signup first. The sign-up link inside the sign-in window opens the website and does not bring you back to Claude.
- Know which Google login can open your Merchant Center account. You use it in step 3.
- On a Team or Enterprise plan, an Owner first adds PaidSync for the organization under Organization settings, then Connectors. Each person then connects with their own PaidSync login.
Add PaidSync to Claude from the connector directory
Open PaidSync in Claude's connector directory and click Connect. Or, in claude.ai or the Claude Desktop app, open Customize, then Connectors, click + next to Connectors, search PaidSync, and click Connect. Connectors work on every Claude plan, including Free.
On a client with no directory, add PaidSync as a custom connector with the server URL https://mcp.paidsync.ai/mcp instead. Using Claude Code? Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then type /mcp inside a session to sign in.
Sign in to PaidSync and press Approve
The PaidSync sign-in screen opens. Pick Continue with Google, or sign in with your PaidSync email and password. A PaidSync screen then asks whether to allow Claude to manage your ad accounts via PaidSync. Press Approve and Claude shows PaidSync as connected.
New to PaidSync and signing in with Google? Your free account (100 tasks a month, no credit card) is created when you press Approve. The screen also mentions ad accounts already connected inside PaidSync. On a new account that list is empty until you finish step 3.
Connect your Merchant Center account and ask Claude
In any chat, ask: "Connect my Merchant Center." Claude replies with a link that opens Google's own sign-in and consent screen. Sign in with the Google account that has access to your Merchant Center and approve access. PaidSync asks Google for the content scope, which covers reads and the product and feed changes you ask for. PaidSync never sees your Google password.
Come back and ask: "List my Merchant Center accounts." Claude uses list_merchant_accounts to show them, sub-accounts under a multi-client account included, and set_active_merchant_account to pick the one you name. Connecting accounts and picking one uses none of your tasks. Then try: "Which issues are disapproving the most products?" You can also connect Merchant Center from the PaidSync dashboard instead. Both routes use the same PaidSync login, so Claude sees the account either way.
The 16 Merchant Center Tools Claude Gets
PaidSync ships 630+ 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.
What You Can Ask Claude After Connecting
Each prompt runs on the PaidSync tools named after it and uses one or more of your tasks. Prompts 7 and 8 change your account. The others read and change nothing.
- "Which issues are disapproving the most products in my Merchant Center, and how do I fix each one?" Runs
list_product_issues, which returns each issue's code, severity, destination, country, number of affected products and Google's fix instructions. - "Split my product issues by destination. How many products are affected in free listings and in Shopping ads?" Runs
list_product_issues. - "Audit my Merchant Center account health. What is blocking growth?" Runs
get_merchant_account_status, which returns account-level issues with their severity and country, and whether a Google Ads link is active. - "Which products got impressions but almost no clicks in the last 14 days?" Runs
get_product_performance, which returns clicks, impressions, CTR, conversions and conversion value for up to 1,000 products. Merchant Center reports run one to two days behind. - "Is my Merchant Center linked to my Google Ads account, and is the link approved?" Runs
merchant_list_linksandget_merchant_account_status. - "List my products that are out of stock or have no brand." Runs
list_products, which returns each product's title, brand, price, availability, condition and feed label. - "Create a supplemental feed called Holiday Sale Prices for my US products in English." Runs
merchant_create_supplemental_feed. Merchant Center changes apply on the first call with no preview, so keep Claude's confirmation on. - "Link my Merchant Center to Google Ads account 123-456-7890." Runs
merchant_create_link. A Google Ads admin then approves the link in Google Ads before Shopping ads use the feed.
What This Does Not Do
- 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 Center group feeds the data, and 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 Google's review when it is upserted. Claude fixes the data. It cannot make Google 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.
Why PaidSync Is the Right MCP for Merchant Center on Claude
Three things make PaidSync the practical choice for ecommerce operators running Shopping on Claude.
Merchant Center next to Google Ads. Google runs an official Merchant Center MCP server in alpha since May 2026, limited to reads and low-risk changes such as creating data sources (13 tools). PaidSync gives you 16 Merchant Center tools next to your Google Ads Shopping campaigns in one chat, and can insert, update and delete products, add supplemental feeds and link Google Ads when you ask.
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 (158 tools), Meta Ads (92 tools), LinkedIn Ads (34 tools), TikTok Ads, GTM (39 tools), and GA4 (26 tools). 630+ 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.
Google Merchant Center MCP Options
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 13 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.
Claude Code
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.
Troubleshooting Merchant Center in Claude
- The sign-in fails. Sign in to PaidSync the way you signed up, with Continue with Google or with your PaidSync email and password. Email users without an account create one at paidsync.ai/signup first, then click Connect in Claude again. If Google's own consent screen fails, ask Claude "Connect my Merchant Center" again for a fresh link.
- Claude picked the wrong account. Ask Claude to list your Merchant Center accounts and switch to the one you mean, by name or ID. It runs
list_merchant_accounts, thenset_active_merchant_account, and every Merchant Center request after that goes to the account you picked. Switching uses none of your tasks. - An account is not listed, or requests fail. PaidSync lists the Merchant Center accounts your connected Google login can open, sub-accounts included. Ask an admin of the Merchant Center account to give that login access, then list your accounts again. The first request to an account registers PaidSync with it, which needs admin access and takes about 5 minutes to take effect. Connected with the wrong Google login? Disconnect it in the PaidSync dashboard and connect again with the login that has access.
- Claude says it has no Merchant Center tool. PaidSync shows Claude a short starter list of tools to keep the chat light. Ask Claude to call
paidsync_contextfirst. It returns your connected platforms and the full tool list, Merchant Center included, and Claude then runs those tools throughpaidsync_exec. If PaidSync is missing from Claude altogether, check that it shows as connected under Customize, then Connectors.
Add to ChatGPT: open PaidSync.ai in ChatGPT's plugin directory, install it, then sign in.
Add to Claude: open PaidSync.ai in Claude's connector directory, click Connect, then sign in.
Frequently Asked Questions
Does Claude support Google Merchant Center natively?
No. Claude has no first-party Merchant Center integration. PaidSync is the bridge. Google runs an official Merchant Center MCP server in alpha since May 2026, limited to reads and low-risk changes such as creating data sources (13 tools). PaidSync gives you 16 Merchant Center tools next to your Google Ads Shopping campaigns in one chat, and can insert, update and delete products, add supplemental feeds and link Google Ads when you ask.
What can Claude do with my Merchant Center account?
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.
Is Merchant Center support unique to PaidSync?
No. Google runs an official Merchant Center MCP server in alpha since May 2026, limited to reads and low-risk changes such as creating data sources (13 tools). PaidSync gives you 16 Merchant Center tools next to your Google Ads Shopping campaigns in one chat, and can insert, update and delete products, add supplemental feeds and link Google Ads when you ask.
Is PaidSync free to use with Merchant Center?
Yes. The free plan gives you 100 tasks a month at $0. Pro starts at $99 per month for 1,000 tasks, with options for 2,500 tasks at $149 and 6,000 tasks at $199. Team plans start at $249 per month for 10,000 shared tasks and up to 20 seats. No credit card required to start.
Can Claude also fix disapprovals automatically?
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.
Is there an official Google Merchant Center MCP server?
Yes, in alpha. Google lists a Merchant API MCP Access Service at merchantapi.googleapis.com/mcp under May 2026, with 13 tools, read-mostly with limited writes. Google's separate Google Ads MCP server has 7 tools, is self-hosted and has no Merchant Center tools; since its 2 Nov 2026 release it also creates Google Ads assets and manages labels. 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.
Is it safe to give Claude write access to my product feed?
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.
What Google OAuth scope does PaidSync request for Merchant Center?
PaidSync requests https://www.googleapis.com/auth/content for Merchant Center. That one permission covers reads and writes. PaidSync gives you 16 Merchant Center tools next to your Google Ads Shopping campaigns in one chat, and can insert, update and delete products, add supplemental feeds and link Google Ads when you ask. Writes apply on the first call, so keep Claude's approval prompt on.
Does this work with ChatGPT, Perplexity, and Gemini too?
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.
How do I connect Google Merchant Center to Claude Code?
Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp in the terminal, start a session, type /mcp, pick paidsync and sign in with your PaidSync.ai login in the browser window that opens. Then ask Claude Code to connect your Merchant Center account. No key is pasted anywhere.
How can I query Google Ads, GA4 and Merchant Center live from an AI assistant?
Connect Google Ads, Google Analytics 4 and Merchant Center to PaidSync.ai with Google's own sign-in, then add PaidSync.ai to Claude, Claude Code or ChatGPT. One connection reads all three live in the same chat, so a question such as "Which disapproved products sit in my best Shopping campaigns?" is answered from current data, with no export.
Related Guides
Connect Google Merchant Center to Claude today. Free plan is $0 with 100 tasks a month.
Try PaidSync Free Book a Demo