Google Merchant Center MCP Server
15 Merchant Center tools your AI agent can call today. Product upserts, supplemental feeds, disapproval diagnosis, and Google Ads link management, in the same session as 140+ Google Ads tools. Every write approval-gated.
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: 15 Merchant Center tools covering product upserts, supplemental feeds, disapproval diagnosis, and Merchant Center to Google Ads links, inside the same endpoint as 140+ Google Ads tools. Reads run freely; writes preview with dry_run and wait for your confirmation.
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 UIs: 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 disapproved products still sit in active Shopping campaigns, drafts the title fixes, previews the upserts, and applies them after you approve. This page lists the exact 15 tools, what agents can do with them, where the write access honestly stops, and how the PaidSync stack compares with what Google itself ships.
The 15 Merchant Center tools by category
PaidSync's live registry counts 15 Merchant Center tools inside its 430+ tool, 13-platform endpoint. Four categories.
| 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 |
list_merchant_accounts | Lists the Merchant Center accounts your Google login can access | Read | |
set_active_merchant_account | Pins the session to one merchant ID so later calls need no ID argument | Session | |
get_merchant_account_status | Account health, policy flags, and whether a Google Ads link is live | Read | |
| Products and feed health | list_merchant_products | Lists catalog products with approval status, paginated for large feeds | Read |
list_merchant_disapproved_products | Filters to disapproved products with the reason for each | Read | |
get_merchant_center_feed_status | Feed processing status: items processed, items with issues, fetch errors | Read | |
merchant_list_data_sources | Lists primary and supplemental data sources feeding the account | Read | |
| Product writes and supplemental feeds | validate_merchant_products_dryrun | Validates a product payload before anything is written | Read |
merchant_insert_product | Upserts a product: inserts it, or replaces the version with the same ID | Write | |
merchant_delete_product | Removes a product from the feed. Destructive, so it is confirmation-gated | 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 approved links between this Merchant Center and Google Ads accounts | Read |
merchant_create_link | Creates the Merchant Center to Google Ads link Shopping campaigns require | Write | |
merchant_delete_link | Removes a link. Held out of the default toolset because it breaks serving | Write |
What agents can do with these tools
Product upserts
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_merchant_disapproved_products, drafts corrected payloads, checks them with validate_merchant_products_dryrun, and upserts with merchant_insert_product once you approve. Upsert means insert or replace: a product with the same ID is overwritten, a new ID is added. The worked example lives in our guide to optimizing a Shopping feed and Performance Max with AI.
Supplemental feeds
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 them as secondary sources linked on top of a primary one. merchant_create_supplemental_feed creates that source through the API, and merchant_list_data_sources shows what is already feeding the account. Typical use: a custom_label sweep that groups products by margin band so Performance Max can bid them differently.
Link management
No Merchant Center to Google Ads link, no Shopping ads. merchant_list_links diagnoses the state and merchant_create_link creates the link without leaving the chat. One honest nuance we learned running this in production: the Merchant API only returns approved links. A link that is still pending on the Google Ads side shows in the Merchant Center UI but not in the API, so the agent will tell you to finish the approval inside Google Ads under Tools, then Linked accounts.
Cross-platform questions
Because the same endpoint carries 140+ Google Ads tools, the agent can answer the question neither UI answers alone: how much did Shopping campaigns spend last month on products that are disapproved today? Feed status from Merchant Center, spend from Google Ads, joined in one reply. The full setup walkthrough is in our Google Merchant Center MCP connection guide.
Read and write boundaries
Plainly stated, because agent write access to a live product feed deserves plain statements.
- Reads are open. Accounts, products, disapprovals, feed status, data sources, and links can be queried freely within your plan's call allowance.
- Writes preview first. Mutation tools default to a dry_run that shows exactly what would change before anything does.
- Destructive actions ask twice. Deletes require an explicit confirmation flag on top of the preview.
- The riskiest tool is buried.
merchant_delete_linkis deliberately excluded from the default toolset, because deleting a link stops Shopping ads from serving. - You hold the kill switch. Sessions are revocable from the PaidSync dashboard at any time, per connected platform.
Connect Merchant Center and Google Ads to Claude or ChatGPT in about five minutes.
Start free, 15 calls, no card See pricingThe official Google stack
Google publishes an open source MCP server for the Google Ads API, announced October 7, 2025 on the Google Ads developer blog. It is read-only and it covers the Google Ads API. It does not cover Merchant Center. As of August 2026 there is no official Merchant Center MCP server; the Merchant API is a REST API you integrate yourself, and you host your own keys, OAuth, and infrastructure.
One date matters for anyone building on the older path. Google sunsets the Content API for Shopping on August 18, 2026, replaced by the Merchant API. Any Merchant Center tooling still wired to the Content API stops working that day.
Stack 2 of 2The PaidSync stack
PaidSync is a hosted MCP server. One endpoint, one OAuth connection per platform, 430+ tools across 13 platforms, of which 15 are Merchant Center. The merchant tools run against the current Merchant API, so the Content API sunset does not touch them. Unlike the official stack, PaidSync writes: upserts, supplemental feeds, and link creation, all behind the approval gates above. It works in Claude, ChatGPT, Gemini, Copilot, Perplexity, and code-first clients like Claude Code and Cursor. Six agencies became paying customers in the first four days after launch in May 2026.
| Dimension | Official Google stack | PaidSync stack |
|---|---|---|
| Merchant Center coverage | None (Ads API only) | 15 tools |
| Write access | Read-only | Read + gated write |
| Hosting | Self-hosted, your keys and infra | Hosted, OAuth from the dashboard |
| Google Ads in same session | Yes (read-only) | Yes, 140+ tools, read + write |
| Other platforms | None | 12 more, incl. Meta (69 tools), LinkedIn (25), GTM (37), GA4 (28), Search Console (6) |
| Cost | Free, open source | Free $0 (15 calls/mo), Pro from $99/mo |
Running both stacks together
This is not either-or. MCP clients mount multiple servers, and a dual-stack setup is reasonable: the official server for raw read-only Google Ads API queries, PaidSync for Merchant Center work and any action that writes. Developers who want zero third parties in the read path get that; the write path still runs through PaidSync's approval gates. If you only ever read Google Ads data and never touch Merchant Center, the official free server alone may be all you need. That is the honest boundary of our pitch.
What this does not do
- It does not create a Merchant Center account, or claim and verify your website. Those steps stay in the Merchant Center UI.
- It does not manage promotions, local inventory, or customer reviews. The 15 tools cover products, feeds, diagnostics, and links.
- It does not host or replace your primary feed. Supplemental sources layer on top of the primary source you already run.
- It does not skip Google's review. An upsert changes what you submit; approval decisions still belong to Google.
- It does not act silently. Every write previews first and waits for you.
Pricing
Merchant Center tools are included in every plan. Calls are metered from one shared pool across all 13 platforms, with no per-platform or per-account surcharge. Full detail on the pricing page.
| Plan | Price | What you get |
|---|---|---|
| Free | $0 | 15 tool calls per month, all 13 platforms, no card required |
| Pro | From $99/mo | 600 calls at $99, 1,200 at $149, 4,000 at $199 |
| Team | From $249/mo | Seats and a shared credit pool for agencies |
| Done For You | Custom | Managed paid media on top of the platform |
Put your Shopping feed one prompt away. Reads are free to try, and every write waits for your approval.
Frequently asked questions
What is a Google Merchant Center MCP server?
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, check feed processing status, 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 UI. PaidSync ships 15 Merchant Center tools inside the same MCP endpoint that also covers Google Ads (140+ tools), Meta, LinkedIn, GA4, GTM, and 7 more platforms.
Can an AI agent write to Merchant Center through PaidSync?
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 Merchant Center to Google Ads links. Every write is approval-gated: tools default to a dry_run preview, destructive actions require explicit confirmation, and merchant_delete_link is deliberately held out of the default toolset. Reads cover accounts, products, disapprovals, feed status, data sources, and links.
Is there an official Google Merchant Center MCP server?
Not as of August 2026. Google's official open source MCP server, announced October 7, 2025 on the Google Ads developer blog, covers the Google Ads API and is read-only. It does not cover Merchant Center. The Merchant API itself is a REST API you would have to integrate yourself. PaidSync is a hosted MCP server that includes 15 Merchant Center tools alongside its Google Ads tools.
What happens when the Content API for Shopping shuts down on August 18, 2026?
Google is sunsetting the Content API for Shopping on August 18, 2026 and replacing it with the Merchant API, per developers.google.com/merchant/api. Tools built on the old Content API stop working on that date. PaidSync's Merchant Center tools run against the current Merchant API, so the sunset does not interrupt them.
What does the Merchant Center MCP cost?
Merchant Center tools are included in every PaidSync plan. Free is $0 with 15 tool calls per month and no card required. Pro starts at $99 per month for 600 calls, with 1,200 calls at $149 and 4,000 calls 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.
What can the Merchant Center tools not do?
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.
Which AI clients can use the Merchant Center MCP?
Any MCP-compatible client. PaidSync publishes setup guides for Claude, ChatGPT, Gemini, Copilot, 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 15 tools. Sessions can be revoked from the dashboard at any time. Start with the Merchant Center to Claude guide.