Disposable WordPress for AI agents
Spin up via API, let your agent work, throw it away. Or skip the API entirely — paste one config into Claude and just say what you want built.
No dashboard. No persistent state. No credit card.
curl -X POST https://api.wp.run/v1/instances \
-H "Authorization: Bearer $WPRUN_KEY" \
-H "Content-Type: application/json" \
-d '{
"php": "8.4",
"wp": "6.9",
"ttl": "2h",
"mcp": true
}'{
"id": "inst_8f2a1c9d",
"url": "https://8f2a1c9d.wprun.site",
"admin_url": "https://8f2a1c9d.wprun.site/wp-admin",
"app_password": "aB3k 9Lm2 Qx7T v0Rp",
"mcp_endpoint": "https://8f2a1c9d.wprun.site/wp-json/mcp/v1",
"expires_at": "2026-07-01T20:14:00Z"
}How it works
You talk. Your agent builds. The site is real.
Connect once
Paste one config block into Claude, Cursor, or any MCP client. That is the whole setup — no terminal, no hosting account, nothing installed on your machine.
Say what you want
In plain English: "Spin up a WordPress site with Elementor and build a landing page for my bakery." Your agent creates the instance and does the work.
Open a real site
You get a live *.wprun.site URL with a real wp-admin. Click around, share it, keep what works — the site deletes itself when the timer runs out.
Setup
One paste. Your agent takes it from there.
{
"mcpServers": {
"wprun": {
"url": "https://mcp.wp.run",
"headers": { "Authorization": "Bearer $WPRUN_KEY" }
}
}
}This is the whole integration. Your agent creates instances, works on them, and destroys them — you never touch a server.
- RUNTIME
- real server · PHP-FPM + MySQL
- NETWORK
- outbound HTTP, cron, mail
- ACCESS
- app password + WP-CLI
- MCP
- mounted at boot
- LIFETIME
- auto-destroy · 2h default
- STATUS
- ready
Tools
Everything WordPress can do, as tools your agent already understands.
create_instance A fresh WordPress in seconds. Pick WP and PHP versions, set the timer.
install_plugin Anything from the WordPress.org directory — Elementor, WooCommerce, Yoast.
activate_theme Install and switch themes, see the result on the live site.
edit_content Create and edit pages, posts, and menus like a person in wp-admin would.
upload_media Images and files straight into the media library.
manage_settings Permalinks, site title, users, options — the whole Settings screen.
run_wp_cli The full WP-CLI for everything the other tools don’t cover.
destroy_instance Clean up early — or do nothing and let the TTL handle it.
Who this is for
You already have an agent. You need a place to point it.
Plugin & Ability developers
You're building an MCP plugin or a WordPress Ability and need a clean WordPress to point Claude, Cursor, or Codex at — without wrecking the install on your laptop.
Platform & agent builders
You're building a product where an agent builds someone's WordPress site. You need disposable instances at volume, created and destroyed by code, not a human clicking a button.
You build with Elementor, not a terminal
You already use Claude or another AI assistant. Paste one config, describe the site you want, and watch it get built on a real WordPress — no code, no hosting, nothing to break.
Why this exists
A real server, not a trick.
Real server, not a simulation
Real outbound HTTP, real cron, real email, a public URL your agent's API calls can actually reach. No WASM runtime standing in for a server.
Pre-wired for agents
Every instance boots with an MCP adapter, an Application Password, and WP-CLI already configured. Point your agent at it and go.
Ephemeral by design
Instances self-destruct on a timer. Not a limitation — the point. Every run starts from a clean box and leaves nothing behind.
FAQ
The obvious questions.
What is MCP, and which agents support it?
The Model Context Protocol — the standard way AI assistants connect to real tools. Claude Desktop, Claude Code, Cursor, and Codex speak it already, and any custom agent can via an MCP SDK. No MCP? The plain REST API does everything too.
I don't write code. Can I use this?
Yes. If your AI chat supports MCP, setup is pasting one block of text into its settings — about as hard as installing an Elementor addon. After that you just talk. Your assistant handles the API for you.
Is it a real WordPress install?
Real server — PHP-FPM and MySQL, real plugins from the directory, real wp-admin you can open in your browser and click around in. Not an emulator, not a screenshot preview.
What happens when the timer runs out?
The instance and everything on it is deleted. That is the point — every run starts clean and leaves nothing behind. Ask your agent to export anything you want to keep before the TTL hits.
Can this touch my existing site?
No. wp.run only hands your agent disposable sandboxes on *.wprun.site. Your production site is never part of the picture.
What does it cost?
Early access is free, with fair-use limits. We'll share pricing with the list before anything changes — no credit card to start, no surprise charges.
Your agent is ready. Give it a server.
Early access is opening in waves. Leave your email and we'll send your API key, the MCP config, and a two-minute quickstart when your spot opens.
Free during early access · No credit card