Google Merchant Center MCP

Name: Google Merchant Center MCP
Author: A1-x-Tech

by A1-x-Techversion 1.3.2i★ –iRuns on your computer

Registry nameio.github.A1-x-Tech/mcp-google-merchants

Install

Overview

Description from the maker (original English)

MCP server for Google Merchant Center (Merchant API v1): products, promotions, reports, issues.

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 821/wk · ★ –

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: GOOGLE_MERCHANTS_CLIENT_ID, GOOGLE_MERCHANTS_CLIENT_SECRET, GOOGLE_MERCHANTS_REFRESH_TOKEN, GOOGLE_MERCHANTS_ACCESS_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: GOOGLE_MERCHANTS_CLIENT_ID, GOOGLE_MERCHANTS_CLIENT_SECRET, GOOGLE_MERCHANTS_REFRESH_TOKEN, GOOGLE_MERCHANTS_ACCESS_TOKEN, GOOGLE_MERCHANTS_ACCOUNT_ID, GOOGLE_MERCHANTS_OAUTH_PORT, GOOGLE_MERCHANTS_API_BASE, GOOGLE_MERCHANTS_TIMEOUT_MS, GOOGLE_MERCHANTS_MAX_RETRIES

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

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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": {
    "google-merchants": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-merchants"
      ],
      "env": {
        "GOOGLE_MERCHANTS_CLIENT_ID": "your-value",
        "GOOGLE_MERCHANTS_CLIENT_SECRET": "your-value",
        "GOOGLE_MERCHANTS_REFRESH_TOKEN": "your-value",
        "GOOGLE_MERCHANTS_ACCESS_TOKEN": "your-value",
        "GOOGLE_MERCHANTS_ACCOUNT_ID": "your-value",
        "GOOGLE_MERCHANTS_OAUTH_PORT": "your-value",
        "GOOGLE_MERCHANTS_API_BASE": "your-value",
        "GOOGLE_MERCHANTS_TIMEOUT_MS": "your-value",
        "GOOGLE_MERCHANTS_MAX_RETRIES": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add google-merchants --env GOOGLE_MERCHANTS_CLIENT_ID=your-value --env GOOGLE_MERCHANTS_CLIENT_SECRET=your-value --env GOOGLE_MERCHANTS_REFRESH_TOKEN=your-value --env GOOGLE_MERCHANTS_ACCESS_TOKEN=your-value --env GOOGLE_MERCHANTS_ACCOUNT_ID=your-value --env GOOGLE_MERCHANTS_OAUTH_PORT=your-value --env GOOGLE_MERCHANTS_API_BASE=your-value --env GOOGLE_MERCHANTS_TIMEOUT_MS=your-value --env GOOGLE_MERCHANTS_MAX_RETRIES=your-value -- npx -y mcp-google-merchants

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": {
    "google-merchants": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-merchants"
      ],
      "env": {
        "GOOGLE_MERCHANTS_CLIENT_ID": "your-value",
        "GOOGLE_MERCHANTS_CLIENT_SECRET": "your-value",
        "GOOGLE_MERCHANTS_REFRESH_TOKEN": "your-value",
        "GOOGLE_MERCHANTS_ACCESS_TOKEN": "your-value",
        "GOOGLE_MERCHANTS_ACCOUNT_ID": "your-value",
        "GOOGLE_MERCHANTS_OAUTH_PORT": "your-value",
        "GOOGLE_MERCHANTS_API_BASE": "your-value",
        "GOOGLE_MERCHANTS_TIMEOUT_MS": "your-value",
        "GOOGLE_MERCHANTS_MAX_RETRIES": "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": {
    "google-merchants": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-merchants"
      ],
      "env": {
        "GOOGLE_MERCHANTS_CLIENT_ID": "your-value",
        "GOOGLE_MERCHANTS_CLIENT_SECRET": "your-value",
        "GOOGLE_MERCHANTS_REFRESH_TOKEN": "your-value",
        "GOOGLE_MERCHANTS_ACCESS_TOKEN": "your-value",
        "GOOGLE_MERCHANTS_ACCOUNT_ID": "your-value",
        "GOOGLE_MERCHANTS_OAUTH_PORT": "your-value",
        "GOOGLE_MERCHANTS_API_BASE": "your-value",
        "GOOGLE_MERCHANTS_TIMEOUT_MS": "your-value",
        "GOOGLE_MERCHANTS_MAX_RETRIES": "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

GOOGLE_MERCHANTS_CLIENT_ID secret env
Google OAuth 2.0 client ID (refresh-token flow).
GOOGLE_MERCHANTS_CLIENT_SECRET secret env
Google OAuth 2.0 client secret (refresh-token flow).
GOOGLE_MERCHANTS_REFRESH_TOKEN secret env
OAuth refresh token with scope https://www.googleapis.com/auth/content.
GOOGLE_MERCHANTS_ACCESS_TOKEN secret env
Pre-minted OAuth access token (~1h lifetime) — alternative to the refresh trio.
GOOGLE_MERCHANTS_ACCOUNT_ID env
Default Merchant Center account ID; tools can override it per call.
GOOGLE_MERCHANTS_OAUTH_PORT env
Fixed port for the loopback listener of the in-chat login (127.0.0.1 + PKCE). Set it when the client runs over SSH port forwarding; otherwise a free port is picked per login.
GOOGLE_MERCHANTS_API_BASE env
API root host override.
GOOGLE_MERCHANTS_TIMEOUT_MS env
Per-request timeout in milliseconds.
GOOGLE_MERCHANTS_MAX_RETRIES env
Retries on transient errors (429 always; 5xx/network for reads).

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 A1-x-Tech, 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 2569 servers in this category
Published to the registry more recently than 86% of the other 2569 servers in this category
Basic checks equal to or better than 100% of the other 2569 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 Google Merchant Center 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: GOOGLE_MERCHANTS_CLIENT_ID, GOOGLE_MERCHANTS_CLIENT_SECRET, GOOGLE_MERCHANTS_REFRESH_TOKEN, GOOGLE_MERCHANTS_ACCESS_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 (1.3.2) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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

Spree Commerce: open-source B2B and marketplace ecommerce

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

by spreeWidely used★ 15.8KUpdated 9 days ago

Runs in the cloud

Install

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

Install

MCP Cn Commerce

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

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

Runs on your computer

Install

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

English | Русский

A1 Google Merchant Center MCP connects an AI app to your Google Merchant Center account. Find out why products are disapproved, inspect feeds and promotions, explore reports and market prices, then make deliberate changes to product data when you need to.

It works with the Merchant Center data behind Shopping listings: products, data sources, promotions and reports. Campaigns, budgets and bids belong to Google Ads and are outside this server.

22 tools. 15 operations only read Merchant Center data; 5 write product, data-source or promotion data; 2 are potentially destructive.
Your Google access. The server uses your OAuth credentials and the Merchant API v1 — it does not create a separate Merchant Center account.
Source-aware changes. Product and promotion inputs can be changed only through an API data source. A file feed can be re-fetched, but its contents are not edited here.
Visible boundaries. Tools carry read-only, write or destructive metadata, so an AI client can distinguish an inspection from a live change.

Start with a read-only question:

Which products are disapproved, and what issues does Google report for each?

Connect the server · Explore use cases · Open technical documentation

See it work in a minute

You: Which products are disapproved, and what issues does Google report for each?

Assistant: Lists the affected products and explains the item-level issues that Merchant Center reports.

You: Show the current price and availability of product SKU-123, then prepare an availability update to in_stock.

Assistant: Shows the current product input, the API data source it belongs to and the exact change to make. It asks for confirmation before updating the live product input.

You: Confirm the update.

Assistant: Sends the update and explains that Merchant Center processes product data asynchronously. The processed product and its quality status can take several minutes to refresh.

Quick start
What you can ask it to do
How Merchant Center data is connected
What can change
Getting access
Configuration
Data and telemetry
Limits and background work
Technical documentation
Support

Quick start

You need Node.js 20+, a Google Merchant Center account and a Google Cloud project registered with Merchant Center. OAuth credentials are not required at install time — the server connects from the conversation, see Getting access.

Add the server to your AI app using one of the instructions below.
Say "connect Google Merchant Center": the assistant walks you through the OAuth client and the browser consent, no config files and no restart.
Ask the first read-only question above.

Codex

In the app:

Open Settings → MCP servers.
Select Add server.
Choose STDIO, then enter the launch command npx -y mcp-google-merchants@latest and the four environment variables below.

Variable	Value
`GOOGLE_MERCHANTS_CLIENT_ID`	Your Google OAuth client ID
`GOOGLE_MERCHANTS_CLIENT_SECRET`	Your Google OAuth client secret
`GOOGLE_MERCHANTS_REFRESH_TOKEN`	Your Google OAuth refresh token
`GOOGLE_MERCHANTS_ACCOUNT_ID`	Your Merchant Center account ID

Select Save, then Restart.

From the command line:

codex mcp add google-merchants \

-- npx -y mcp-google-merchants@latest

Check the connection:

codex mcp list

Codex MCP documentation

Claude Code

claude mcp add \

--transport stdio \ --scope user \ google-merchants \ -- npx -y mcp-google-merchants@latest

Check the connection:

claude mcp list

Claude Code MCP documentation

Claude Desktop

The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.

This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:

"mcpServers": { "google-merchants": { "command": "npx", "args": ["-y", "mcp-google-merchants@latest"] } } }

In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.

Claude Desktop MCP documentation

Cursor

Add a user-level server to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:

"mcpServers": { "google-merchants": { "type": "stdio", "command": "npx", "args": ["-y", "mcp-google-merchants@latest"] } } }

