Google Merchant Center MCP

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.

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

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

Codex

In the app:

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

1. 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:

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-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:

1. 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.
2. 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.
3. 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.
4. 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