Connect Google Merchant Center to Microsoft Copilot by adding PaidSync as a tool in Copilot Studio. Server URL https://mcp.paidsync.ai/mcp, sign-in with OAuth 2.0. Copilot then checks product approval status, surfaces feed errors, lists disapproved products, and cross-references your catalog with Shopping campaign performance. Product and feed writes are held for your approval. Setup takes under 5 minutes.
For e-commerce advertisers running Google Shopping, Merchant Center health directly affects how much of your catalog is eligible to serve. Copilot gives you a fast way to audit that health through conversation instead of navigating Merchant Center's diagnostic screens.
Ask Copilot how many products in your catalog are approved, pending, disapproved, or excluded. Copilot pulls this from the Merchant Center API and gives you the counts, then can drill into specific disapproval reasons on request.
Ask Copilot to list all active feed errors and warnings in your account. Common issues Copilot surfaces: missing required attributes, price mismatch between feed and landing page, image policy violations, and title/description length issues. These errors suppress product serving and cost impressions.
Ask Copilot which disapproval reason is affecting the most products. Copilot groups your disapproved products by reason so you can see whether to fix one systemic issue or address many individual problems.
Ask about specific products by ID or title, check which products are in a specific category, or find products below a certain price threshold. Copilot queries your product catalog in real time through the Merchant API.
Connect both Merchant Center and Google Ads to PaidSync and Copilot can cross-reference them. Ask which disapproved products are also in your active Shopping campaigns, or which products have the highest Shopping impressions in Google Ads but are currently pending review in Merchant Center.
Go to paidsync.ai/signup. Free plan, no credit card. 15 tasks per month.
In the PaidSync dashboard, click Connect Merchant Center and authorize with the Google account that has access to your Merchant Center. PaidSync requests access through Google's official Merchant API.
OAuth 2.0 is the default. Copilot Studio discovers PaidSync's sign-in metadata on its own and you log in with your PaidSync login. Any change to your account needs OAuth. For read-only use, an API key from PaidSync Settings (format: ps_...) also works, sent as a query parameter named api_key.
Microsoft 365 Copilot reaches custom MCP servers through a Copilot Studio agent. In Copilot Studio open your agent, then Tools, Add a tool, New tool, Model Context Protocol. Server name PaidSync, a short description, and the server URL:
https://mcp.paidsync.ai/mcp
Authentication: choose OAuth 2.0, then Dynamic discovery (PaidSync publishes the discovery metadata Copilot Studio looks for), or API key sent as a Query parameter named api_key with your ps_ key. Transport is Streamable HTTP. Click Create, then Add to agent.
Publish the agent to the Microsoft 365 Copilot channel. Most tenants need an admin to approve it before it appears in Teams and Microsoft 365 Copilot. Copilot Studio needs a work or school account, included with Microsoft 365 Copilot licences or as a standalone Copilot Studio subscription or trial. The consumer Copilot app does not accept custom MCP servers. Field-by-field walkthrough: Connect any ad platform to Microsoft Copilot.
Ask Copilot: "How many products in my Merchant Center are disapproved?" If a count appears with reason details, the connection is live.
GitHub Copilot in VS Code is a different product from Microsoft 365 Copilot. Press Cmd+Shift+P (Ctrl+Shift+P on Windows), run MCP: Add Server, choose HTTP, paste the same URL https://mcp.paidsync.ai/mcp, and sign in when prompted.
For e-commerce teams running on Microsoft 365, having Merchant Center accessible through Copilot means product feed health checks happen inside the same environment as your other work. A disapproval alert in the morning can be triaged in Teams chat without opening a separate browser tab. The agent reaches Teams and Microsoft 365 Copilot once it is published to the Microsoft 365 Copilot channel and, in most tenants, an admin has approved it.
PaidSync also connects Merchant Center to Claude, ChatGPT, Gemini, and Perplexity. Connect once, use any AI.
Yes, through Copilot Studio. Microsoft 365 Copilot reaches custom MCP servers through a Copilot Studio agent, which needs a work or school account. Add PaidSync as a Model Context Protocol tool at https://mcp.paidsync.ai/mcp, sign in with OAuth 2.0, and publish the agent to the Microsoft 365 Copilot channel. Copilot then has live Merchant Center access. GitHub Copilot in VS Code is a separate product and connects to the same endpoint. The consumer Copilot app does not accept custom MCP servers.
Yes. PaidSync offers a free plan with 15 tasks per month at $0, no credit card required. Pro starts at $99/month for heavier use.
Check product approval status, list disapproved products and their reasons, review feed health, check account-level issues, and cross-reference product performance with Google Ads Shopping campaigns.
Partly. Copilot reads every product and feed issue and explains the fix. PaidSync also carries product and feed writes, such as inserting or deleting a product and creating a supplemental feed, each held for your approval. Larger catalogue corrections still belong in the feed source. Nothing here touches campaigns.
Yes. Connect both Merchant Center and Google Ads to PaidSync and Copilot can cross-reference them in the same conversation. Ask which disapproved products are also in your active Shopping campaigns.
Yes. The same PaidSync account works with Claude, ChatGPT, Gemini, Perplexity, and Microsoft Copilot. Connect Merchant Center once and use whichever AI you prefer.
PaidSync connects Merchant Center, Google Ads, Meta Ads, TikTok Ads, GA4, GTM, Search Console, and LinkedIn Ads to Copilot and every major AI. 500+ tools, one account.
Get Started Free Book a Demo