Google Merchant Center

Google Merchant Center

This connector works with Google Merchant Center through the Merchant API v1 (https://merchantapi.googleapis.com): products and product inputs, data sources (feeds), product statuses and issues, reports in Merchant Center Query Language, local and regional inventory, promotions, notification subscriptions, account settings and quotas. The Merchant API replaced the Content API for Shopping v2.1, which Google sunset on 18 August 2026: since 1 September 2026 Content API calls fail more and more often with HTTP 410, and it shuts down completely in early 2027. Merchant API v1beta was retired on 28 February 2026; this connector uses v1.

Setup (one-time, about 15 minutes)

1. Open https://console.cloud.google.com, pick or create a project, then APIs & Services → Library → enable Merchant API.
2. APIs & Services → OAuth consent screen: choose Internal if you are on Google Workspace (simplest), otherwise External. For External, set the publishing status to In production: while an app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. For your own use, the "unverified app" warning can be clicked through.
3. APIs & Services → Credentials → Create credentials → OAuth client ID → application type Web application → add the authorized redirect URI <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
4. Paste the client ID and secret into GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. Put the Merchant Center account id into GOOGLE_MERCHANT_ACCOUNT_ID: the number shown at the top of Merchant Center next to the store name, or after a= in its address (merchants.google.com/mc/overview?a=123456789). On an advanced (multi-client) account, use the advanced account's id to manage the account itself, or a sub-account's id for that shop.
5. On the connector page, click Authorize with Provider and sign in with a Google account that is a user of the Merchant Center account (Admin access for setup and writes, Standard for products and feeds, Read only for reads; Performance reporting only covers the performance reports).
6. Register the Cloud project once: call google_merchant_center_register_gcp_project (optionally with developer_email). Until then every other call answers 401 GCP project with id ... is not registered with the merchant account. The signed-in user must have Admin access, and the registration is done on the main (advanced or standalone) account, not on each sub-account. google_merchant_center_get_developer_registration shows the registered project numbers.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector (Gmail, Google Calendar, Google Drive, Google Sheets, Search Console, Analytics, Ads, Merchant Center). Enable each API in that project, reuse the same GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, and authorize each connector once: each one asks only for its own scopes.

Scope: https://www.googleapis.com/auth/content, the only Merchant API scope (read and write). What the agent can do is bounded by the Merchant Center access of the signing-in user; for a read-only agent, sign in with a Read only user and disable every insert, update, create, fetch and register tool.

Account: one connector works on one Merchant Center account, the one in GOOGLE_MERCHANT_ACCOUNT_ID. google_merchant_center_get_account checks it; google_merchant_center_list_accounts lists every account the user can open and google_merchant_center_list_subaccounts the sub-accounts of an advanced account. To work on another account, install the connector again with that id.

Switched off at install: google_merchant_center_delete_product_input, google_merchant_center_delete_local_inventory, google_merchant_center_delete_regional_inventory and google_merchant_center_delete_notification_subscription; they cannot be undone (a deleted product loses its history and status), so an admin switches them on when the team needs them.

Health check of a store

1. google_merchant_center_list_account_issues: account-level problems (unclaimed website, misrepresentation, missing shipping or return policy, suspension).
2. google_merchant_center_list_aggregate_product_statuses: approved, pending and disapproved counts per destination and country, with the top issues.
3. Products with problems: google_merchant_center_search_reports with SELECT id, offer_id, title, aggregated_reporting_context_status, item_issues FROM product_view WHERE aggregated_reporting_context_status = 'NOT_ELIGIBLE_OR_DISAPPROVED'; then google_merchant_center_get_product for the full productStatus.itemLevelIssues (code, attribute, description, resolution).
4. Settings behind the issues: google_merchant_center_get_business_info, google_merchant_center_get_homepage, google_merchant_center_get_shipping_settings, google_merchant_center_list_programs, google_merchant_center_list_users.

Products

• Read: google_merchant_center_list_products (keep page_size small, default 25, max 1000) and google_merchant_center_get_product. A product id is contentLanguage~feedLabel~offerId, e.g. en~US~sku123; the full name is accounts/<id>/products/en~US~sku123. Offer ids containing /, % or ~ must be passed as the unpadded base64url encoding of the whole id string.
• What you read is the processed product, merged from every data source. Writes go to a product input in one API data source: find or create one with google_merchant_center_list_data_sources / google_merchant_center_create_data_source (primary_product_data_source), then google_merchant_center_insert_product_input (creates or fully replaces), google_merchant_center_update_product_input (change some fields, update_mask like product_attributes.price,product_attributes.availability), google_merchant_center_delete_product_input. File feeds and products added in the Merchant Center UI cannot be edited here; override their attributes with a supplemental API data source instead.
• Changes show in google_merchant_center_get_product after a few minutes; approval for ads and free listings can take up to a few days.
• Attribute names are the Merchant API ones in camelCase (title, link, imageLink, availability IN_STOCK/OUT_OF_STOCK/PREORDER/BACKORDER, condition NEW/USED/REFURBISHED, gtins, brand, mpn, googleProductCategory, salePrice, shipping).

Data sources (feeds): google_merchant_center_list_data_sources, google_merchant_center_get_data_source, google_merchant_center_create_data_source, google_merchant_center_update_data_source (update_mask required), google_merchant_center_fetch_data_source to fetch a file feed now and google_merchant_center_get_latest_file_upload for the result of the last upload (items created, updated, issues).

Reports (google_merchant_center_search_reports): Merchant Center Query Language, SELECT fields FROM table WHERE ... ORDER BY ... LIMIT n. Field names are snake_case; conditions combine with AND only (no OR; use IN); ORDER BY only on selected fields. Performance tables (product_performance_view, non_product_performance_view) need a date condition, date BETWEEN '2026-10-01' AND '2026-10-29' or date DURING LAST_30_DAYS, and at least one metric (clicks, impressions, click_through_rate, conversions, conversion_value). Segments: offer_id, title, brand, category_l1, product_type_l1, customer_country_code, marketing_method (ADS, ORGANIC), date, week. Other tables: product_view (status and issues per product), price_competitiveness_product_view (your price vs benchmark_price), price_insights_product_view (suggested_price, predicted impact), best_sellers_product_cluster_view and best_sellers_brand_view (select report_date, report_granularity, report_country_code and report_category_id, and filter on report_granularity and report_country_code, e.g. WHERE report_granularity = 'WEEKLY' AND report_country_code = 'US'), competitive_visibility_*_view. Rows come back as results[], each holding one object named after the table (productPerformanceView, ...). Page with nextPageToken.

Inventory: in-store with google_merchant_center_list_local_inventories, google_merchant_center_insert_local_inventory and google_merchant_center_delete_local_inventory (store codes from the linked Business Profile); by region with google_merchant_center_list_regional_inventories, google_merchant_center_insert_regional_inventory and google_merchant_center_delete_regional_inventory (region ids from google_merchant_center_list_regions). An insert replaces the entry for that store or region.

Promotions: google_merchant_center_list_promotions, google_merchant_center_get_promotion (id like en~US~SPRING10), google_merchant_center_insert_promotion into a promotion data source. The Promotions program must be enabled for the country; Google reviews each promotion.

Notifications: google_merchant_center_list_notification_subscriptions, google_merchant_center_get_notification_subscription, google_merchant_center_create_notification_subscription (an HTTPS callback for PRODUCT_STATUS_CHANGE or ACCOUNT_SERVICE_CHANGE), google_merchant_center_update_notification_subscription, google_merchant_center_delete_notification_subscription.

Quota: google_merchant_center_list_quotas shows daily and per-minute limits and today's usage per method group. Product writes are limited per day relative to the catalog size; spread bulk updates out and prefer one supplemental feed over thousands of single updates.

Reading the answers

• Money is in micros: {"amountMicros": "19990000", "currencyCode": "EUR"} = 19.99 EUR. Large numbers (micros, quantities, ids) arrive as JSON strings.
• Times are RFC 3339 in UTC; report date values are in the account's time zone.
• Names are resource paths: accounts/123/products/en~US~sku1, accounts/123/dataSources/456; tools take the last part as the id.
• Paging: list tools return nextPageToken; call again with page_token until it is missing.

Common errors

• 401 GCP project with id ... is not registered: run google_merchant_center_register_gcp_project (setup step 6). 401 otherwise: authorization expired or was revoked (always after 7 days while the consent screen is in Testing); click Authorize with Provider again.
• 403 The caller does not have access to the accounts: the signed-in user is not a user of that Merchant Center account, or GOOGLE_MERCHANT_ACCOUNT_ID is wrong. 403 "Merchant API has not been used in project": enable the API (step 1).
• 400 on a product input: a required attribute is missing or misspelled, or the data source is not an API source. 404: unknown product, data source or promotion id (check the contentLanguage~feedLabel~offerId parts).
• 429 RESOURCE_EXHAUSTED: quota reached; check google_merchant_center_list_quotas and retry later.

Out of scope here: orders and returns, changes to shipping and return policies, account creation and user management, product reviews, and Google Ads campaigns (use the Google Ads connector).