Vibery Sites — WordPress hosting built for AI agents (closed beta)

WordPress hosting built for AI agentsPoint Claude at it. Ship sites.

Run every WordPress and WooCommerce site you own from the AI tool you already use. Vibery provisions, runs, backs up and restores sites over MCP. Your assistant does the work. You approve every change.

01 Your assistant sends the request over MCP

02 Vibery provisions it on our infrastructure, about 30 s

03 A live HTTPS site comes back. You approve what happens next

You run more than one WordPress site.

Two or twenty, the pain has the same shape: every site is its own login, its own plugin stack, its own Saturday. Tick the ones that sound like you.

Freelancers with client sitesSmall agenciesFounders with several brandsDevelopers who avoid wp-admin

0 / 6Tick what sounds like you

from “deploy” to a live HTTPS site, measured in the beta proof run

0command

to connect Claude Code. It signs in with the same email link you use

0unattended actions

every change traces back to something you asked for and approved

This is the whole workflow.

No dashboard hopping, no FTP, no wp-admin tabs. Your assistant talks to Vibery over MCP and reports back with a URL. The transcript is a real session from the beta proof run, trimmed.

$ claude mcp add --transport http vibery https://site-manager-api.sites.vibery.app/mcp
$ claude
> Deploy the Blog Starter template as “bakery”, then tell me the URL.
⏺ vibery.execute(templates.deploy, {template:"blog-starter", name:"bakery"})
⏺ status: provisioning → active (31 s)
✓ https://bakery-8a8188a7.sites.vibery.app is live.
> Import products from ./menu.csv and schedule nightly backups.
⏺ 24 products created · 2 need a price, listed below.
⏺ Rule created: backup every day at 03:00.
— you review, approve, done.

Sign in with an email link
No password. Beta accounts are created by invite; you get a magic link, approve once, and you are in the console.
Connect your AI tool
One command for Claude Code. It signs in with the same email link. Codex and scripts use an access token you create in Settings.
Ask, approve, ship
Deploy from a template, connect a site you already run, manage content and the store, restore to any backup. Every action is something you asked for.

A Tuesday with five sites, before

Log into five dashboards, five password-manager entries, two expired sessions
Update the same plugin five times, hold your breath five times
Check five backup plugins actually ran. Two did
Client asks for “a site like the last one”. Block out Saturday

The same Tuesday, after

“Show me anything that changed on my sites since Friday.” One answer
“Back up all five, then update the SEO plugin.” Restore point first, every time
“Which backups ran last night?” A list, with sizes and times
“Deploy the agency template as acme-dental.” Live before the call ends

What you get

Everything an agent needs to run a site.

Each of these is a tool your assistant can call today. The same actions are buttons in the console when you would rather click.

Deploy from a template

Pick a template, name the site, get a live HTTPS address on sites.vibery.app in about half a minute. Templates carry the whole site: theme, plugins, content. Make your own from any site you host.

Connect a site you already have

Any WordPress on any host, through a revocable application password. No plugin install for the standard tier. Cut access from wp-admin at any time, nothing stays behind.

Run the store

Products with variations, orders, customers, coupons, refunds. Bulk work runs on our side, not on the site’s server.

Backup and point-in-time restore

Portable bundles you can download. Restore a hosted site to any past backup, or move it out entirely.

Content, SEO, automation

Posts, pages, media, menus and settings. Rank Math scoring when installed. Rules that run on a schedule or on events.

What the beta includes, and what it does not yet.

We would rather tell you the edges now than let you find them.

In Available now

Hosted WordPress on *.sites.vibery.app, up to 3 sites per account, free during the beta
Connect unlimited existing sites: standard, WooCommerce, and plugin tiers
MCP endpoint with OAuth sign-in for Claude Code, access tokens for Codex and scripts
Backups to our storage, restore to any point, export as a portable bundle
Tenant isolation: your token sees only your sites, revoke it in one click

Not yet Coming after the beta

Custom domains on hosted sites (today: our subdomain)
Self-service signup and paid plans (indicative: from $24 per month, priced per site)
A template library beyond the starter set. Register your own from any hosted site today
Status page and formal uptime commitments. It is one region, one operator, and we say so

Straight answers.

Is this an AI website builder?

No. Nothing runs unattended. Your own assistant proposes actions, Vibery executes them, and you see and approve what happens. It is infrastructure for agents, not an agent.

Do I need Claude?

Any MCP client works: Claude Code and Claude Desktop sign in with OAuth, Codex and scripts use an access token. You can also do everything from the console without an assistant.

Can I bring my existing WordPress sites?

Yes, as many as you like. Connect each with a WordPress application password from its admin. We never need hosting or database credentials, and you can revoke access from wp-admin in seconds with nothing left installed.

What happens to my hosted sites when the beta ends?

They keep running. Export is available at any time as a portable bundle you can restore anywhere. If we introduce paid plans, beta accounts get notice and a migration path first.

Who is the beta for?

People who already run two or more WordPress or WooCommerce sites and already use Claude Code or Codex: freelancers, small agencies, founders with several brands, developers. If that is you, ask for an invite.