ecompick.
For makers中文Submit a tool

Popular seller tasks

Product & keyword researchListings & product copyProduct photosProduct video & ad creativeAdvertising & PPCEmail & marketing

Google Merchant Center MCP

Inspect product records and feed-related issues

Open sourceAny store
#mcp
Visit website

Overview

This community Python server connects assistants to Google Merchant API v1. It focuses on shopping feeds, product diagnostics and account operations rather than general web search.

Who it suits

Merchants or feed specialists with Merchant Center access who need to diagnose disapproved products, inspect Shopping performance, or prepare controlled product-feed corrections.

Who it may not suit

Advertisers whose question is about campaign bids or budgets rather than Merchant Center products, or users without permission to access the merchant account.

Seller use cases

  • Group disapproved products by issue to prepare a feed-repair queue for the catalog team.
  • Compare a store export with Merchant Center product records to identify missing items or conflicting attributes.
  • Inspect product-performance reports before selecting feed changes to investigate, keeping reporting periods consistent.

What you can do

  • Inspect product records and feed-related issues. ↗
  • Query Merchant Center reports for shopping diagnostics. ↗
  • Manage supported inventory and promotion resources. ↗

What you need

  • Python, a Merchant Center account and authorized service-account or OAuth credentials.

Install

Local MCP

pip install gmc-mcp
# Configure the required Merchant Center credentials before running.
gmc-mcp run
Installation source ↗

Permissions & data

Runs Python locally, reads credential files and calls merchantapi.googleapis.com. It writes audit records and may save refreshed OAuth credentials.

Project info

Maintainer
kiwoongeom
GitHub stars at check date
19
Last commit
2026-05-02
License
MIT
Last checked
2026-10-30
GitHub ↗

Pricing at a glance

The gmc-mcp package is MIT-licensed and runs locally in Python. It does not supply Merchant Center credentials, paid advertising, or a hosted feed-management subscription; those account and operating arrangements remain yours.

Open source

Good to know

Feed changes can affect product eligibility and displayed price or availability. Use the documented dry-run and audit facilities, check affected product IDs, and verify the resulting Merchant Center status after a write.

Alternatives to Google Merchant Center MCP

Agentic Commerce Skills inspect shopping-agent readiness and protocol integration, rather than managing a Merchant Center feed.

GeLi2001 checks source catalog records in Shopify; gmc-mcp checks the corresponding Google merchant-side representation.

Google Ads MCP queries advertising performance, while this connector inspects the product data and eligibility underlying Shopping listings.

Frequently asked questions

Does it use the Google Ads API?

This project targets Merchant API v1 for Merchant Center. Campaign reporting and bid-management questions belong to the advertising API rather than this product-feed connection.

Can a write be previewed?

The README documents dry-run controls, an audit log, and confirmation requirements for destructive bulk operations. Inspect the proposed scope before allowing a feed change.

Does a corrected feed guarantee Shopping approval?

No. The connector can read issues and change supported resources, but Google’s review and product-policy decisions remain separate from an API request succeeding.

Where is the feed audit trail stored?

The local implementation writes audit records and may save refreshed OAuth credentials. Review its storage configuration and protect those files, especially when running shared feed-maintenance jobs.

Checked against the official site on 2026-10-30 · Official source ↗

Sources