01
What WebMCP actually is
The whole idea, without the jargon — what changed, what it is not, and why it arrived now. Start here even if you have never touched AI.
New course & community · opening [YOUR LAUNCH DATE]
Soon, nobody will visit your site.
They’ll send an AI assistant instead — and it will only be able to use the sites that are ready for it. WebMCP is the new web standard that makes yours one of them.
This is where you learn how — in plain English, on a site you already own. No prior experience with AI required.
Free to join the list · no card, no spam
Course + community hosted on Skool
I want to learn how to make my website work with AI agents.
webmcp.academy
Asked the site about the course
WebMCP Academy teaches exactly that — how to make a site you already own usable by AI agents. It opens [YOUR LAUNCH DATE]. Want me to put you on the waitlist?
Yes please.
webmcp.academy
Added them to the waitlist
Done — you’re on the list.
This is what an agent-ready site looks like. Never once looked at the page.
Why now
This has happened to the web twice.
Both times, the businesses that moved early didn’t just keep up. They picked up all the customers the slower ones couldn’t serve.
1995
You needed a website
If customers couldn’t find you online, you slowly stopped existing. Plenty of good businesses waited it out and never recovered.
2007
It had to work on a phone
Same site, new kind of visitor, completely different requirements. The ones who shrugged watched their traffic quietly leave.
Now
It has to work for agents
People are starting to ask an assistant instead of opening a browser. If it can’t use your site, it will quietly recommend one it can.
Being visible to agents is not the same as being usable by them. Right now, almost every site on the internet is the first and not the second.
In plain English
It’s a menu your site hands the assistant.
Instead of leaving an AI assistant to squint at your page and guess, WebMCP lets your site say plainly: here are the things you can do here. Check availability. Search the catalogue. Join the waitlist. The assistant picks one and your site does the work — the same work it already does for people.
Every site today
- The assistant takes a picture of your page and tries to work out what everything does.
- It clicks around, gets stuck on a cookie banner, gives up, tells the customer it couldn’t.
- It cannot tell a “cancel” button from a “confirm” one until it has already pressed it.
- Change your design and everything it learned is wrong again.
Your site, after
- You decide exactly what an assistant is allowed to do, and name each one in your own words.
- It asks for the one it needs. Your site answers straight away.
- Everything runs as that customer, signed in as themselves, with your usual rules in place.
- Redesign whenever you like. The menu is what the assistant relies on, not your layout.
A real standard. Being built at the W3C by Google and Microsoft engineers.
Already in browsers. Chrome has begun rolling it out to the public.
Assistant-agnostic. Works the same whichever AI your customer uses.
What you learn
Six lessons. One agent-ready site.
Built for site owners, marketers and founders — not just developers. You work on the site you already have, and finish with it working.
02
Why it matters for you
Where agent traffic actually comes from, what it is worth, and the honest cost of deciding to wait another year.
03
Choosing what to offer
The lesson that decides whether this works: picking the small handful of things an assistant should be able to do on your site, and naming them well.
04
Adding it to your site
Step by step, on the platform you already use. Copy-and-paste starting points you adjust to your own site — nothing rebuilt from scratch.
05
Staying in control
What an assistant should never be allowed to touch, how to make sure it always asks first, and how to sleep at night afterwards. Nobody skips this one.
06
Going live & proving it
Turning it on, testing it with a real assistant, and knowing for certain it worked — not just hoping.
The community
You won’t be doing this alone.
This is brand new territory — there is no ready-made answer waiting for you online yet. So the lessons come with a working group of people doing the same thing to their own sites at the same time.
Everything lives in one place on Skool: the lessons, the templates, and the room where you ask when something does not behave.
Join the waitlistInside the community
- The six lessons, at your own pace
- Starting templates you adapt to your own site
- A room to ask when something misbehaves
- Updates as the standard moves — it is still changing
- [ANYTHING ELSE YOU ARE INCLUDING — live calls, teardowns, office hours]
Practise what we teach
This page is agent-ready too.
Open this site in a browser that supports WebMCP and ask your assistant about the course. It will not read the page — it will ask the page. These are the two things we let it do.
Tell me about the course
What it covers, who it is for, what it costs and when it opens — answered by the site itself, always current.
Put me on the waitlist
Signs the visitor up without them filling in a single box — and always checks with them before it does.
Who’s behind it
Taught by
[YOUR NAME]
[TWO SENTENCES: what you have built with WebMCP, what you did before, why you are the person to learn this from. Specific beats impressive.]
[@handle] · [link]
Placeholder — replace
“[A REAL QUOTE once you have early members — ideally someone non-technical saying they got it working]”
Placeholder — replace
“[A SECOND QUOTE, or swap this card for logos of sites that have shipped it]”
The waitlist
Get in before the doors open.
The course and community open [YOUR LAUNCH DATE]. Everyone on the list hears first — and joins at [YOUR FOUNDING-MEMBER OFFER] before it goes to the public price.
- First access when it opens, and the founding-member price
- [WHAT ELSE THEY GET FOR JOINING EARLY — a guide, a template, an invite]
- Nothing else. One email when there is genuinely something to say.
Questions
What people ask first.
Do I need to be a developer?
No. You need to be able to add one line to your site’s settings — or have whoever looks after it do that bit. We show you exactly what goes where. The genuinely hard part of this course isn’t technical anyway: it is deciding what your site should let an assistant do, and that is a decision about your business, not your website.
What if my site is on WordPress or Shopify?
That is exactly the situation lesson 04 is written for — you keep the site you have. [CONFIRM THE PLATFORMS YOU WILL COVER STEP BY STEP, e.g. WordPress, Shopify, Squarespace, Wix, Webflow, custom builds.]
Isn’t it too early to bother with this?
Early is the entire point. Chrome has already begun shipping it, and the part that takes real thought — working out which things your site should offer an assistant, and which it absolutely should not — does not change when the standard settles. Do that thinking now and switching it on later is the easy half.
Will an AI be able to break something on my site?
Only if you let it, which is why lesson 05 exists. You choose every single thing an assistant is allowed to do — it can do nothing you have not deliberately offered, it acts as the customer who is already signed in, and anything consequential asks that person first.
What does it cost, and when does it open?
It opens [YOUR LAUNCH DATE] on Skool at [YOUR PRICE]. Everyone on the waitlist gets in first at [YOUR FOUNDING-MEMBER OFFER]. Joining the list costs nothing and commits you to nothing.
Being early is the whole advantage.
Before long every site will do this. Today it is a reason to pick you over the one that hasn’t.
Join the waitlist