adsyncs
Free Trial
View markdown

How it works

A 60-second tour. You stay in your AI client — AdsSyncs handles the platforms behind the scenes.

The three pieces

1. Your AI client (Claude Desktop, Codex, Antigravity) Where you actually type. It speaks the Model Context Protocol — a standard way for AI clients to call tools on remote servers.

2. The AdsSyncs dashboard at app.adsyncs.net Where you sign in, connect Google / Meta / LinkedIn / Bing, and choose which ad accounts the AI can see. It's the source of truth for which accounts belong to which workspace.

3. The AdsSyncs MCP server at https://mcp.adsyncs.net/mcp Where the tools live. When your AI calls meta_ads_get_campaign_performance, the request lands here, we use your stored credentials to ask Meta, and stream the answer back to your chat.

What happens when you ask the AI a question

  1. You type "What did campaign A spend last week?"
  2. The AI picks a tool — say google_ads_get_campaign_performance — and sends it to AdsSyncs.
  3. AdsSyncs checks who you are (OAuth 2.0 token from your client) and looks up which Google Ads accounts your workspace authorized.
  4. AdsSyncs calls Google Ads with your refresh token, gets the data, formats it for the AI.
  5. The AI writes you an answer.

You don't see steps 2–4. The whole loop takes seconds.

Read by default, writes are opt-in

Every tool is tagged read, transform, or write.

  • Read tools (e.g. list_campaigns, get_search_terms) are always available.
  • Transform tools rephrase or summarize data without hitting the platforms.
  • Write tools (e.g. pause_campaign, update_campaign_budget) require turning Writes on for that provider in app.adsyncs.net/settings. Off by default.

This means an AI you connect today can read everything but cannot change anything until you say so.

Always fresh, never installed

The MCP server runs on Google Cloud Run with auto-traffic-shifting. New tools, new providers, bug fixes — everyone gets them at the same moment. There's nothing to update on your laptop.

Architecture details

AdsSyncs is built on Fastify + the MCP TypeScript SDK. The dashboard is a Next.js app backed by Supabase, with ad-platform credentials encrypted at rest. The full system design lives in docs/system design/remote_mcp/ — see Remote endpoint and Authentication for the protocol details.

Next steps