Gmc Mcp
Let your agent manage Google Merchant Center catalogs, feeds, and Merchant API v1 operations through 126 structured MCP tools instead of clicking the console.
Overview
gmc-mcp is a MCP server for the Grow phase that exposes 126 tools for Google Merchant Center via Merchant API v1 with pip stdio and service-account or OAuth auth.
What is this MCP server?
- 126 MCP tools covering Google Merchant Center on Merchant API v1
- pip-installable gmc-mcp package (MIT licensed, v0.2.5)
- stdio transport with service-account or OAuth user token auth paths
- Supports MCA sub-accounts via optional GMC_SUBACCOUNT_ID
- GMC_DRY_RUN and gmc-mcp auth-init for safer agent-driven changes
- 126 MCP tools for Merchant API v1
- PyPI package gmc-mcp version 0.2.5
Community signal: 1 GitHub stars.
What problem does it solve?
Maintaining Merchant Center feeds and account settings by hand—or with brittle custom scripts—does not scale when an agent could enforce feed rules but lacks a typed API bridge.
Who is it for?
Indie ecommerce founders who already use Google Merchant Center and want Claude Code or Cursor to automate catalog and feed operations safely.
Skip if: Builders with no Google Shopping footprint or teams unwilling to grant Merchant Center admin to a service account or OAuth user.
What do I get? / Deliverables
After configuring GMC credentials and registering gmc-mcp, your agent can call Merchant API operations through MCP tools to update catalogs and diagnose feed issues faster.
- MCP tool surface for Merchant Center API v1 operations
- Agent-ready catalog and feed management workflows with optional dry-run
Recommended MCP Servers
Journey fit
Grow/lifecycle is the canonical shelf because Merchant Center work optimizes product presence and feed health after you have something to sell, not while you are only ideating. Lifecycle covers ongoing catalog updates, account linking, and feed fixes that compound visibility for solo ecommerce operators.
How it compares
Merchant API MCP bridge with 126 tools, not a storefront theme or ad creative generator.
Common Questions / FAQ
Who is gmc-mcp for?
Solo sellers and small teams who operate a Google Merchant Center account and want MCP-native automation for feeds and catalog tasks.
When should I use gmc-mcp?
Use it when you need agent-driven product feed fixes, Merchant API v1 tasks, or repeatable catalog updates after your store is live on Google Shopping surfaces.
How do I add gmc-mcp to my agent?
pip install gmc-mcp, set GMC_ACCOUNT_ID and either GMC_SERVICE_ACCOUNT_KEY or GMC_OAUTH_TOKEN from gmc-mcp auth-init, add the stdio server to your MCP config, and use GMC_DRY_RUN while testing.