Add a paidsync entry with url set to https://mcp.paidsync.ai/mcp in .cursor/mcp.json, open Cursor Settings, then MCP, and sign in with your PaidSync login. Cursor then has 530+ tools across 14 platforms, including Google Ads, Meta Ads, TikTok Ads and LinkedIn Ads. Cursor asks before it runs each tool unless you turn on auto-run, and most creates preview with a dry run first.
One config entry. OAuth sign-in, no key pasted. Free plan, 15 tasks a month, no card.
Cursor reads MCP servers from .cursor/mcp.json in your project, or from ~/.cursor/mcp.json for every project on your machine. PaidSync is a remote server, so the entry is a single URL:
{
"mcpServers": {
"paidsync": { "url": "https://mcp.paidsync.ai/mcp" }
}
}Save the file, open Cursor Settings, then MCP, and sign in with your PaidSync login when Cursor prompts for OAuth.
Takes 10 seconds. Google or email sign-in. The free plan is 15 tasks a month at $0, no card.
Click Connect on each platform you run. Google Ads authorizes via Google OAuth, Meta Ads via Facebook OAuth, LinkedIn Ads via LinkedIn OAuth and TikTok Ads via TikTok OAuth. Merchant Center, GA4 and Search Console use the same Google sign-in. PaidSync stores the tokens encrypted at rest with AES-256-GCM.
After each sign-in, PaidSync lists the ad accounts that login can reach. Tick the ones that belong in this workspace. Cursor only ever sees the accounts you pick.
Add PaidSync to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project):
{
"mcpServers": {
"paidsync": { "url": "https://mcp.paidsync.ai/mcp" }
}
}Open Cursor Settings, then MCP, and sign in with your PaidSync login when Cursor prompts for OAuth. Tools appear in the agent once the server shows as connected.
Windsurf uses the same shape with serverUrl in ~/.codeium/windsurf/mcp_config.json.
In Cursor chat ask: “List my ad accounts”
Cursor returns the account names and IDs across every platform you connected. Then try: “Show me last 7 days spend by platform”
The same server covers every platform, so one chat can move from Google Ads to Meta to GA4. The last column says whether the call can change anything in the account.
| Ask | Tools it calls | Changes your account? |
|---|---|---|
| “Audit the Google Ads account and list the five biggest fixes” | run_account_audit | No |
| “Which search terms spent money this month with zero conversions?” | get_search_terms_report | No |
| “Show Meta performance by placement for the last 14 days” | get_fb_performance_by_placement | No |
| “Break down LinkedIn spend by job title” | get_linkedin_performance_by_dimension | No |
| “Sessions and key events by source and medium, last 28 days” | run_ga4_report | No |
| “Pause the TikTok campaign with the worst cost per conversion” | pause_tiktok_campaign | Yes, after you confirm |
| “Add these five terms as negatives on the Brand campaign” | add_negative_keywords | Yes, after you confirm |
Reports, audits and lookups only read. Budget, bid, status, keyword, audience and campaign changes are writes. Over MCP, the approval step is Cursor’s own tool prompt, which asks before each call unless you turn on auto-run. On the PaidSync side, most create tools preview with dry_run first, deletes, pauses and budget changes need confirm_destructive, and a pre-write rule check blocks unsafe arguments. Some Google Analytics, Tag Manager and upload tools have no dry run and apply on the first call. The approval card and one-tap undo apply only in the PaidSync workspace.
Sign up at paidsync.ai, connect your ad platforms in the dashboard, then add a paidsync entry with url https://mcp.paidsync.ai/mcp to .cursor/mcp.json. Open Cursor Settings, then MCP, and sign in with your PaidSync login when Cursor prompts for OAuth.
No. The OAuth sign-in is the primary path. Sign in once with your PaidSync login when Cursor prompts and no key is needed. Applying a change to Google Ads requires that OAuth sign-in.
Yes. Cursor asks before it runs an MCP tool unless you turn on auto-run. On the PaidSync side, dry_run previews most creates, and destructive operations need confirm_destructive.
Yes. Commit .cursor/mcp.json in the repo. Every engineer who opens the project gets the connector and signs in with their own PaidSync login.
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.
530+ tools. 14 platforms. One entry in mcp.json.