Claude has no Merchant Center integration of its own. It reaches your shop through the GSC Wizard MCP server at mcp.gscwizard.com, a hosted connector that holds the Merchant Center access, so Claude and Claude Code read your free listing performance, the products Google is holding back, price insights and feed health instead of guessing them.
Connector URL: https://mcp.gscwizard.com/mcp
The short answer
Link Merchant Center to your shop in GSC Wizard first, then pick the route that matches how you use Claude:
claude mcp add command, then sign in from /mcp, or pass an API key for scripts and CI.Claude only sees the shops you linked in GSC Wizard, and you can make the connection read-only when you approve it.
Claude reads Merchant Center through the link you set per site in GSC Wizard, so you never paste a merchant ID into a chat. If the property's Organic Shopping report in the app shows numbers, Claude can read them too.
MCP access is part of every GSC Wizard plan, and every new account starts with a 7-day free trial. Sign in at tool.gscwizard.com with Google.
Connect Merchant Center on the Account page. Google offers no read-only Merchant Center permission, so its consent screen asks to manage your product listings, but GSC Wizard only reads your reports and catalog and never edits products or your feed.
Open the property, expand E-commerce in the sidebar, click Organic Shopping and pick the Merchant Center account it maps to. The Merchant Center setup guide covers multi-client accounts and the registration step Google sometimes asks for.
Already using GSC Wizard in Claude for Search Console? There is nothing to add: the shopping tools live on the same server, so your existing connector already has them.
The Connectors screen signs you in with OAuth, so there is no key to copy, paste or rotate. Connectors you add on the web also appear in the desktop app, and the other way round.
Open Settings → Connectors → Add custom connector, name it GSC Wizard and enter https://mcp.gscwizard.com/mcp. Leave the OAuth client ID and secret empty, because Claude registers itself with the server. On a Team or Enterprise plan, an owner may have to add the connector for the organisation first.
Click Connect. The GSC Wizard sign-in screen shows the account you are signed in as, so check that it is the one that holds the shop. Leave Also allow Claude to make changes ticked if you want Claude to queue feed audits, or untick it for a read-only connection.
Open the tools menu in the message box and make sure GSC Wizard is switched on for the conversation. Claude asks before it calls a tool for the first time, and you can allow it once or always.
Working on one shop? Put it in a Claude Project and add the property to the project instructions, for example "The shop is sc-domain:example.com. Compare trends between Search Console and Merchant Center, never totals." Every chat in the project then starts from the right place.
Ask something you can compare with the app: "List my Merchant Center accounts and their sites, then show free listing clicks for example.com over the last 28 days, with the dates." The clicks should match the Organic Shopping report for those dates. If Claude answers with a notConfigured note instead, the note names the reason, which is usually a missing link on the property in the app.
One command adds the same server to Claude Code, which then runs the sign-in in your browser the first time you use it.
claude mcp add --transport http gsc-wizard https://mcp.gscwizard.com/mcpStart Claude Code, type /mcp, select gsc-wizard and choose to authenticate. For scripts and CI, where no browser is available, create a key under Account → API keys in GSC Wizard and pass it as a header instead. Pick a read-only key unless the job has to queue audits.
claude mcp add --transport http gsc-wizard \
https://mcp.gscwizard.com/mcp \
--header "Authorization: Bearer gscw_live_..."With the shop's code open, Claude Code can tie a Merchant Center issue to the line behind it. Ask it to read the top issues from get_product_listing_status, such as a price that does not match the landing page, and then find where the repository renders that price or the Product structured data the issue is about.
Prefer the Claude Desktop config file to the Connectors screen? It only starts local servers, so a remote server has to go through the mcp-remote bridge, and the Claude setup guide has the exact config.
The shopping tools work for every subscriber, on every plan and during the trial. They return analysed answers, so Claude reads finished figures instead of adding up thousands of product rows.
Free listing clicks, impressions and conversions with the top offers, grouped by brand, Google category or your own product type, next to the merchant listings Search Console reports for web Search.
Disapproved and limited products sorted by Google's own click-potential rank, account issues and suspensions, the processing state of every feed, title hygiene, and a feed audit with a Feed Score from 0 to 100.
Competitor visibility per country and category, your prices against the market benchmark with Google's suggested sale price, and Google's best sellers with the ranked products you do not stock.
Every tool, its inputs and how to read its numbers are in the shopping tools reference.
Ask in your own words, and name the property when you have more than one shop.
One Merchant Center link in GSC Wizard serves every assistant you connect.
A developer-mode connector, or the Responses API with a key.
Read the guideMore prompts that tie a Merchant Center issue to your shop's code.
Read the guideThe same connector reads your clicks, impressions and rankings too.
Read the guideSee also the Merchant Center MCP overview, the GA4 MCP for ecommerce revenue, and the Merchant Center MCP playbook with a weekly feed triage and a monthly shop report.
No. Claude has no built-in Merchant Center integration. It reaches your shop through an MCP connector: add the GSC Wizard MCP server at https://mcp.gscwizard.com/mcp and Claude can read the Merchant Center accounts you linked to your sites in GSC Wizard.
Custom connectors live under Settings → Connectors and work on every Claude plan, including Free, which can add one custom connector. On a Team or Enterprise plan an owner may have to add the connector for the organisation first. Claude Code connects with one command on any account that can run it.
Yes. One claude mcp add command adds the server, and Claude Code signs you in through the browser the first time, or takes an API key header for scripts and CI. With the shop's code open, it can trace a Merchant Center issue, such as a price mismatch, to the template that renders the price.
No. Google offers no read-only Merchant Center permission, so its consent screen asks to manage your product listings, but GSC Wizard only reads your reports and catalog and never edits products or your feed. The one tool that changes anything, run_feed_audit, queues an audit inside GSC Wizard that crawls your product pages and writes nothing to Merchant Center. Untick the option to allow changes when you approve the connection and even that is off.
They count different surfaces. Search Console merchant listings count enriched product results in web Search only, for your own URLs, while Merchant Center free listings cover the Shopping tab, Search, Images, Lens, YouTube and Maps. Merchant Center clicks are therefore usually higher and the two never reconcile, and the tools say so in their descriptions, so the assistant compares the two trends instead of adding the totals.
MCP access, including every shopping tool, is part of every GSC Wizard plan, from €17 a month, and every new account starts with a 7-day free trial. Once a trial ends without a subscription, the tools stop answering until you subscribe. See pricing.
Link your shop in GSC Wizard, add one connector URL and sign in. Claude then reads your free listings, product issues, prices and feeds, with nothing to export.
Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.