Cursor MCP documentation

VS Code

Run MCP: Open User Configuration from the Command Palette and add:

"servers": { "google-merchants": { "type": "stdio", "command": "npx", "args": ["-y", "mcp-google-merchants@latest"] } }, "inputs": [ { "type": "promptString", "id": "google_merchants_client_id", "description": "Google OAuth client ID" }, { "type": "promptString", "id": "google_merchants_client_secret", "description": "Google OAuth client secret", "password": true }, { "type": "promptString", "id": "google_merchants_refresh_token", "description": "Google OAuth refresh token", "password": true }, { "type": "promptString", "id": "google_merchants_account_id", "description": "Merchant Center account ID" } ] }

Check the server with MCP: List Servers.

VS Code MCP documentation

What you can ask it to do

Find and understand catalog problems

Which products are disapproved, and what does Google report for each of them?
Show the title, price, availability and current status of product SKU-123.
Which products are out of stock?
Show the most frequent product issues for this Merchant Center account.

Explore performance and prices

Show clicks and impressions by product for July.
Which products are priced above the market benchmark in the United States?
What prices does Google suggest, and what impact does it predict?

Price comparisons and suggestions require the free Market Insights opt-in in Merchant Center. If the account has not opted in, the server explains why the report has no rows.

Inspect the account and feeds

