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 and promotions. 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.

Related MCP server: gmc-mcp

Contents

• 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, OAuth credentials from Google Cloud, and a Google Cloud project registered with Merchant Center. The access setup is described in Getting access.

1. Prepare the four values: OAuth client ID, OAuth client secret, OAuth refresh token, and Merchant Center account ID.

2. Add the server to your AI app using one of the instructions below.

3. Ask the first read-only question above.

In the app:

1. Open Settings → Plugins → MCP servers.

2. Select Add server.

3. Add the launch command npx -y mcp-google-merchants@latest and the four environment variables below.

From the command line:

codex mcp add google-merchants \
  --env GOOGLE_MERCHANTS_CLIENT_ID=your_client_id \
  --env GOOGLE_MERCHANTS_CLIENT_SECRET=your_client_secret \
  --env GOOGLE_MERCHANTS_REFRESH_TOKEN=your_refresh_token \
  --env GOOGLE_MERCHANTS_ACCOUNT_ID=your_merchant_id \
  -- npx -y mcp-google-merchants@latest

Check the connection:

codex mcp list

Codex MCP documentation

claude mcp add \
  --env GOOGLE_MERCHANTS_CLIENT_ID=your_client_id \
  --env GOOGLE_MERCHANTS_CLIENT_SECRET=your_client_secret \
  --env GOOGLE_MERCHANTS_REFRESH_TOKEN=your_refresh_token \
  --env GOOGLE_MERCHANTS_ACCOUNT_ID=your_merchant_id \
  --transport stdio \
  --scope user \
  google-merchants \
  -- npx -y mcp-google-merchants@latest

Check the connection:

claude mcp list

Claude Code MCP documentation

1. Open Claude Desktop and go to Settings → Developer.

2. Select Edit Config.

3. Add the server to mcpServers:

{
  "mcpServers": {
    "google-merchants": {
      "command": "npx",
      "args": ["-y", "mcp-google-merchants@latest"],
      "env": {
        "GOOGLE_MERCHANTS_CLIENT_ID": "your_client_id",
        "GOOGLE_MERCHANTS_CLIENT_SECRET": "your_client_secret",
        "GOOGLE_MERCHANTS_REFRESH_TOKEN": "your_refresh_token",
        "GOOGLE_MERCHANTS_ACCOUNT_ID": "your_merchant_id"
      }
    }
  }
}

If Edit Config is unavailable, open the configuration file directly:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

Claude Desktop MCP documentation

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"],
      "env": {
        "GOOGLE_MERCHANTS_CLIENT_ID": "your_client_id",
        "GOOGLE_MERCHANTS_CLIENT_SECRET": "your_client_secret",
        "GOOGLE_MERCHANTS_REFRESH_TOKEN": "your_refresh_token",
        "GOOGLE_MERCHANTS_ACCOUNT_ID": "your_merchant_id"
      }
    }
  }
}

Cursor MCP documentation

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

{
  "servers": {
    "google-merchants": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "mcp-google-merchants@latest"],
      "env": {
        "GOOGLE_MERCHANTS_CLIENT_ID": "${input:google_merchants_client_id}",
        "GOOGLE_MERCHANTS_CLIENT_SECRET": "${input:google_merchants_client_secret}",
        "GOOGLE_MERCHANTS_REFRESH_TOKEN": "${input:google_merchants_refresh_token}",
        "GOOGLE_MERCHANTS_ACCOUNT_ID": "${input:google_merchants_account_id}"
      }
    }
  },
  "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 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.

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 incoming data and the resulting product status separate:

1. An account contains product and promotion data sources.

2. A data source can be an API source, a file, a Google Sheet, the Merchant Center interface, or an automatic feed.

3. A product input is the product data supplied by one source.

4. 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

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

Getting access

The server uses the Google Merchant API and the OAuth scope https://www.googleapis.com/auth/content.

1. Create or select a Google Cloud project, enable Merchant API, and configure the OAuth consent screen.

2. In Google Cloud, create an OAuth client of type Desktop app. Save its client ID and client secret.

3. Authorize the Google account that has access to your Merchant Center and obtain a refresh token for the scope above. The OAuth 2.0 Playground can help with this step: enable Use your own OAuth credentials, enter the scope, authorize, exchange the code for tokens.

4. Find your Merchant Center account ID in Merchant Center and use it as GOOGLE_MERCHANTS_ACCOUNT_ID.

5. Register the Google Cloud project with Merchant Center once. Google requires a production Merchant Center account with a verified website and an account administrator for this operation. The registration links one Cloud project to the Merchant Center account; until it completes, Merchant API calls from that project are blocked. Follow Google's developer registration guide.

The one-time registration is available through the technical raw_request tool, but it is safer to follow Google's guide if this is your first Merchant API setup. After registration, Google may take up to five minutes to accept calls.

将 OAuth 客户端密钥和刷新令牌视为密码。它们保存在 MCP 客户端配置中，可授予对 Merchant Center 账户的访问权限。

配置

* 可同时使用客户端 ID、客户端密钥和刷新令牌，也可使用预先签发的访问令牌。访问令牌通常约一小时后过期；刷新令牌让服务器在需要时获取新的访问令牌。

数据与遥测

该服务器作为由你的 AI 应用启动的进程在本地运行。它向 Google 发送 Merchant Center 请求，并通过 Google 的 OAuth 端点刷新 OAuth 访问令牌。

它会发送匿名使用遥测数据，以统计活跃安装数和工具需求：一个随机的安装 ID、包版本、AI 客户端与 Node.js/操作系统版本，以及工具名称。它绝不会发送或存储 OAuth 令牌、Merchant Center 数据、工具参数或提示。可通过以下方式为 A1 MCP 服务器禁用此遥测功能：

ASKADS_TELEMETRY=0

限制与后台工作

• Merchant Center 处理是异步的。 新插入、更新或删除的产品输入可能需要几分钟才能出现在已处理产品中。产品和促销的审批问题稍后才会出现，而非立即报 API 错误。

• Market Insights 是可选的。 只有在账户选择加入免费 Market Insights 计划后，价格竞争力和建议价格报告才会返回数据。

• 配额取决于账户和 API 方法。 使用 list_method_quotas 检查当前消耗量；Google 的每日计数器在 12:00 UTC 重置。

• 临时限制会被谨慎处理。 当 Google 返回 429 时，服务器会在提供 Retry-After 时遵循该指令，并进行有限次数的重试。在网络或服务器故障不确定的情况下，它不会重放写入操作。

• 没有后台监控。 服务器仅在 AI 应用调用它时工作。如果你的 AI 应用支持计划任务，你可以要求它定期检查产品问题或配额使用情况。

• 聚合产品问题存在账户限制。 list_product_issues 适用于独立账户和子账户，不适用于高级主账户。

技术文档

• MCP 能力目录 — 针对每个工具的任务导向页面。

• 所有工具及其输入

• 开发文档

• 发布文档

• Google Merchant API 概览

• Google Merchant API 认证

• Google 开发者注册

支持

发现了 bug 或需要某个场景？请创建 issue或通过 Telegram 联系。