Vibery Sites is WordPress hosting with an API that AI agents can actually drive. You connect your assistant once, and from then on you manage every site you own by asking for what you want: deploy a site, write a post, import products, take a backup, restore to last Tuesday. Your assistant proposes the action, Vibery executes it, and you approve what happens.
It is not an AI website builder. Nothing runs unattended. Vibery is infrastructure for agents, not an agent.
How does it work?
Vibery exposes its whole surface over MCP, the Model Context Protocol. Any MCP client can talk to it: Claude Code and Claude Desktop sign in with OAuth, while Codex and scripts use an access token.
Once connected, your assistant sees every site you have and can call around 42 tools against them. Those tools cover the things you actually do on a WordPress site:
- Provision a new hosted site from a template, live on HTTPS in about thirty seconds
- Connect a WordPress you already run on any host, through a revocable application password
- Create and edit posts, pages, media, menus and settings
- Run a WooCommerce store: products with variations, orders, customers, coupons, refunds
- Take backups, restore to any point in time, and export the whole site as a portable bundle
- Create rules that run on a schedule or on an event
Why does an agent need special hosting?
Because wp-admin is built for a human with a mouse, and the WordPress REST API on its own is not enough to run a site end to end. There is no standard way to provision a site, no standard way to back one up, no standard way to move it somewhere else.
An agent driving five client sites also needs something wp-admin never gives you: one control plane. One connection that sees all of your sites, so "back up all five and then update the SEO plugin" is a single conversation rather than five logins.
And the heavy work has to happen somewhere sane. Bulk product imports, media scans and backups run on our infrastructure, not on the client's cheap shared hosting, so they land as clean writes instead of timing out halfway through.
How do I get started?
The beta is invite only. Once you have an invite, connecting takes one command:
- Run
claude mcp add --transport http vibery https://site-manager-api.sites.vibery.app/mcp - Approve the sign-in link that arrives in your email
- Ask your assistant to list your sites
That is the whole setup. From there you can deploy your first hosted site by name, or connect a WordPress you already own by pasting in an application password generated from its own wp-admin.
What does the beta include?
During the closed beta you get hosted WordPress on *.sites.vibery.app, up to three sites per account, free. You can point your own domain at a hosted site and a certificate is issued automatically. You can connect unlimited existing sites across the standard, WooCommerce and plugin tiers. Backups go to our storage, restore to any point, and export as a bundle you keep.
What is not there yet: self-service signup and paid plans, a template library beyond the starter set, and a formal status page with uptime commitments. It is one region and one operator today, and we would rather say so than let you discover it.
If you already run two or more WordPress sites and already live in Claude Code or Codex, this was built for you. Ask for an invite.
No comments yet