MCP connector · For head office

Build the whole catalogue
by describing it.

Amplaro connects to Claude over MCP, so a head office marketing team can build campaign packages and load a whole marketing calendar by attaching the plan it already wrote. Everything arrives as a draft for a person to publish. Then every franchise partner can order it for their own store.

What it looks like

The campaign brief is now a chat message.

Head office
Prepare a two-week Buy 1 Get 1 Free campaign for all stores. Budget 50 to 200 per store, 100 recommended. Headline "BOGO in {store}", and pre-fill the local line with "This week only at {store}". Use the hero image from our drive.
Claude
Done. I checked Amplaro's packaging rules, pulled the image in and created the campaign as a draft:
BUY 1 GET 1 FREEFACEBOOK & INSTAGRAM
Buy 1 Get 1 Free
$50 to $200 per store · 7 or 14 days · headline "BOGO in {store}"
Draft · ready for your review
Looks good, publish it.
Published. Every franchise partner now sees it in their app, personalised with their own store name, ready to order.
How it works

Three steps, once.

1

Connect

Generate a private connection link in the Amplaro console and add it to Claude as a connector. One click, revocable anytime, scoped to your organisation only.

2

Prompt

Describe the offer, the budget range, the runtime and the visuals. Claude reads Amplaro's packaging rules, so headlines fit, budgets validate, and store-name personalisation is used out of the box.

3

Review & publish

Every AI-built campaign lands as a draft in your console. You check it, hit publish, and it appears in the partner app for every store, ready to order in two minutes.

Built for real campaign work

Claude can create Facebook and Instagram campaigns, local Search campaigns and Google Maps promoted pins. It fills in the dynamic fields, so "BOGO in {store}" becomes each store's own name automatically, from Brisbane CBD to Broadbeach.

It also knows the rules of the road: no promo codes in Google ad text (it uses promotion extensions instead), no competitor trademarks in copy, character limits per channel. The same validation as the console applies to every AI-built campaign.

Safe by design

One private key per organisation, shown once and revocable in one click. Everything Claude builds is marked "Claude (MCP)" in your activity log, starts as a draft, and never touches budgets or billing. Spending only happens when a franchise partner orders.

At scale

Build a whole quarter in one pass.

One campaign is quick to set up in any console. A season of them, across several markets, is not. Type the title, paste the copy, set the dates, pick the channels, set the budget range, save, repeat. For a head office team that is hours of work producing nothing new, because the thinking already happened in the planning document.

Amplaro takes the document instead. Attach the plan, ask for the campaign packages and the marketing calendar to be created, and they arrive as drafts. Up to sixty calendar entries in a single pass, checked against what is already there so nothing doubles up.

Attach the plan you wrote Packages and calendar created as drafts Head office reviews and publishes Every partner can order it

As far as we can tell, Amplaro is the first franchise marketing platform with an MCP connector. What that changes for a team running local marketing across hundreds of stores is on running LSM at scale.

The guardrails

What it will not do on its own.

Anything that can create things inside your marketing platform should be careful at the edges. These limits are deliberate, and they are the reason this is safe to hand to a marketing team.

It creates drafts

Nothing goes live from a chat. Packages arrive as drafts and a person at head office publishes them.

It never guesses a date

If the plan does not give a clear date it asks. A campaign that starts on a date nobody chose is worse than one that is late.

Running it twice changes nothing

Entries are matched on title and start date, and duplicates are skipped by default, so re-running the same document is safe.

It cannot spend money

No budgets, no billing, no launching. Spend only happens when a franchise partner orders a campaign for their own store.

Everything is logged

Every action is written to the activity log as Claude (MCP), against your organisation, so there is a record of what was created and when.

One key, revocable

A private connection link per organisation, shown once and revoked in one click. Scoped to your organisation and nothing else. More on the security page.

The partner side stays deliberately plain. Franchise partners do not prompt anything, they pick an approved campaign and a budget. Why that split matters is on brand protection.

Why it matters

Campaign production stops being the bottleneck.

A seasonal push across nine markets. A response to a competitor promotion that has to be live around every store this weekend. What used to be an afternoon of form filling per campaign becomes a sentence. Head office stays in control of what gets published, partners keep their two minute ordering flow, and the catalogue stays full and current instead of slowly going stale.

Works with Claude on web, desktop and mobile. It is one of the two things that make Amplaro different from every other franchise marketing platform. The other one is targeting each store's real delivery area.

Book a demo See the full flow
Common questions

Building campaigns with AI.

What is MCP, and why does it matter for franchise marketing?

MCP is an open standard for connecting an AI assistant to a real system, so it can read and create things rather than just talk about them. For a franchise marketing team it means the campaign catalogue can be built by describing it, instead of by filling in the same form a few hundred times. As far as we can tell, Amplaro is the first franchise marketing platform to offer one.

Can head office build campaign packages in bulk?

Yes. That is the point of it. You can create a run of packages in one pass and load up to sixty calendar entries per call, so a quarter or a season goes in at once rather than one screen at a time. Everything arrives as a draft for someone at head office to check and publish.

Does the AI publish campaigns by itself?

No. Packages are created as drafts unless a person explicitly says otherwise, and publishing is a human action in the console. Nothing a chat produces is visible to franchise partners until head office says so.

Can it load our marketing calendar?

Yes. Attach the plan you already wrote, whether that is a document, a spreadsheet or a deck, and ask for the calendar entries to be created. It reads the dates out of your plan rather than working them out.

What happens if we run the same plan twice?

Nothing changes. Entries are matched on title and start date, and duplicates are skipped by default, so re-running the same document is safe. If you want an update instead of a skip, you say so.

Does it invent dates or offers?

It refuses to guess dates. If the plan does not give a clear date it asks rather than picking one, because a campaign that starts on a date nobody chose is a bigger problem than a campaign that is late. Offers and copy come from what you give it.

Who can see and use the connection?

One private connection link per organisation, shown once when it is created and revocable in one click. It is scoped to your organisation only, and every action it takes is written to the activity log as Claude (MCP).

Do franchise partners get to use AI as well?

Not inside Amplaro, and that is deliberate. The partner flow stays pick an approved campaign, pick a budget, pick a date. Generative work belongs at head office where it runs on your own assets and approved copy, with a person publishing. See brand protection for why that split matters.

Keep reading

Related pages

Building a full shelf of packages per sector is where this saves the most time. See franchise industries.