Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, type /mcp, and sign in with your PaidSync login. Claude Code then reaches your Merchant Center accounts through 16 tools: product issues, account status, product performance and data sources, plus product, supplemental feed and Google Ads link changes. Claude Code asks before it runs each tool.
Configure tier. Merchant Center writes have no dry run and apply on the first call, so keep Claude Code's prompt on for write tools.
The command
Claude Code talks to remote MCP servers over Streamable HTTP. PaidSync is one of them. Add it once and the same terminal that edits your code can report on and manage your Merchant Center campaigns.
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcpBy default that registers the server for the current project only. Add --scope user to make it available in every project on your machine. Run claude mcp list to confirm it is there, then start a session and type /mcp to sign in.
5-Step Setup
Sign up at paidsync.ai/signup
Takes 10 seconds. Google or email sign-in. The free plan is 15 tasks a month at $0, no card.
Connect Merchant Center in the PaidSync dashboard
Click Connect on Merchant Center and sign in with the Google account that has access to your Merchant Center. Merchant Center authorizes via Google OAuth with the content scope, and PaidSync never sees your Google password.
Already inside Claude Code? Ask it to run connect_merchant_center. The tool returns a link to open in your browser.
Pick the ad account Claude Code should work on
Inside a session, list_merchant_accounts shows the accounts your Google login can open, sub-accounts under a multi-client account included, and set_active_merchant_account picks the one Claude Code works on.
Add PaidSync to Claude Code
In your terminal, run:
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcpStart a session, type /mcp, pick paidsync, and sign in with your PaidSync login in the browser window that opens. Claude Code stores the OAuth token for you. No key is pasted anywhere.
Setting this up for a team? Commit a .mcp.json at the repo root so every engineer gets the same connector:
{
"mcpServers": {
"paidsync": { "type": "http", "url": "https://mcp.paidsync.ai/mcp" }
}
}Prefer an API key, for example for headless runs? Send it in a header, never in the URL, where it would end up in logs:
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp --header "Authorization: Bearer $PAIDSYNC_API_KEY"In a committed .mcp.json, add "headers": { "Authorization": "Bearer ${PAIDSYNC_API_KEY}" } so the key stays in each engineer's environment and never enters git. Applying a change to Google Ads still requires the OAuth sign-in. On other platforms a key can apply changes too, so treat it like a password and prefer OAuth.
Test the connection
In a Claude Code session ask: “Which issues are disapproving the most products in my Merchant Center”
Claude Code returns each issue's code, severity, destination, country, number of affected products and Google's fix instructions. The connection is live.
Merchant Center prompts to try in Claude Code
Each prompt below maps to tools in the PaidSync Merchant Center group. Claude Code picks the tool. The last column says whether the call can change anything in the ad account.
| Ask | Tools it calls | Changes your account? |
|---|---|---|
| “List my Merchant Center accounts and make Acme the active one” | list_merchant_accounts, set_active_merchant_account | No |
| “Which issues are disapproving the most products, and how do I fix each one” | list_product_issues | No |
| “Is my Merchant Center account at risk” | get_merchant_account_status | No |
| “List every Google Ads account linked to my Merchant Center” | merchant_list_links | No |
| “Which products got impressions but no clicks in the last 28 days” | get_product_performance | No |
| “List my products marked out of stock, with their price” | list_products | No |
| “Create a supplemental feed called Holiday Sale Prices for my US products in English” | merchant_create_supplemental_feed | Yes, after you confirm |
Run it headless with claude -p
The -p flag runs Claude Code without the interactive session. Sign in once through /mcp and the stored OAuth token carries over. A report that lands in a file looks like this:
claude -p "Pull the Merchant Center product issues and write a list of the issues that disapprove the most products." \
--allowedTools "mcp__paidsync" \
--output-format json > reports/merchant-center-$(date +%F).jsonReads run straight through, and so do writes. --allowedTools "mcp__paidsync" allows every PaidSync tool, writes included, with no prompt. For an unattended job, allow only the read tools it needs, each by name as mcp__paidsync__tool_name.
What reads and what writes
Of the 16 Merchant Center tools, 9 only read and 5 can write. Reads cover accounts, product issues, account status, products, product performance, links and data sources. Writes cover products, supplemental feeds and Google Ads links. Merchant Center writes have no dry run and apply on the first call, and product and link deletes need no confirm flag.
Over MCP, the approval step is Claude Code’s own prompt. It asks before it runs a tool unless you allowed it with --allowedTools or in your settings. PaidSync adds checks on its side. Deletes, pauses and budget changes need confirm_destructive, and a pre-write rule check blocks unsafe arguments. The approval card, and Undo on an applied card whose change has a safe inverse, apply only in the PaidSync workspace.
What Claude Code cannot do on Merchant Center
- Merchant Center changes apply on the first call with no preview, so keep Claude Code's prompt on for write tools.
- The first request to an account registers PaidSync with it, which needs admin access and takes about 5 minutes to take effect.
- Merchant Center reports run one to two days behind.
- Product performance covers up to 1,000 products per request.
- PaidSync lists only the accounts your connected Google login can open.
Frequently Asked Questions
How do I connect Merchant Center to Claude Code?
Sign up at paidsync.ai, connect Merchant Center in the dashboard, then run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp in your terminal. Type /mcp inside a session, pick paidsync, and sign in with your PaidSync login.
Can Claude Code fix product disapprovals?
Claude Code can list every disapproval with its reason and fix instructions. For attribute fixes PaidSync can update products, and Claude Code asks before it runs each write tool.
Does PaidSync also connect Google Ads to Claude Code?
Yes. PaidSync connects both Merchant Center and Google Ads in the same tool set, so Claude Code can compare feed health with Shopping campaign spend in one session.
Does it work in headless mode with claude -p?
Yes. Once you have signed in through /mcp, claude -p reuses the stored OAuth token. Reads run straight through. Writes need care. No one is there to answer the Claude Code prompt, so any write tool you allowed with --allowedTools runs straight through. For an unattended job, allow only the read tools it needs.
Is it free?
Yes. The free plan is $0 for 15 tasks a month with no card. Pro starts at $99 a month and Team at $249 a month.
Merchant Center reports and feed changes. One command in Claude Code.