Switch to Danish

Ads MCP. Every change waits for a yes.

The Ads MCP is what I use when an AI assistant works in ad accounts: Google Ads, Meta, TikTok and LinkedIn, all from one conversation. I built it myself, and it’s for my own work only.

Christian from behind at his laptop, seen through a pane of glass

01The connection

It gives the assistant a set of tools inside the ad account.

MCP is an open standard for connecting AI assistants to other software. A server like this one gives the assistant a defined set of tools in the account, so it can handle what I’d otherwise click through by hand. I describe the task, and the assistant does it.

Christian in profile at his desk, holding a mug
Christian from behind at a screen on his desk

The tools

Pull numbers, write ads, adjust budgets and create campaigns.

02The big picture

The assistant does the legwork in the accounts, so I can stay focused on the big picture.

Answering a budget question used to mean clicking through four ad platforms. Now I ask in the conversation, and the assistant pulls the numbers from every platform into one answer. The time that frees up goes to strategy, and to seeing how the ads fit with the rest of the marketing.

The questions

  • How much have we spent?
  • What’s working?
  • Where should the money go?
  • What should we test next?

03The safeguards

Four layers stand between the assistant and the account.

The assistant can read anything in the accounts it has access to. Any change has to get through four layers, and each one narrows what it can touch.

  1. Dry run

    Every change runs as a dry run until I confirm it.

  2. Approved accounts

    Confirming only works on accounts I’ve put on the list. With an empty list, nothing goes through.

  3. Ceiling

    Any daily budget above the ceiling is refused, even after I confirm it.

  4. Pause

    New campaigns start paused and spend nothing until I switch them on.

The log. Every attempt is logged, whether it was a dry run, a change or a refusal. Access tokens and lead details never go into the log.

04The platforms

Google and Meta have their own. I built the rest.

Google’s own server can read an ad account but can’t change anything. Meta’s can read, create and edit, so for Meta I’ve only built what it doesn’t cover. TikTok and LinkedIn run through the same server. That’s the state of play in October 2026.

  • Google Ads

    Reads and changes budgets, bids, status, ad copy and extensions.

  • Meta

    Uploads from a local file, and new creative on a live ad without losing its likes and comments.

  • TikTok

    Reporting, status, budgets, uploads and campaign builds.

  • LinkedIn

    Reads campaigns, ads, performance and demographics. It can’t make changes yet.

05The decision

I read the dry run before I say yes.

The assistant proposes the change and runs it as a dry run. The result shows what would happen, and whether the platform or the tool itself did the checking. The change only goes through once I’ve read it, and nothing runs in a client’s account without me in the loop.

  • The assistant.

    Proposes and tests.

  • Me.

    Reads and confirms.

Want to see it in action? Happy to walk you through it.

Let’s talkcb@bucca.dk