To connect Google Ads to VS Code, run MCP: Add Server, choose HTTP, enter https://mcp.paidsync.ai/mcp and complete the sign-in prompt, then ask GitHub Copilot about your account. Copilot can then use PaidSync.ai tools for Google Ads, Meta Ads and 12 other platforms without leaving the editor.
VS Code adds MCP servers through a guided command. For a remote server like PaidSync.ai you need:
https://mcp.paidsync.ai/mcp.The command writes the entry for you. You can also write it by hand in the portable format.
| Setting | Value |
|---|---|
| Command | MCP: Add Server |
| Type | HTTP (HTTP or Server-Sent Events) |
| URL | https://mcp.paidsync.ai/mcp |
| Where it is saved | Global writes ~/.copilot/mcp-config.json |
| Transport | VS Code tries HTTP Stream first and falls back to SSE |
VS Code's docs say headers are optional and usually carry authentication. If your sign-in prompt does not appear, add a PaidSync.ai API key as a Bearer header. A key reads and previews on Google Ads, and applying a change there needs the OAuth sign-in.
Do these in order. The code box holds the exact setup from VS Code MCP servers docs.
Sign up at paidsync.ai and connect Google Ads on Google's own sign-in screen.
Open the Command Palette, run MCP: Add Server and choose HTTP.
Paste the endpoint from the box below and give the server the ID paidsync.
Select Global to use PaidSync.ai in every workspace, then review the trust and sign-in prompts.
Open chat in an agent session and name the server in your prompt. Check that a PaidSync.ai tool is called and returns output.
Portable MCP config
{
"mcpServers": {
"paidsync": {
"type": "http",
"url": "https://mcp.paidsync.ai/mcp"
}
}
}VS Code's docs suggest naming the server in a prompt and confirming a tool was called. Do the same here.
Setup follows the VS Code MCP documentation, checked on 24 October 2026. VS Code's pages do not describe dynamic client registration, so the sign-in prompt is not confirmed there. Source: VS Code MCP servers docs. Also VS Code MCP configuration reference. Every Google Ads tool is on the Google Ads MCP server page, and the full list of clients is on Connect your ads.
Yes. VS Code adds remote MCP servers through MCP: Add Server, and Copilot chat can then call their tools.
Not if the sign-in prompt appears. A Bearer header with a PaidSync.ai API key is the documented fallback, for reports and previews.
The Global choice writes ~/.copilot/mcp-config.json. A workspace file is also supported.
Yes. The same server exposes Meta Ads tools. See the Meta Ads MCP server page.
PaidSync.ai is free for 15 tasks a month with no card. Pro starts at $99 a month. See pricing.
PaidSync.ai runs 630+ tools across 14 ad and analytics platforms. Connect your accounts once and use them in the AI assistant you already work in.
Get Started Free Book a Demo