To connect Google Merchant Center to Claude, first decide whether you need analysis of exported data or an authenticated integration that reads live account information. Those are different projects.
Do not assume there is a verified native Merchant Center connector available in every Claude account. A custom connection requires a compatible integration and the necessary authorization.
Option 1: analyze an export
For a one-off review, export a relevant product or issue report, remove unnecessary sensitive information, and provide the file to Claude where uploads are supported.
Explain the task precisely: group issue types, compare product titles, or identify rows missing a known field. Include the meaning of columns and the period covered.
This is a snapshot. Claude cannot infer that the current account still matches the uploaded file, and suggested corrections need review before application.
Option 2: use an authenticated MCP integration
Claude supports custom connectors using remote Model Context Protocol servers. An MCP server can expose selected operations from an external service.
For Merchant Center, a developer can design a server that authenticates to Google’s Merchant API and presents narrowly scoped tools to Claude. This is an implementation approach, not a claim that Anthropic or Google supplies a particular ready-made connector.
The server must handle credentials, account permissions, request validation, and errors.
Use the current Google API
Google’s developer documentation states that Content API for Shopping reached its sunset on August 18, 2026. New implementation work should use the current Merchant API guidance.
The quickstart includes a Google Cloud project, authentication, and developer registration. Follow the current documentation rather than pasting credentials into a chat.
An old tutorial using deprecated endpoints may need substantial revision.
Start with read-only tasks
A sensible first tool retrieves product issues or catalog details for a specific authorized account. Test the result against a known account sample.
Only add write operations when there is a clear need. Define what can change, how proposed modifications are reviewed, and how failures are logged.
For example, “suggest improved titles” and “replace live titles” should be distinct operations with different review expectations.
Common integration mistakes
A connector URL alone does not authorize access to Google. Google authentication, Merchant Center permissions, and the Claude connector setup all need to work.
Remote connector reachability also matters. Anthropic explains that remote MCP connections originate from its infrastructure, which can affect servers behind a private network or firewall.
Frequently asked questions
Can I connect without coding?
An export-based analysis may require no custom development. Live access depends on an available compatible connector.
Should I paste API keys into Claude?
Use the integration’s supported authentication and secret-management mechanisms.
Can Claude fix suspensions automatically?
An assistant can help analyze information. Google retains control over reviews and enforcement decisions.
Related reading
What Is Google Merchant Center? A Beginner’s Guide
How to Fix a Google Merchant Center Suspension
Official sources
https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
https://developers.google.com/merchant/api/latest-updates
https://developers.google.com/merchant/api/guides/quickstart/overview
https://developers.google.com/merchant/api/guides/quickstart/authentication?hl=en