Claude Code can investigate a Merchant Center feed problem alongside the code that produces the catalog. The connection adds account, source and product diagnostics to the coding session. This guide uses a direct HTTP MCP server and starts with reading processing evidence before any request to change a feed or product.
What do you need before connecting?
Use Claude Code installed on the computer where you will run these commands. Its CLI supports remote HTTP MCP servers and browser OAuth. This route registers an explicit user-scoped server for use across your projects; project-scoped team configuration is a separate choice. You do not need to run a local Google API server.
- 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 Code 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. Register the remote MCP server in Claude Code
Run this command in your system terminal, outside a Claude Code conversation. User scope makes the connection available across your projects. The URL selects this Google service's tools.
claude mcp add --transport http --scope user loomascale-gmc https://api.loomascale.com/mcp/gmcIf you already use the full LoomaScale agent plugin, check its tools before adding a second connection. The plugin route is documented in the Claude Code setup guide; this article uses direct MCP setup.
3. Authenticate from Claude Code's MCP menu
Open Claude Code and enter /mcp. Select loomascale-gmc and complete its authentication flow in the browser. Use the LoomaScale account with your Google source connected. Return to Claude Code and confirm the server is connected. You can inspect the saved server from the system terminal with claude mcp get loomascale-gmc or claude mcp list. A successful add command saves configuration; it does not prove that the Google account lookup succeeded.
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 investigate a feed-processing failure with Claude Code?
Find the data source involved and read its input type and available latest-processing details. For a file source, inspect reported row-level issues; for an API source, follow the applicable product-input path instead. Then review the repository's serialization or mapping code for the affected fields. Use a small reproducible example to avoid broad catalog changes.
Use LoomaScale for my selected Merchant Center store. List data sources and ask which one to inspect. Read its type and available processing details, including file issues when applicable. Compare the reported field problem with this repository's export or upload code without editing files. Identify a minimal example and propose a focused fix plus a verification plan. Do not fetch a feed, upload products or change settings.
A data-source processing failure differs from a policy disapproval on a processed product. Preserve the exact stage and error before proposing a fix. Some settings belong to a store integration rather than repository code. After a later approved repair, validate the submitted data, the latest processing result and the resulting product status as separate checks.
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 Code 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 the server needs authentication, open /mcp and sign in again. If tools are missing, check claude mcp list, the source endpoint, and whether an organization policy restricts the server. Restart the session after a configuration change if needed. A Claude web connector and an explicit CLI server can overlap; check the active tools before adding duplicate connections.
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 Claude to GMC
- How to Connect Codex to GMC
- How to Connect Grok Build to GMC
Connect another Google source to Claude Code
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.
