Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Gmc MCP

by kiwoongeomversion 0.2.6i★ –iRuns on your computer
Registry nameio.github.kiwoongeom/gmc-mcp

Install

Overview

Description from the maker (original English)

MIT-licensed pip-installable MCP for Google Merchant Center on Merchant API v1 (126 tools).

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Online shops & payments
  • You need to fill in: GMC_ACCOUNT_ID, GMC_SERVICE_ACCOUNT_KEY, GMC_OAUTH_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: GMC_ACCOUNT_ID, GMC_SERVICE_ACCOUNT_KEY, GMC_OAUTH_TOKEN, GMC_SUBACCOUNT_ID, GMC_DRY_RUN, GMC_LOG_LEVEL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "gmc": {
      "command": "uvx",
      "args": [
        "gmc-mcp"
      ],
      "env": {
        "GMC_ACCOUNT_ID": "your-value",
        "GMC_SERVICE_ACCOUNT_KEY": "your-value",
        "GMC_OAUTH_TOKEN": "your-value",
        "GMC_SUBACCOUNT_ID": "your-value",
        "GMC_DRY_RUN": "your-value",
        "GMC_LOG_LEVEL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add gmc --env GMC_ACCOUNT_ID=your-value --env GMC_SERVICE_ACCOUNT_KEY=your-value --env GMC_OAUTH_TOKEN=your-value --env GMC_SUBACCOUNT_ID=your-value --env GMC_DRY_RUN=your-value --env GMC_LOG_LEVEL=your-value -- uvx gmc-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gmc": {
      "command": "uvx",
      "args": [
        "gmc-mcp"
      ],
      "env": {
        "GMC_ACCOUNT_ID": "your-value",
        "GMC_SERVICE_ACCOUNT_KEY": "your-value",
        "GMC_OAUTH_TOKEN": "your-value",
        "GMC_SUBACCOUNT_ID": "your-value",
        "GMC_DRY_RUN": "your-value",
        "GMC_LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "gmc": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "gmc-mcp"
      ],
      "env": {
        "GMC_ACCOUNT_ID": "your-value",
        "GMC_SERVICE_ACCOUNT_KEY": "your-value",
        "GMC_OAUTH_TOKEN": "your-value",
        "GMC_SUBACCOUNT_ID": "your-value",
        "GMC_DRY_RUN": "your-value",
        "GMC_LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • GMC_ACCOUNT_ID required env
    Your 10-digit Google Merchant Center account ID (top-right of merchants.google.com).
  • GMC_SERVICE_ACCOUNT_KEY secret env
    Absolute path to a Google Cloud service-account JSON key file. The service account must be added as Admin in Merchant Center.
  • GMC_OAUTH_TOKEN secret env
    Absolute path to an OAuth user-token JSON file produced by `gmc-mcp auth-init`. Use this OR GMC_SERVICE_ACCOUNT_KEY.
  • GMC_SUBACCOUNT_ID env
    Optional sub-account ID when operating an MCA (Multi-Client Account).
  • GMC_DRY_RUN env
    When 'true', writes are logged to the audit log only (no actual API calls).
  • GMC_LOG_LEVEL env
    Log verbosity: DEBUG / INFO / WARNING / ERROR.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account kiwoongeom, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

  • More stars than 0% of the other 2577 servers in this category
  • Published to the registry more recently than 88% of the other 2577 servers in this category
  • Basic checks equal to or better than 100% of the other 2577 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Gmc MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GMC_ACCOUNT_ID, GMC_SERVICE_ACCOUNT_KEY, GMC_OAUTH_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.6) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeWidely used★ 2KUpdated 13 months ago

Runs in the cloud✓ stripe.com

MCP Cn Commerce

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

by TonyWang-hubEarly↓ 73/wk★ 96Updated 30 days ago

Runs on your computer

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Google Merchant Center MCP (gmc-mcp)

MCP server for Google Merchant Center, built on Merchant API v1.

126 tools, MIT-licensed, pip install-able. Drive your Google Shopping

feed, products, inventory, Reports, promotions, returns, and account

configuration in natural language from Claude Desktop, Claude Code, or any

MCP-compatible client.

### Where this fits in the GMC + MCP landscape

| Option | Type | API | License | Install | Tools |

|---|---|---|---|---|---|

| Adzviser / Catchr / Windsor.ai / Pipedream | Paid hosted SaaS | varies | proprietary | sign-up | varies |

| archpeng/GMC-mcp-server | Self-hosted | Content API v2.1 (deprecated 2026-08) | none declared | git clone | 34 |

| `gmc-mcp` (this package) | Self-hosted | Merchant API v1 (future-proof) | MIT | `pip install gmc-mcp` | 126 |

Pick this if you want: future-proof API, an actual OSS license, PyPI install,

a larger toolset, audit log + rollback + dry-run safety, and credentials that

never leave your machine.

Built on Merchant API v1 (replaces Content API for Shopping; v1beta was discontinued 2026-02-28). Safe by default: every write is recorded to an append-only audit log with before snapshots, dry-run is one toggle away, and destructive bulk operations require an explicit confirm parameter.

Why this exists

Google Merchant Center (GMC) powers Google Shopping listings, Free Listings, Shopping Ads, Buy on Google checkout, YouTube Shopping, and more. Managing a feed of thousands of products through the GMC web UI is tedious, and writing one-off Python scripts against the Merchant API REST endpoints is slow.

There are existing MCP services for GMC, but they fit different niches:

  • Paid hosted SaaS (Adzviser, Catchr, Windsor.ai, Pipedream) — your data is proxied through their servers; monthly subscription.
  • `archpeng/GMC-mcp-server` — earliest self-hosted Python option (Feb 2026), but built on the deprecated Content API v2.1 which Google retires in August 2026, has no license declared, and isn't on PyPI.

gmc-mcp was built to fill the gap: a self-hosted package on the new Merchant API v1, MIT-licensed, on PyPI, with audit/rollback/dry-run safety and 126 tools across 19 modules.

The package gives Claude (or any MCP client) 126 tools that map directly onto the Merchant API v1 surface, so you can do things like:

  • *"Show me every disapproved product, grouped by issue code."*
  • *"Bump US prices 5% on these 40 SKUs."*
  • *"Which products had impressions but zero clicks last week?"*
  • *"Roll back audit ID 8fc8dc42… — that update broke something."*
  • *"Compare this Shopify CSV against my GMC feed; what's missing?"*

What's exposed

126 tools across 19 modules + 4 meta tools.

ModuleTools
productsgmc_list_products, gmc_get_product, gmc_insert_product, gmc_update_product, gmc_delete_product, gmc_bulk_delete_products, gmc_list_disapproved_products
inventorygmc_update_regional_inventory, gmc_update_local_inventory, gmc_list_regional_inventories, gmc_list_local_inventories
issuesgmc_list_account_issues, gmc_get_product_status, gmc_summarize_product_issues
reportsgmc_query_report, gmc_product_performance, gmc_price_competitiveness, gmc_best_sellers, gmc_zero_click_products, gmc_revenue_by_brand, gmc_category_performance, gmc_competitive_visibility_top_merchants, gmc_price_insights, gmc_demoted_products
promotionsgmc_list_promotions, gmc_get_promotion, gmc_insert_promotion
accountsgmc_get_account, gmc_get_business_info, gmc_update_business_info, gmc_list_users, gmc_add_user, gmc_remove_user, gmc_get_shipping_settings, gmc_update_shipping_settings, gmc_list_programs, gmc_request_program_review, gmc_get_program_review
regionsgmc_list_regions, gmc_get_region, gmc_create_region, gmc_update_region, gmc_delete_region
notificationsgmc_list_subscriptions, gmc_subscribe, gmc_unsubscribe
feedsgmc_list_datasources, gmc_get_datasource, gmc_create_supplemental_feed, gmc_create_primary_feed, gmc_delete_datasource, gmc_fetch_datasource
return_policiesgmc_list_return_policies, gmc_get_return_policy, gmc_create_return_policy, gmc_update_return_policy, gmc_delete_return_policy
homepagegmc_get_homepage, gmc_update_homepage, gmc_claim_homepage, gmc_unclaim_homepage
account_configgmc_get_business_identity, gmc_update_business_identity, gmc_get_checkout_settings, gmc_create_checkout_settings, gmc_update_checkout_settings, gmc_delete_checkout_settings, gmc_get_automatic_improvements, gmc_update_automatic_improvements, gmc_get_autofeed_settings, gmc_update_autofeed_settings, gmc_get_account_tax, gmc_update_account_tax, gmc_get_email_preferences, gmc_update_email_preferences, gmc_get_latest_tos, gmc_list_tos_agreement_states, gmc_accept_tos
quotasgmc_list_quotas
reviewsgmc_list_merchant_reviews, gmc_get_merchant_review, gmc_insert_merchant_review, gmc_delete_merchant_review, gmc_list_product_reviews, gmc_get_product_review, gmc_insert_product_review, gmc_delete_product_review
conversionsgmc_list_conversion_sources, gmc_get_conversion_source, gmc_create_conversion_source, gmc_update_conversion_source, gmc_delete_conversion_source, gmc_undelete_conversion_source
omnichannelgmc_list_omnichannel_settings, gmc_get_omnichannel_settings, gmc_create_omnichannel_settings, gmc_update_omnichannel_settings, gmc_request_inventory_verification, gmc_link_gbp_account, gmc_list_gbp_accounts
lfpgmc_lfp_list_stores, gmc_lfp_get_store, gmc_lfp_insert_store, gmc_lfp_delete_store, gmc_lfp_insert_inventory, gmc_lfp_insert_sale, gmc_lfp_get_merchant_state
mcagmc_list_relationships, gmc_get_relationship, gmc_update_relationship, gmc_create_aggregation, gmc_delete_aggregation, gmc_list_account_services, gmc_propose_account_service, gmc_approve_account_service, gmc_reject_account_service
bulkgmc_bulk_update_regional_prices, gmc_bulk_set_availability
diagnosticsgmc_health_check, gmc_rollback, gmc_export_all, gmc_diff_with_shopify
metagmc_describe_server, gmc_audit_lookup, gmc_audit_tail, gmc_set_dry_run

CLI also exposes: gmc-mcp run, auth-init, register-gcp, webhook, describe, version.

Install

pip install gmc-mcp

For development:

git clone https://github.com/kiwoongeom/gmc-mcp

cd gmc-mcp pip install -e ".[dev,test]" pre-commit install

Quick start

1. Enable the Merchant API and create a service account
  1. console.cloud.google.com → create / pick a project.
  2. APIs & Services → Library → enable Merchant API.
  3. IAM & Admin → Service Accounts → Create service account named gmc-mcp.
  4. Open the new service account → Keys → Add key → Create new key → JSON. Save it somewhere safe.
2. Add the service account to your Merchant Center
  1. merchants.google.com → top-right gear → Account access → People.
  2. Add user → enter the gmc-mcp@PROJECT.iam.gserviceaccount.com email → grant Admin.
  3. Note the 10-digit Merchant Center ID in the top-right.
3. Configure
cp .env.example .env

edit:

GMC_ACCOUNT_ID=1234567890

GMC_SERVICE_ACCOUNT_KEY=/abs/path/to/service-account.json

4. One-time GCP registration

Required before any v1 Merchant API call works for a new project.

gmc-mcp register-gcp --developer-email you@example.com
5. Smoke-test
gmc-mcp describe              # prints the resolved config

python examples/quickstart.py # makes one read against the Merchant API

6. Wire into Claude

Drop this into %APPDATA%/Claude/claude_desktop_config.json (Desktop) or ~/.claude/settings.json (Code):

{

"mcpServers": { "gmc": { "command": "gmc-mcp", "args": ["run"], "env": { "GMC_ACCOUNT_ID": "1234567890", "GMC_SERVICE_ACCOUNT_KEY": "/abs/path/to/service-account.json" } } } }

Restart Claude. Ask: *"What account am I connected to?"* — it should call gmc_describe_server.

OAuth instead of a service account

For acting on behalf of an end user (e.g. multi-tenant SaaS):

# 1. In GCP, create OAuth client credentials (type: Desktop), download client_secret.json.

gmc-mcp auth-init --client-secrets ./client_secret.json

follow the browser flow; a token JSON is saved to secrets/oauth-token.json.

2. Use it

export GMC_OAUTH_TOKEN=./secrets/oauth-token.json gmc-mcp run

Transports

gmc-mcp run                              # stdio (Claude Desktop default)

gmc-mcp run --transport sse --port 8000 # SSE / HTTP (remote, Docker, hosted)

Or via Docker:

docker build -t gmc-mcp .

docker run --rm -p 8000:8000 \ -e GMC_ACCOUNT_ID=1234567890 \ -v $PWD/secrets:/secrets \ -e GMC_SERVICE_ACCOUNT_KEY=/secrets/service-account.json \ gmc-mcp

Audit log + rollback

GMC_DRY_RUN=true blocks writes, but still sends read requests, including the read-only Reports API POST reports:search. Report tools return real data; Merchant API errors are surfaced to the caller rather than reported as zero rows.

Every write logs a JSONL entry to GMC_AUDIT_LOG (default: ./logs/audit.jsonl). Each entry contains:

  • audit_id — UUID for lookup
  • op, method, url, request_body, response_status, response_body
  • before — pre-write snapshot when the tool fetched it (used by update_* and delete_*)
  • dry_run — whether the request was actually sent

Inspect from inside Claude:

> Show me my last 5 GMC writes.

[gmc_audit_tail(limit=5) → ...]

Look up audit ID abc123.

[gmc_audit_lookup(audit_id="abc123") → ...]

Roll back audit ID abc123, that update was wrong.

[gmc_rollback(audit_id="abc123", confirm="ROLLBACK") → ...]

Dry-run

Two ways to enable:

GMC_DRY_RUN=true gmc-mcp run
> Set dry-run on and update the price of SKU1 to $19.99.

[gmc_set_dry_run(enabled=True) → ok] [gmc_update_regional_inventory(...) → {"_dry_run": true, ...}]

Reads always go through; only writes are skipped.

Reports query examples

Paste into gmc_query_report:

-- Top 50 by clicks last 7 days

SELECT offer_id, title, clicks, impressions, ctr FROM product_performance_view WHERE date BETWEEN '2026-04-23' AND '2026-04-30' ORDER BY clicks DESC LIMIT 50

-- Disapproved products with reason codes SELECT id, offer_id, title, item_issues FROM product_view WHERE aggregated_reporting_context_status = 'NOT_ELIGIBLE_OR_DISAPPROVED'

-- You're priced h

Only the beginning is shown; read the rest in the repo

Ask PopNx