Skip to main content
Agency Program 50% cashback. Exclusive discounts. Priority support. Built for growing agencies. 50% cashback. Exclusive discounts. Priority support. Built for growing agencies. Speak to the team Join free
Platform/Dev Tools/CLI
@instawp/cli · beta

Drive WordPress from your terminal.

The scriptable side of InstaWP. One token, local (free, no Docker), your cloud sites, and the sync between them, all non-interactive and drivable by any AI agent or CI. Provision, deploy, run, and roll back, from one command line.

Install the CLI → See every command
JSON on every command Remote WP-CLI, no SSH setup One INSTAWP_TOKEN

From a local build to a live fix, in one loop.

Your agent runs the whole cycle from one prompt and one token. It builds on a free local WordPress, pushes to a cloud site, reads the live logs when something breaks, then patches and pushes again.

Every later push lands on the same linked site, so the loop is patch, push, check the log.

claude code · instawp
# free, on this machine: WASM PHP + SQLite, no Docker
$ instawp local create --name acme
✓ Instance "acme" created
# Starting WordPress latest with PHP 8.3...
→ http://127.0.0.1:9400
you › build a membership checkout on acme
✓ agent scaffolds the plugin and the checkout page
# first push creates the cloud site and links it to acme
$ instawp local push acme --with-db --force
✓ Cloud site created
✓ Site provisioned
✓ Cloud DB backed up: ~/db-backup-….sql.gz
✓ Database imported · URLs rewritten
✓ Push complete!
$ instawp logs acme --php -n 20
PHP Warning: Undefined array key "tier" in checkout.php on line 42
$ instawp wp acme --api -- option get acme_tiers
Error: Could not get 'acme_tiers' option. Does it exist?
you › fix it locally and push again
$ instawp local push acme
✓ guard added · same site updated · log is quiet

Let the agent act freely. Rewind in one command.

An in-site MCP stays safe by blocking risky writes. The CLI lets the agent act, then puts the whole site back if a change goes wrong.

  • Checkpoint firstFiles and database, saved and named before the agent changes anything.
  • A backup before every importdb push saves the remote database first and fixes a mismatched table prefix, so admin login survives.
  • Restore in placeOne command puts files and database back. In --json it errors instead of waiting on a prompt.

Pull a live site down. Push it back up.

Clone a cloud site into a free local sandbox, work on it offline, then ship it back with its database. WordPress has no official SQLite to MySQL exporter, so the CLI converts both ways.

acme.instawp.siteLive
InstaWP cloud
  • MySQL database
  • Public URL
Backed up before every push
Pull downCloud → Local
$ instawp local clone acme
  • Database exported
  • MySQL → SQLite
  • URLs and prefix fixed
  • wp-content synced
Push backLocal → Cloud
$ instawp local push acme --with-db
  • Cloud DB backed up
  • SQLite → MySQL
  • User roles remapped
  • URLs rewritten, cache flushed
127.0.0.1:9400Running
Your machine
  • WASM PHP + SQLite
  • Free, no Docker
Linked to acme for every push

The whole control surface.

Everything an agent or a CI job needs to provision, deploy, run, observe and recover, addressed by site name and authenticated with one token.

Provision

A ready site per CI job

Waits for HTTP, then returns logins as JSON.

$ instawp create --name pr-42 --temporary --json
Run anything

WP-CLI and shell, remotely

SQL and WP-CLI over HTTPS, real exit codes.

$ instawp exec acme --shell 'wp cron event list | grep due'
Observe

Logs an agent can read

PHP and WordPress logs as structured JSON.

$ instawp logs acme --php --wp --json
Deploy files

Ship code, preview first

Dry-run a wp-content mirror, or install a plugin.

$ instawp sync push acme --delete --dry-run $ instawp plugin install acme ./plugin --activate
Local ⇄ cloud

Clone down, push back

A no-Docker WASM copy, pushed back with its DB.

$ instawp local clone acme $ instawp local push acme --with-db
Recover

Checkpoint before risky work

A named version, plus a gzipped DB dump.

$ instawp versions create acme --name pre-deploy $ instawp db pull acme --output backup.sql.gz
Roll back

Any version, restored in place

Files and database, back in one command.

$ instawp versions list acme $ instawp versions restore acme <id> --force
Scope

One token, one team

Point the token at a single team's sites for agency and fleet automation.

$ instawp teams switch acme-clients

The CLI sets the stage. The MCP does the work.

The MCP acts inside one install through schema-validated tools. The CLI acts on the environment around it: provision, deploy, recover, scope. The loop that ties the two together is the whole point.

CLIProvision a targetinstawp create --temporary
›
CLIHand off its MCP URLacme.instawp.site/insta-mcp?t=…
›
MCPAgent builds inside itcreate · patch · plugins
›
CLIShip it, or roll it backlocal push · versions restore

Account MCP, on steroids. The CLI already spans local (free, on your machine), remote (your cloud sites), and sync between them. Fully scriptable, drivable by any agent or CI, today. See the MCP →

One install, one token.

Three commands from zero to a CLI your agent or your CI can drive.

Quick startNode 18+macOS · Linux · Windows
  1. 1Install
    $ npm install -g @instawp/cli

    Checks for a new version once a day. instawp upgrade installs it.

  2. 2Authenticate
    $ instawp login

    Opens your browser. In CI, pass --token or set INSTAWP_TOKEN.

  3. 3Check the session
    $ instawp whoami

    Shows the account and the team the token is scoped to.

  • Any site by name, ID or domainThe CLI resolves it for you.
  • WP-CLI and SQL over HTTPSAdd --api: no SSH setup, works behind firewalls and in CI.
  • Local sites, no DockerWordPress Playground on WASM, free on your machine.
  • Beta, built in the openReport issues on GitHub.
Dev ToolsSSH, Local Mount, InstaCode, Git
→
AI & MCPThe in-site MCP the CLI hands off to
→
API & WebhooksProvision sites over REST
→

Put WordPress on the command line.

Install the CLI, point it at a free local sandbox or a live cloud site, and let your agent or your CI drive the whole loop.

Install the CLI → Read the CLI docs
✓ One token · local + remote + sync · drivable by any agent or CI