Log inSubmit server
Google Merchant Center MCP logo

Google Merchant Center MCP

Connects AI clients to Merchant Center for catalog checks, reports, feed inspection, and controlled product updates.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Merchant Center MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-merchant-center-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-merchants@latest"
      ],
      "env": {
        "GOOGLE_MERCHANTS_CLIENT_ID": "YOUR_VALUE_HERE",
        "GOOGLE_MERCHANTS_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "GOOGLE_MERCHANTS_REFRESH_TOKEN": "YOUR_VALUE_HERE",
        "GOOGLE_MERCHANTS_ACCOUNT_ID": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 28 tools correctly (4d ago).

Overview

Google Merchant Center MCP MCP server connects AI applications to Google Merchant Center through Merchant API v1. It provides read access to products, promotions, reports, data sources, account settings, issues, and market-price data, plus supported write operations. Use it to investigate disapproved products, inspect feeds and performance, or make deliberate changes through API data sources. Google Ads campaigns, budgets, and bids are outside its scope.

Use cases

  • Investigate disapproved products and their reported issues
  • Inspect product feeds, promotions, and data sources
  • Compare product prices with market benchmarks
  • Review clicks and impressions by product
  • Update product availability or price through an API data source

Key features

  • Merchant API v1 access
  • Read products, issues, promotions, feeds, and reports
  • Inspect market prices and Google suggestions
  • Write product, data-source, and promotion data
  • Read-only, write, and destructive operation metadata
  • OAuth-based Merchant Center authentication

Tools28

What Google Merchant Center MCP lets your agent do. Expand a tool for its parameters.

Verified live~7.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

20/22 checks healthy over the last 90d

What it can do

From the 28 tools this server returned when we ran it; 28 declare their own safety hints.

Can delete or modify data · 4Handles credentials · 5Makes network requests · 28Read-only tools · 24
Network at startup4 connections
Files written at startup1
Install scriptsprepare
npm provenanceNot published
Package age87 days
Maintainers1

Observed 2026-11-04 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · mcp-google-merchants@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed28Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Google Merchant Center MCP works

What Google Merchant Center MCP does

Google Merchant Center MCP MCP server gives an AI client access to Merchant Center account data through Google Merchant API v1. It covers the catalog and related Shopping data rather than Google Ads campaign management. Developers can use it to inspect product status, diagnose item-level issues, review promotions, examine reports, and check available data sources.

The server supports 22 tools. Fifteen are read-only, five modify product, data-source, or promotion data, and two are marked as potentially destructive. Tool metadata distinguishes inspection from operations that can change live account data, helping an AI client request confirmation before a consequential action.

How it works

The server connects to an existing Google Merchant Center account using Google OAuth credentials. It does not create a separate Merchant Center account. Merchant Center data is organized around accounts, data sources, and the resulting product state.

Product and promotion changes are limited to API data sources. A scheduled file feed can be triggered for re-fetching, but the server does not edit the contents of that file. Product processing happens asynchronously, so updated product details and quality status may take several minutes to appear.

Market-price comparisons and price suggestions depend on the account having enabled the free Market Insights opt-in. Without that opt-in, the relevant report may contain no rows and the server explains the reason.

Setup and configuration

The documented runtime requirement is Node.js 20 or newer, a Google Merchant Center account, and a Google Cloud project registered with Merchant Center. The package can be launched with npx -y mcp-google-merchants@latest using the stdio transport.

A configured stdio deployment uses these environment variables:

  • GOOGLE_MERCHANTS_CLIENT_ID
  • GOOGLE_MERCHANTS_CLIENT_SECRET
  • GOOGLE_MERCHANTS_REFRESH_TOKEN
  • GOOGLE_MERCHANTS_ACCOUNT_ID

In supported setups, credentials do not need to be entered during package installation.

The repository provides setup instructions for Codex, Claude Code, Claude Desktop, Cursor, and VS Code. Claude Desktop instructions note that the repository publishes an npm stdio package, not a .mcpb extension bundle.

Tools and capabilities

The Google Merchant Center MCP MCP server can help an agent:

  • List accessible Merchant Center accounts.
  • Find disapproved or out-of-stock products and inspect their issues.
  • Show product fields such as title, price, availability, and status.
  • List product and promotion data sources and identify API sources.
  • Re-fetch a scheduled file feed.
  • Review clicks and impressions by product.
  • Compare prices with market benchmarks when Market Insights is enabled.
  • Read Google price suggestions and predicted impact.
  • Update product price or availability through an API data source.
  • Create an API data source for a product feed.
  • Create or update promotions and check their approval status.

For changes, the documented workflow is to first show the target account, data source, and fields to be changed, then confirm the live operation.

Limitations and notes

This Google Merchant Center MCP MCP server does not manage Google Ads campaigns, budgets, or bids. File-feed contents cannot be edited through the server. Product and promotion writes require an API data source, and Merchant Center may need several minutes to process the resulting data. Market-price reports require the relevant Merchant Center opt-in. Start with read-only requests when diagnosing an account, especially before approving a write or potentially destructive operation.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Merchant Center MCP

Google Merchant Center MCP is an MCP server that connects an AI app to Google Merchant Center through Merchant API v1. Its tools read products, promotions, reports, issues, data sources, and account data, and can write supported product, data-source, and promotion changes. It uses your Google access and does not manage Google Ads campaigns, budgets, or bids.

Install it by launching `npx -y mcp-google-merchants@latest` as a stdio MCP server. You need Node.js 20 or newer, a Merchant Center account, and a Google Cloud project registered with Merchant Center. Configuration can use four Google credential environment variables, or the documented interactive OAuth connection flow.

It can change product, data-source, and promotion data through supported API operations. Product and promotion inputs must belong to an API data source; file-feed contents cannot be edited. Ask the assistant to display the target account, data source, and exact fields before confirming a live change.

Yes, Google Merchant Center MCP works with Cursor through a user-level stdio configuration. Add the server to `~/.cursor/mcp.json` on macOS or Linux, or the corresponding user directory on Windows, using the `npx -y mcp-google-merchants@latest` launch command.

No, it does not manage Google Ads campaigns, budgets, or bids. Its scope is Merchant Center data such as products, promotions, reports, issues, and data sources.

Related MCP servers

All in E-Commerce All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Merchant Center MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-merchant-center-mcp?style=directory)](https://allmcps.com/mcp/google-merchant-center-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/google-merchant-center-mcp"><img src="https://allmcps.com/api/badge/google-merchant-center-mcp?style=directory" alt="Google Merchant Center MCP on AllMCPs" /></a>