Let Codex handle the repetitive ad work.

Add PaidSync.ai once and Codex can pull reports, check pacing and prepare changes across Google Ads, Meta Ads and 12 more platforms.

Example data

Let Codex run the repetitive ad work

Reports, pacing checks and prepared changes across 14 platforms. With its approval mode set to writes, Codex asks before any tool that is not read only.

Example data

Listed in Claude, ChatGPT and GitHub. Approved by the ad platforms you run.

Listed in

Approved by

OpenAI
Select Partner
Google Ads API
Standard Access
Google Partner
Meta-approved app
TikTok API
Platform Partner
LinkedIn-approved
Advertising API app

Built by Ahmed Ashraf, who led paid media at Scandiweb, a 2025 Google Premier Partner (top 3% of agencies).
10+ years$500M+ in ad budgets$1B+ client revenue.

  • 5platforms to build campaigns on
  • 630+tools
  • 14ad and data platforms
  • Freeplan, no card

Why PaidSync.ai in Codex

  • Two commandscodex mcp add, then codex mcp login. Codex registers itself with PaidSync.ai, so there is no client ID or key to paste.
  • Every platform you connectThe same entry reaches Meta Ads, LinkedIn Ads, TikTok Ads, GA4 and every other platform you connect in PaidSync.ai.
  • Headless runs are possibleFor runs where nobody can sign in, bearer_token_env_var sends a key in the Authorization header. Applying a Google Ads change still requires the OAuth sign-in.
  • You pick which accounts it seesAfter each sign-in you tick the ad accounts for the workspace, and Codex only sees those.

What works in Codex and what does not

What works

Two commands codex mcp add, then codex mcp login. Codex registers itself, so no client ID or key is pasted.

One setup, three places The CLI, the IDE extension and Codex in the ChatGPT desktop app share ~/.codex/config.toml.

Writes with an approval mode Set default_tools_approval_mode to writes and Codex asks before any tool not marked read-only.

What does not, or needs checking

Headless runs use a key bearer_token_env_var sends a key in the Authorization header. Applying a Google Ads change still requires the OAuth sign-in.

Sign-in may need a nudge If the IDE extension or the app lists paidsync as needing a sign-in, select Authenticate.

No plan or region limit named The connect guide names no Codex plan or region requirement.

How it works in three steps

These are the commands you run in your terminal.

  1. Add the server

    Run the command in your terminal. It writes an mcp_servers entry to ~/.codex/config.toml.

    Run in your terminal
    codex mcp add paidsync --url https://mcp.paidsync.ai/mcp
  2. Log in

    Run the login command. A browser window opens, so sign in with your PaidSync.ai login and Codex stores the token.

    Run in your terminal
    codex mcp login paidsync
  3. Check and ask

    Type /mcp in a Codex CLI session to see paidsync listed, then ask for your accounts.

Cheaper than an agency. Faster than a freelancer.

Start free. Scale with your team. Cancel anytime.

Limited offer
Free
Explore before you commit.
$0/month
Free forever.
Start free
  • No credit card needed
  • No time limit
  • MCP read and write access
  • API access
  • Claude, ChatGPT and any agent

  • 15 tasks a month
  • All 14 ad platforms
  • Full analysis suite, 630+ tools
  • Upgrade anytime
Pro
For solo operators.
$99/month
Billed monthly, cancel anytime
Tasks
Get started
  • 600 tasks a month
  • 1 seat
  • MCP read and write access
  • API access
  • Claude, ChatGPT and any agent

  • Everything in Free, plus
  • Top ChatGPT and Claude models
  • Cloud agents on your schedule, hourly to monthly
  • PMax insights on every platform
  • Wasted spend alerts
  • Anomaly detection
  • Unlimited ad accounts
  • Up to 10 brand spaces
Prefer we run it for you?
Done For You
We run your ad accounts and automations end to end.
  • Full campaign management
  • Custom agents for your process
  • Dedicated success manager
  • Advanced systems in your workflow
  • SSO and DPA on request
Contact us
We reply within 1 business day
Per-tier options, Team seats, and the full FAQ. Compare full pricing →

Frequently asked questions

How do I connect Google Ads to Codex?

Sign up at paidsync.ai and connect Google Ads in the dashboard. Then run codex mcp add paidsync --url https://mcp.paidsync.ai/mcp and codex mcp login paidsync, and sign in with your PaidSync.ai login. The same entry reaches every other platform you connect.

Do the CLI, the IDE extension and the desktop app each need a setup?

No. They share ~/.codex/config.toml, so a server added in one is there in the others. If one lists paidsync as needing a sign-in, select Authenticate and sign in with your PaidSync.ai login.

Does Codex need an API key?

No. OAuth is the primary path. For headless runs, bearer_token_env_var in config.toml sends a key in the Authorization header, never in the URL. Applying a change to Google Ads still requires the OAuth sign-in.

Can Codex change my campaigns?

Yes. Over MCP the human check is Codex's own approval prompt. Set default_tools_approval_mode to writes and Codex asks before any tool that is not marked read-only.

Where does the config live?

Codex keeps MCP servers in ~/.codex/config.toml, or in .codex/config.toml inside a trusted project.

How much does PaidSync.ai cost?

The Free plan includes 15 tasks a month with no credit card and no time limit. Pro starts at $99 a month for 600 tasks. Team starts at $249 a month for 5 seats and 6,000 shared tasks.

Start handing ad work to Codex.

Add PaidSync.ai once, then ask in plain words.