Real WordPress you own, driven two ways: paste one MCP URL into any chat client, or run the agent-ready CLI in your terminal. Locked down by default.
Same WordPress, different reach. MCP is the universal doorway: paste a URL into any chat or coding client, nothing installed. The CLI is the deep doorway: a token-auth binary that owns the whole environment around the site.
Best for chat & web clients
Paste one authenticated URL into ChatGPT, Claude on web or desktop, Cursor, anything that speaks MCP. No install, no application password. The agent gets 40+ structured WordPress tools and works inside the conversation.
You want to drive WordPress from a conversation, hand a scoped token to a client or teammate, or work in a chat or web client with zero setup.
Best for coding agents & CI
A token-auth binary your terminal agent runs non-interactively: Claude Code, Codex, Antigravity, the Gemini CLI, or a CI job. It owns provisioning, local-to-cloud, deploy, sync and one-command rollback.
$ instawp login
✓ Logged in successfully
# a coding agent owns the whole environment
$ instawp create --name acme --php 8.3
✓ acme (ID 48213) · https://acme.instawp.site
$ instawp wp acme plugin activate woocommerce --api
$ instawp local push acme --with-db
✓ Push complete! · URLs rewritten
An agent needs to own the environment: spin sites up and down, push a local build to the cloud, run it in CI, snapshot and roll back around risky changes.
Six jobs every WordPress team runs into, and the actual moves an agent on InstaWP makes to clear each one, from chat over MCP or the terminal over the CLI.
Each site exposes its own authenticated MCP endpoint. Drop it into any client and an agent gets 40+ structured WordPress tools. No Node bridge, no application password, no config files.
One scoped token. Paste it into any MCP client. Connected in one step.
Where most AI-for-WordPress access is an application password with raw run of a live site, InstaWP is locked down by default.
Two scopes, both live. The per-site endpoint is built for deep work inside a single install. The account-level MCP connects over OAuth to manage the account itself and run one job across your whole fleet.
A unique, token-authenticated endpoint scoped to one site. One click to enable, one paste to connect. Built to build, configure and debug a single install end to end.
Connect your whole InstaWP account over OAuth and an agent can manage the account itself and run one job across your whole fleet, from a single prompt. A distinct surface from the per-site endpoint.
Want zero risk? Point the agent at a $2 disposable sandbox first. Let it build and break on a throwaway site, then promote the same site to production with one plan change. Other tools tell you to use staging. We are the staging.
MCP talks to a site. The instawp CLI owns everything around it. A coding agent in a terminal already shells out to its tools, so it drives the whole loop the same way: run a command, read the --json it returns, decide, run the next. Build, troubleshoot, ship, roll back.
# one token in the env: no SSH keys, no wp-admin password, no browser
$ export INSTAWP_TOKEN=iwp_••••
you › build the membership checkout on a local site, fix what breaks, then ship it
# 1 · BUILD ·····
# a real WordPress on your machine: WASM PHP + SQLite, no Docker, free
$ instawp local create --name acme --php 8.3 --json
{ "instance": "acme", "php": "8.3", "status": "running" }
agent ▸ acme is up. scaffolding the plugin, a tier option, and a checkout page.
# 2 · TROUBLESHOOT ·····
# run the checkout test over HTTPS with --api. no SSH to set up.
$ instawp wp acme --api -- eval-file tests/checkout.php
✕ exit 1
agent ▸ exit 1, a real failure not a hang. pulling the PHP log as JSON.
$ instawp logs acme --php --json -n 20
{ "level": "error", "message": "Undefined array key \"tier\"", "file": "checkout.php:42" }
agent ▸ reads checkout.php:42, the "tier" key is missing. patches the guard, seeds a default.
$ instawp wp acme --api -- eval-file tests/checkout.php
Success: 1 assertion passed.
# 3 · SHIP ·····
# checkpoint a restorable version (files + db), then push local up to the cloud
$ instawp versions create acme --name "pre-launch" --json
{ "id": 9135, "contains": "files+db" }
$ instawp local push acme --with-db
✓ Cloud DB backed up · URLs rewritten · Push complete!
→ https://acme.instawp.site
agent ▸ shipped in one session: build, fix, live. the checkpoint rolls it all back in one command.
Add --json to any command and the agent gets machine-readable output, the observe half of an observe-then-act loop. Nothing to scrape.
$ instawp logs acme --php --json
# the agent parses it, decides, acts
One INSTAWP_TOKEN (or instawp login) authenticates everything. No SSH keys, no wp-admin password, no browser, so it runs the same in CI.
$ export INSTAWP_TOKEN=iwp_••••
# works in CI, behind any firewall
Commands return faithful exit codes, so a broken step actually fails. Destructive ops need --force in --json mode, so a script errors instead of hanging on a prompt.
$ instawp versions restore acme 9135 --force --json
# non-interactive, no y/N to hang on
The MCP and the CLI are live today. Here is where AI goes next across the platform, each item badged so you always know what is shipping and when.
Describe the site you want and watch a real WordPress take shape on a sandbox you can promote to production. Not a throwaway draft: a real site you own, keep building on, with the agent that built it still on hand.
Chat with your site from inside wp-admin. Ask what is slow, what changed, and what to fix, without leaving WordPress.
Let AI keep two sites in step, syncing just what changed between them instead of the whole install.
Use MCP to drive WordPress from a chat or any MCP client with no install, great for conversational edits and handing a scoped token to a client or teammate. Use the CLI to provision, deploy, sync and roll back from a terminal or CI. Many teams use both.
Any MCP client with a bearer token. We publish setup guides for 13, including Claude (Desktop, Code and web), ChatGPT (web and desktop), Cursor, Windsurf, Cline, Zed, GitHub Copilot, the Gemini CLI and the Codex CLI.
Yes. The agent gets a scoped, revocable token tied to a WordPress role and acts through structured tools, not raw code. Safe Mode blocks destructive writes and deletes, and raw PHP, SQL and file access stay off until you turn them on.
Only if you enable it. execute_php, db_query and site_files ship off by default and admin-gated, and execute_php also needs the admin scope. Agents can see the tools exist but get a "how to enable" message until you opt in.
Not necessarily. The CLI uses SSH by default and generates and caches the key for you. Add --api to run over HTTPS with no SSH setup, the way it works in CI and behind firewalls.
Same protocol, none of the setup. No Node bridge, no application password, no config files. One scoped token, 40+ tools and a $2 sandbox to test against, hosted and managed. On WordPress 6.9+ every tool is also registered through the WordPress Abilities API, so the official adapter sees them too.
Live: site-level and account-level MCP, the instawp CLI and AI-enabled migrations. Coming: the AI Builder (July 2026), AI Assistance in wp-admin and AI Way Sync. Each one is badged so you always know which is which.
The MCP is part of the site, no extra charge. You pay the usual per-site price, from a $2 sandbox up, billed by the day. The CLI is free to install. See pricing.
Every InstaWP site plugs into the rest of the platform. Keep exploring:
Clone, test, push live
SSH, CLI, Git deploy, MCP
Provision sites by API
Save sites & reusable presets
Managed WordPress, per site
Buy, connect, or resell
Bring sites in, free
Connect your stack
Every site, one dashboard
Resell hosting, your brand
Panel for your clients
Sell ready-made sites
Connect by MCP from any chat client, or drive the CLI from your terminal. Either way, let an agent build, operate and troubleshoot a real WordPress, without leaving WordPress.