PaidSync is the only advertising MCP server with native Google Merchant Center integration. 16 tools cover account health, product listing, disapproval diagnosis, feed status, and account-level diagnostics. Connect your Shopping feed to Claude or ChatGPT through the same MCP endpoint that also connects Google Ads, Meta Ads, and 5 other platforms. Adzviser offers Merchant Center data routing, but no native MCP server exists for Merchant Center outside of PaidSync.
Google Merchant Center is where Shopping campaigns live or die. A product that is disapproved does not appear in Shopping results, regardless of how well the Google Ads campaign is optimized. Feed quality issues silently shrink the product pool available for Shopping campaigns. Most advertisers check Merchant Center occasionally, not systematically, because moving between Merchant Center and Google Ads to correlate data is slow and disconnected.
PaidSync connects both in the same session. The AI can ask "which of my disapproved products are currently in active Shopping campaigns?" because it has access to both the Merchant Center product status and the Google Ads campaign product group. That cross-platform question was previously only answerable through manual data exports and spreadsheet joins.
PaidSync's Content API for Shopping integration exposes the following tools:
connect_merchant_center
Connects your Merchant Center account over Google OAuth. One-time setup; the connection is scoped to Content API access and can be revoked at any time.
list_merchant_accounts
Returns every Merchant Center account your Google login can reach, so multi-account operators pick the right one before doing anything else.
set_active_merchant_account
Binds one Merchant Center account for the session. Every later call runs against this account, so multi-store setups never mix catalogs.
merchant_auth_status
Reports the health of the Merchant Center connection itself: whether the token is valid and which account is currently bound. The first thing to check when a call fails.
get_merchant_account_status
Returns account-level status: policy compliance, active warnings, and critical account flags. Surfaces account suspension risks before they become suspensions.
list_products
Returns products in the catalog with their approval status, disapproval reasons, and availability. Supports pagination for large catalogs.
list_product_issues
Returns active product issues with the Merchant Center issue code, severity, affected attribute, and what to fix. The primary tool for disapproval diagnosis, and it groups products that share the same fix.
get_product_performance
Returns Shopping performance metrics for products including impressions, clicks, and click-through rate from Merchant Center's performance data.
list_plannable_products
Returns the products currently eligible to serve in Shopping, the inventory a campaign plan can actually draw on rather than the raw catalog count.
merchant_list_data_sources
Lists the registered data sources, primary and supplemental feeds alike, with their format and processing state. Critical for diagnosing feed processing failures.
merchant_create_supplemental_feed
Creates a supplemental feed, the standard way to patch attributes (titles, GTINs, custom labels) on top of a primary feed you cannot or should not edit directly.
merchant_insert_product
Inserts or updates a single product (upsert). Used to fix a disapproved product's attributes directly from chat once the issue is diagnosed.
merchant_delete_product
Removes a product from the catalog. Destructive, so it is approval-gated like every write in PaidSync.
merchant_list_links
Returns the accounts linked to this Merchant Center, including Google Ads links, with their status. Broken links are a silent killer of Shopping campaigns.
merchant_create_link
Creates an account link, most commonly Merchant Center to Google Ads, so Shopping campaigns can serve from the catalog.
merchant_delete_link
Removes an account link. Destructive and approval-gated.
16 Merchant Center tools. Connect your Shopping feed to Claude. Free tier, no card needed.
Start Free Book a DemoSign up at paidsync.ai/signup. Free tier. No credit card. Get your MCP key immediately.
In the PaidSync dashboard, click Connect next to Google Merchant Center. Authorize with the Google account that has admin or standard access to your Merchant Center. PaidSync requests read access to Content API for Shopping.
In Claude's integrations settings, add a new MCP server:
Once connected, these prompts work immediately:
PaidSync connects Google Ads (134 tools) and Merchant Center (16 tools) in the same session. The combination enables questions that require data from both platforms:
Spend on broken products. "How much did my Google Ads Shopping campaigns spend last month on products that are now disapproved in Merchant Center?" The AI pulls Shopping campaign product-level spend from Google Ads and matches it against current Merchant Center disapproval status. The number is usually surprising.
Missing products in campaigns. "Which of my approved Merchant Center products have zero impressions in Shopping campaigns?" Identifies products that are technically available but not getting into auctions, possibly due to product group exclusions or bid settings.
Feed quality to ROAS correlation. "Which product categories in my Merchant Center have the lowest data quality scores, and how do their Shopping ROAS figures compare to high-quality categories?" Connects feed health to campaign performance to prioritize feed improvement work by revenue impact.
This analysis was previously only possible by exporting data from both platforms, joining the datasets manually, and building a report. With PaidSync, it happens in one conversation.
Adzviser offers data routing that includes some Merchant Center metrics alongside other Google platforms. Their approach is analytics-focused: pull data, build reports, surface insights. PaidSync's 16 Merchant Center tools are more granular and action-oriented: list specific products, get issue codes, pull feed processing logs, cross-reference with campaigns.
Neither Adzviser nor any other advertising MCP server documents a native Merchant Center integration with the tool depth that PaidSync provides. As of May 2026, PaidSync's 16-tool Merchant Center integration is the only one of its kind in the advertising MCP category. For the full cross-platform picture, see the Merchant Center to Claude connection guide.
Yes. PaidSync has 16 Google Merchant Center tools available through its MCP server. These tools cover account health checks, product listing, disapproval diagnosis, feed status monitoring, and account-level diagnostics. Connect your Merchant Center to Claude or ChatGPT at https://mcp.paidsync.ai/mcp.
With PaidSync's 16 Merchant Center tools, Claude can get account status and policy compliance, list all products with their approval status, pull all products with active disapprovals and their reasons, check feed health and data quality scores, get account-level diagnostics and warnings, and filter products by disapproval type to prioritize fixes.
Adzviser offers some Merchant Center data access for reporting purposes. PaidSync is the only advertising MCP server with 16 dedicated Merchant Center tools covering product health, disapprovals, and feed diagnostics alongside the other 6 advertising platforms in one connection.
PaidSync's 16 Merchant Center tools are read-focused: they surface what is wrong and why. The AI can precisely diagnose why products are disapproved, which attribute is causing the issue, and what the fix looks like. Applying the fix typically requires updating the product feed in your CMS or e-commerce platform.
Yes. PaidSync connects Google Ads and Merchant Center in the same session. The AI can cross-reference Shopping campaign performance data from Google Ads (134 tools) with product feed health from Merchant Center (16 tools) to identify which disapproved products are affecting live campaigns.
Yes. PaidSync uses Google's official Content API for Shopping to access Merchant Center data. The integration uses OAuth 2.0 with user consent and does not use undocumented endpoints. Access is read-only for product and account data.
Sign up at paidsync.ai/signup (free tier, no card required), connect Merchant Center via OAuth in the dashboard, then add the MCP server URL to Claude. The full connection guide is at paidsync.ai/docs.
16 Merchant Center tools. Connect Shopping feed to Claude. 400+ total tools across 13 platforms.
Get Started Free Book a Demo