List the Merchant Center accounts I can access.
Is the store homepage claimed? Show the current shipping settings.
List the product and promotion data sources, and identify an API data source.
Re-fetch this scheduled file feed now.

Make deliberate changes

Update the price and availability of this product in its API data source.
Create an API data source for a new product feed.
Create or update a promotion and then check its approval status.

For any request that changes data, first ask the assistant to show the target account, data source and exact fields it plans to change.

How Merchant Center data is connected

Merchant Center keeps the incoming data and the resulting product status separate:

An account contains product and promotion data sources.
A data source can be an API source, a file, a Google Sheet, the Merchant Center interface or an automatic feed.
A product input is the product data supplied by one source.
A processed product is what Merchant Center derives after processing that input. It includes eligibility and item-level issues.

The server can read every listed source type. It can create API data sources and update product inputs only in an API data source; it cannot write into a file, interface or automatic feed. To find products by condition, use a report query: list_products itself does not provide server-side filtering.

What can change

Operation	What happens	Confirmation boundary
Inspect accounts, products, feeds, promotions, reports, issues and quota use	Reads data from Merchant Center	Does not change Merchant Center
Create an API data source	Adds a source for product or promotion data	Changes the account
Update a product input	Changes selected product fields, such as price or availability	Changes live source data
Insert a product input	Replaces the complete input with the same ID in that API source; using a different source moves the product	Changes live source data
Re-fetch a file feed	Requests an out-of-schedule fetch of a file or Google Sheets feed	Starts asynchronous work at Google
Insert or update a promotion	Creates or changes a promotion	Changes live source data
Delete a product input	Removes the input from the selected data source	Destructive
Raw Merchant API request	Can access API methods without a dedicated tool	Potentially destructive

The MCP client decides how it asks you to confirm write and destructive tools. The server marks its read-only, write and destructive operations so the client can present the right boundary.

Getting access

The server uses the Google Merchant API and the OAuth scope https://www.googleapis.com/auth/content. There are two ways to hand it credentials, and the first one needs no configuration files.

Connect from the chat (recommended)

Say "connect Google Merchant Center" and the assistant runs the flow with you:

setup_instructions prints the checklist: create or select a Google Cloud project, enable Merchant API, configure the consent screen and create a Desktop app OAuth client.
Download that client's JSON ("Download JSON") and give the assistant its path — set_client stores it owner-only. The secret never goes through the conversation.
start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.
finish_login exchanges the code, saves the tokens to ~/.config/mcp-google-merchants/credentials.json (mode 0600) and verifies them with a real Merchant API call — so a project that is not registered with Merchant Center yet is caught right there.

The tokens are re-read on

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

Google Merchant Center MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Online shops & paymentsi

Common questions

Alternatives

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

MCP Cn Commerce

README from the maker

Google Merchant Center MCP

See it work in a minute

Contents

Quick start

What you can ask it to do

Find and understand catalog problems

Explore performance and prices

Inspect the account and feeds

Make deliberate changes

How Merchant Center data is connected

What can change

Getting access

Connect from the chat (recommended)