How it works
How it works
Three pieces, each with one job. No jargon, and nothing that needs a developer.
The companion opens a door on each site. The app is the only place that talks to all your doors. The dashboard and your AI walk through it, with your confirmation.
The companion, on every site
You install one small plugin on each WordPress site, like any other. It opens a door so the app can read the site, and act when you confirm.
It pairs with an 8-letter code. No wp-admin password ever leaves the site: the link is a token, and deactivating the plugin cuts it.
In practice: five minutes per site, no code, and you can turn it off at any time in wp-admin.
The app that sees every site at once
A site only knows itself. The app keeps the list and talks to all of them together: inventory, security map, updates, backups, SEO.
This is also where you decide who can do what, and where every action is logged.
In practice: you ask once “which sites still run an old WooCommerce?” and get one answer for the whole fleet.
Your AI, plugged in through MCP
Connect Claude, Cursor or ChatGPT to the fleet. It reads the inventory, the logs and the SEO of every site.
Writes stay in the dashboard: the app sums up what will change, you confirm, it runs, with a copy taken before.
In practice: “Which sites had failed logins from abroad this week?” answered in seconds, sites listed.
Two ordinary evenings, before and after
A plugin gets an update
Today
- You log into twenty wp-admins, one after another.
- You click Update and cross your fingers.
- Thursday, a client calls: checkout has been broken since Monday.
With wpmcp
- A copy of the plugin is taken on every site first.
- The update runs on the whole group from one screen.
- If something moves, rollback is one click, and the full backup is there if needed.
A site gets hacked on a Saturday night
Today
- Nobody sees it. The site quietly serves spam pages to Google.
- The client calls on Monday, angry.
- You lose a day cleaning up, and rankings take months.
With wpmcp
- The admin account created at 03:12 is flagged within the hour.
- The guard blocks the attacking IPs and lists the files changed overnight.
- You wake up to an alert and a log, not to damage.
Your access stays yours
The first question everyone asks. Here are the plain answers.
The companion lives on your server. Deactivate it and the door is closed, no call needed.
By default your AI looks and reports. Changes go through the dashboard, which asks first.
Every update keeps a copy, and full backups restore the whole site in one click.
Which site, which action, when, and what came of it. You can read it back at any time.
The real questions we get
What is MCP, in one sentence?
A standard for plugging an AI into software. Like a USB port, but for AIs. That is all you need to know.
Do I need to code?
No. Install the plugin, paste the code, done. The rest is plain sentences and buttons.
Which AI is used?
Claude, Cursor, ChatGPT or any assistant that speaks MCP. The fleet AI in the dashboard is included, no key to bring.
Can it break my site?
Any update can break a site, including the ones you click yourself. The difference: here there is a copy before, a check after, and going back is one click.
I only have one site.
It works, and that site gets the security map, backups and SEO. The plan covers 5 sites, so it pays off as soon as you look after a few.
And if I stop paying?
Your sites keep running, untouched. The companion stops acting and the dashboard closes. Nothing is locked inside.
Pair your first site in five minutes.
Create the account, choose monthly or annual, install the companion, paste the code.
