A Google Merchant Center MCP server connects an AI assistant like Claude or ChatGPT to your Shopping feed over the Model Context Protocol, so the agent can read product status and change feed data by calling named tools. PaidSync ships one today: 16 Merchant Center tools covering product upserts and deletes, supplemental feeds, disapproval diagnosis, product performance and Merchant Center to Google Ads links, inside the same endpoint as 158 Google Ads tools. Reads run freely. Merchant Center writes have no dry_run preview, so over MCP your assistant's own confirmation prompt is the check before a write runs.
Merchant Center is where Shopping and Performance Max live or die. A disapproved product serves nothing, no matter how well the campaign above it is tuned. The usual workflow splits across two interfaces: diagnose in Merchant Center, act in Google Ads, and export spreadsheets to connect the two.
An MCP server collapses that into one conversation. The agent checks which products carry disapprovals, reads how they performed, drafts the title fixes, and applies the upserts after you say yes in your assistant. This page lists the exact 16 tools, what agents can do with them, where the write access honestly stops, and how the PaidSync stack compares with what Google itself ships.
PaidSync's registry counts 16 Merchant Center tools inside its 630+ tool, 14-platform endpoint, in four groups.
| Category | Tool | What it does | Read or write |
|---|---|---|---|
| Account and session | connect_merchant_center | Starts the OAuth flow that authorizes PaidSync on your Merchant Center | Setup |
merchant_auth_status | Shows whether Merchant Center is connected and when the token expires | Read | |
list_merchant_accounts | Lists Merchant Center accounts across every connected Google login, including sub-accounts under a multi-client account | Read | |
set_active_merchant_account | Pins the session to one merchant account, the account later calls act on | Session | |
register_gcp_developer | One-time registration the Merchant API requires before per-account calls work. It normally runs on its own | Setup | |
get_merchant_account_status | Account health: open issues, severity, country impact, and whether a Google Ads link is live | Read | |
| Products and performance | list_products | Lists catalog products with title, brand, price, availability and feed label, paginated for large feeds | Read |
list_product_issues | Lists product disapprovals and warnings with issue code, severity, destination, country and the fix | Read | |
get_product_performance | Product-level Shopping clicks, impressions, CTR and conversions, with a one to two day delay | Read | |
merchant_list_data_sources | Lists the primary and supplemental data sources feeding the account | Read | |
| Product writes and supplemental feeds | merchant_insert_product | Upserts a product: inserts it, or replaces the version with the same offer ID, language and feed label | Write |
merchant_delete_product | Removes a product input. Shopping ads that reference it stop showing | Write | |
merchant_create_supplemental_feed | Creates a supplemental data source for price, title or custom label overrides | Write | |
| Google Ads links | merchant_list_links | Lists the service links, such as Google Ads, attached to this Merchant Center | Read |
merchant_create_link | Requests the Merchant Center to Google Ads link that Shopping and Performance Max need | Write | |
merchant_delete_link | Removes a link, which stops the Shopping ads that depend on it | Write |
Google now ships two MCP pieces near this job. The Merchant API MCP Access Service, listed under May 2026 on the Merchant API updates page, is a hosted endpoint at merchantapi.googleapis.com/mcp. It is an alpha. Google limits it to read-only tools and low-risk writes such as data source creation, and documents setup for Antigravity, the Claude CLI and cURL, signed in with your own OAuth token or service account and a Google Cloud project. It shares quota with your standard Merchant API calls, and Google recommends testing on a non-live account first. Separately, Google's open-source Google Ads API MCP server, announced October 7, 2025 on the Google Ads developer blog, is read-only and covers Google Ads, not Merchant Center.
One date matters for anyone still on the older path. Google sunset the Content API for Shopping on August 18, 2026, replaced by the Merchant API, and Content API requests have faced progressive errors since September 1, 2026.
Stack 2 of 2PaidSync is a hosted MCP server. One endpoint, one OAuth connection per platform, 630+ tools across 14 platforms, of which 16 are Merchant Center. The merchant tools run against the Merchant API, so the Content API sunset does not touch them. Where Google's alpha limits writes to low-risk actions, PaidSync inserts and deletes products, creates supplemental feeds and manages Google Ads links, with your assistant's confirmation prompt as the check over MCP and approval cards in the workspace. It works in Claude, Claude Code, ChatGPT, Gemini, Copilot Studio, Perplexity and Cursor.
| Dimension | Official Google stack | PaidSync stack |
|---|---|---|
| Merchant Center coverage | Merchant API MCP Access Service, alpha, mostly reads | 16 tools |
| Write access | Low-risk writes such as data source creation | Product upserts and deletes, supplemental feeds, Google Ads links |
| Checks before a write | Tools limited to reads and low-risk writes; Google recommends filtering tools in your client | Your assistant's confirmation prompt over MCP; approval cards and undo in the workspace; no dry_run on Merchant Center writes |
| Hosting and sign-in | Hosted by Google; your own OAuth token or service account and Google Cloud project | Hosted, OAuth from the PaidSync dashboard |
| Google Ads in same session | Separate open-source server, read-only | Yes, 158 Google Ads tools, read + write |
| Other platforms | None | 12 more, incl. Meta (92 tools), LinkedIn (34), GTM (39), GA4 (26), Search Console (6) |
| Cost | No fee; calls share your Merchant API quota | Free $0 (15 tasks/mo), Pro from $99/mo |
This is not either-or. MCP clients mount multiple servers, and a dual-stack setup is reasonable: Google's alpha for its own insights, such as popular products, pricing insights and competitive visibility, and PaidSync for product writes, links, and anything that joins Merchant Center with Google Ads or Meta. Developers who want no third party in the read path get that, while the write path runs through PaidSync. If you only ever read Merchant Center data and never change it, Google's endpoint may be all you need. That is the honest boundary of our pitch.
The classic Merchant Center chore is the disapproval batch. Forty products flagged for a title or attribute problem, each needing an edit. Through PaidSync the agent pulls the batch with list_product_issues, reads the current product data with list_products, drafts corrected payloads, and upserts them with merchant_insert_product once you approve in your assistant. Upsert means insert or replace: a product with the same offer ID, language and feed label is overwritten, and a new ID is added. Each upsert goes straight back into Google's review. The worked example lives in our guide to optimizing a Shopping feed and Performance Max with AI.
When you want to override prices, titles, or custom labels without touching the primary feed your platform generates, the right instrument is a supplemental data source. Google's own Merchant API data sources documentation describes supplemental sources as ones that update existing product data and are linked to a primary source. merchant_create_supplemental_feed creates that source through the API, and merchant_list_data_sources shows what already feeds the account. Typical use: a custom_label sweep that groups products by margin band so Performance Max can bid them differently.
No Merchant Center to Google Ads link, no Shopping ads. get_merchant_account_status and merchant_list_links show the current state, and merchant_create_link requests the link without leaving the chat. A new link only serves once the Google Ads admin approves it inside Google Ads, so the agent will tell you to finish that step there.
get_product_performance returns clicks, impressions, CTR and conversions per product from Merchant Center reports, so the agent can find your top and bottom SKUs. Because the same endpoint carries 158 Google Ads tools, it can also work through the question neither interface answers alone: how much did Shopping campaigns spend last month on products that carry a disapproval today? Feed status from Merchant Center, spend from Google Ads, joined in one reply. The full setup walkthrough is in our Merchant Center and Claude connection guide.
Plainly stated, because agent write access to a live product feed deserves plain statements.
Connect Merchant Center and Google Ads to Claude or ChatGPT with one sign-in each.
Start free, 15 tasks, no card See pricingMerchant Center tools are included in every plan. Tasks come from one shared allowance across all 14 platforms, with no per-platform or per-account surcharge. Full detail on the pricing page.
| Plan | Price | What you get |
|---|---|---|
| Free | $0 | 15 tasks per month, all 14 platforms, no card required |
| Pro | From $99/mo | 600 tasks at $99, 1,200 at $149, 4,000 at $199 |
| Team | From $249/mo | 5 seats and 6,000 shared tasks, with larger seat tiers for agencies |
| Done For You | Custom | Managed paid media on top of the platform |
Put your Shopping feed one prompt away, starting on the free plan.
One setup per client, same endpoint and sign-in everywhere.
It is a Model Context Protocol server that connects an AI assistant like Claude or ChatGPT to your Google Merchant Center account. The AI can then list products, diagnose disapprovals, read product performance, upsert product data, create supplemental feeds, and manage the link between Merchant Center and Google Ads by calling named tools instead of you clicking through the Merchant Center interface. PaidSync ships 16 Merchant Center tools inside the same MCP endpoint that also covers Google Ads (158 tools), Meta, LinkedIn, GA4, GTM, and 8 more platforms.
Yes, within stated limits. Agents can upsert products (merchant_insert_product), delete products, create supplemental feeds for price, title, or custom label overrides, and create or delete Merchant Center to Google Ads links. Over MCP, your assistant's own confirmation prompt is the human check, and PaidSync writes no approval card on that path. Merchant Center writes have no dry_run preview and apply on the first call, and product and link deletes need no confirm_destructive flag, so that prompt is the only check. Reads cover accounts, products, product issues, performance, data sources, and links.
Yes. Google runs an official Merchant Center MCP server in alpha since May 2026 (checked 29 Sep 2026). Google's alpha has 13 tools, limited to reads and low-risk changes such as creating data sources. 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.
Google sunset the Content API for Shopping on August 18, 2026 and replaced it with the Merchant API, per developers.google.com/merchant/api, and Content API requests have faced progressive errors since September 1, 2026. Tools built on the old Content API stop working. PaidSync's Merchant Center tools run against the Merchant API, so the sunset does not interrupt them.
Merchant Center tools are included in every PaidSync plan. Free is $0 with 15 tasks per month and no card required. Pro starts at $99 per month for 600 tasks, with 1,200 tasks at $149 and 4,000 tasks at $199. Team starts at $249 per month. Done For You is custom pricing with a managed service. There is no per-platform or per-account surcharge.
They do not create a Merchant Center account, claim or verify your website, or manage promotions, local inventory, or customer reviews. They do not host or replace your primary feed; supplemental feeds layer on top of the primary source you already run. And an upsert changes what you submit to Google, it does not skip Google's review. Approval decisions still belong to Google.
Any MCP-compatible client. PaidSync publishes setup guides for Claude, ChatGPT, Gemini, Copilot Studio, and Perplexity, plus code-first clients like Claude Code and Cursor. You connect Merchant Center once via OAuth in the PaidSync dashboard, then every client that mounts the endpoint can use the 16 tools. Disconnecting Merchant Center from the dashboard deletes its tokens. Start with the Merchant Center to Claude guide.