Claude can help explain a Merchant Center issue by tracing it from the processed product back to its data source. That is especially useful when an apparently corrected title, price or availability keeps reverting. This guide connects the account and builds a source-aware diagnosis before discussing any product change.
What do you need before connecting?
Use Claude on the web or Claude Desktop with connector access allowed for your account. Organization controls may require an owner to add the connector before members connect individually. This guide covers Claude's connector interface; Claude Code's terminal configuration is a separate route.
- A Google login with access to the Merchant Center store or sub-account you manage.
- A LoomaScale account and a separate Google Merchant Center connection. Google Ads access alone is insufficient.
- The numeric Merchant Center account ID, which discovery can find. An advanced multi-client account is a parent; product reports need the relevant standalone account or sub-account.
How do you connect Claude to GMC?
1. Connect GMC in LoomaScale
Create or sign in to your LoomaScale account, then open Connections. Choose Google Merchant Center, sign in with the Google email that has access to the required data, and review the requested permissions. Signing in to LoomaScale with Google is not a substitute for connecting this data source. You can connect this service without connecting an advertising account.
2. Connect the LoomaScale directory connector
Open LoomaScale in Claude's connector directory and choose Connect to Claude. Use the existing full connector for access to this Google service alongside your other connected sources. LoomaScale is listed in the directory; that listing should not be read as a claim that Anthropic verified its analysis.
3. Authorize LoomaScale and enable its tools
Sign in to the LoomaScale account that holds your Google connection and complete authorization. In Claude, open Customize → Connectors and confirm LoomaScale is connected. Enable it for your conversation through + → Connectors, then request an account lookup by name. For a service-specific custom connection, use + Add → Add custom connector, enter the endpoint below and complete the detected OAuth flow. Team and Enterprise owners manage organization-level connector availability.
4. Verify access with an actual account lookup
Use LoomaScale to call gmc_list_accounts. List my Merchant Center account names and numeric IDs, and identify advanced parent accounts. Ask which store or sub-account to inspect. Read its account health. Do not change products, feeds, settings or website claims.
The account list should identify your store and whether it is an advanced parent. Select a reporting-capable store or sub-account, then check its account-health result for destinations, countries and product issues. A product can have different statuses by destination or country. Keep those fields with every diagnosis rather than labelling the whole catalog approved or disapproved from one row.
How do you trace a product issue to its feed in Claude?
Choose one affected product after reading account health. Retrieve its processed attributes and data source, then inspect the source's input type and processing status. Distinguish an API-owned attribute from one supplied by a file, spreadsheet or store integration. The next useful action can be a change upstream rather than a direct product edit.
Use LoomaScale for my selected Merchant Center store. Ask me for an affected product or choose an example from account-health findings. Read its processed attributes, issues and owning data source. Inspect the source type and latest processing status where available. Explain where the correction should originate and what a later sync could overwrite. Give me a diagnosis and next check only; do not change products or feed settings.
Keep the product ID, language and feed label together so the diagnosis refers to the intended offer. If multiple sources contribute attributes, identify what the available tools actually show and label remaining uncertainty. Correcting an upstream feed and waiting for processing is different from sending an API update. Neither action overrides Google's policy review.
Which MCP endpoint does this guide use?
https://api.loomascale.com/mcp/gmcThe service-specific endpoint exposes GMC tools and LoomaScale account helpers. The full directory plugin or connector uses https://api.loomascale.com/mcp and can reach all sources you separately connect. Choose the full connection for work across services; use the specific endpoint when you want this source's tool set. An endpoint choice limits exposed tools, not the Google roles your login holds.
What can Claude read or change in GMC?
LoomaScale reads account health, product issues, processed product attributes, data sources and available product-performance reports. Merchant Center's Google content permission is read/write; a reporting request does not make the underlying OAuth scope read-only. Write tools depend on account availability and Google roles. Start with inspection. Changes to products also depend on the source that owns the attributes: API sources and file or store-managed feeds require different correction paths. Reading an issue or editing an attribute does not guarantee Google approval.
Why is the connection or data missing?
If Claude does not call a tool, enable the connector for the conversation and name LoomaScale explicitly. If new tools are missing, open its connector page and use Refresh tools list; the Claude refresh guide shows the menu. A refreshed list cannot grant access to a missing Google property or bypass an organization restriction.
For a missing store, check the Google email and store or sub-account access. If reporting fails on an advanced parent, select a child account from discovery. If a corrected product reverts, inspect its source before changing it again; a later feed sync may overwrite the value. Inspect destination, country and processing status after a correction. Website claims, feed fetches and product updates are separate actions, so request a diagnosis first and review any proposed write individually.
Related connection guides and official references
Use GMC in another assistant
- How to Connect ChatGPT to GMC
- How to Connect Codex to GMC
- How to Connect Claude Code to GMC
- How to Connect Grok Build to GMC
Connect another Google source to Claude
Official setup references
Setup references checked on November 12, 2026. Menu labels and workspace policies can change; use the linked vendor guidance for your account. For LoomaScale's supported workflows, see the documentation hub.
