A Merchant Center connection gives Codex a way to compare catalog code with the product Google actually processed. This helps investigate price, availability, link or title mismatches without guessing from a feed template alone. The MCP route connects the store's data; repository access provides separate evidence about how your application generates it.
What do you need before connecting?
Use an installed Codex CLI with remote HTTP MCP and OAuth support. Run the setup on the same Codex host where you will use the tools. A local CLI configuration does not by itself configure a separate cloud task. You need no Google service-account JSON or API key for this hosted OAuth 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 Codex 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. Add the source-specific MCP server to Codex
Run these commands in your terminal. The first saves the remote server and the second starts browser authorization. The server name is specific to this Google source, so another source can be added without replacing it.
codex mcp add loomascale-gmc --url https://api.loomascale.com/mcp/gmc
codex mcp login loomascale-gmc3. Finish OAuth and check the active Codex connection
Complete LoomaScale authorization in the browser using the account with your Google connection, then return to the terminal. Run codex mcp list to check the saved server. Start or reopen a Codex session and use /mcp to inspect its active tools. A saved entry is configuration evidence; the account lookup below verifies data access. Codex's supported local clients share MCP configuration for the same host. Consult OpenAI's current documentation for your desktop or IDE surface; do not assume a different host inherited your login.
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 compare a catalog exporter with Merchant Center in Codex?
Choose a small sample of affected offers and inspect their processed attributes and sources. Read the repository's export or synchronization logic for the same attributes. Align product identity, language, feed label, currency and source before declaring a mismatch. A fetched product can reflect processing and source rules beyond one local export file.
Use LoomaScale for my selected Merchant Center store. Ask for three affected offer IDs with language and feed label. Read their processed price, currency, availability, link, title and data source. Inspect the repository's export mapping for those fields without edits. Compare supported evidence, flag identity or processing ambiguity, and propose a minimal diagnostic or code change for review. Do not update products, fetch feeds or modify files.
The useful output is a field-level comparison with provenance: which value came from the processed product and which from code or a local file. A mismatch may require an upstream mapping correction rather than a Merchant API write. After any later repair, check the processed product again; successful export generation is not the same as successful Google processing or approval.
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 Codex 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 authorization is missing, run codex mcp login loomascale-gmc again. If the entry is configured but absent in the active session, restart that session and inspect /mcp. Check the URL and host if the tools still do not load. The main LoomaScale plugin and the service-specific server are alternative connections; installing both can expose duplicate tool sets.
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 Claude Code to GMC
- How to Connect Grok Build to GMC
Connect another Google source to Codex
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.
