WP-CLI: The Command Line Guide for WordPress Server Management

WP-CLI is the official command line interface for WordPress, and a single line of it can do work that takes twenty clicks in wp-admin. Updating core across forty sites, exporting a database, running a search and replace after a migration: each is one command. This guide to WP-CLI for WordPress server management covers installation, syntax, the commands worth memorising, and the automation patterns most tutorials skip.

What WP-CLI Actually Does on a Server

WP-CLI loads the same WordPress bootstrap that a browser request loads, then hands control to a terminal instead of a theme. Because it runs as a PHP process on the server, it sidesteps the browser entirely: no PHP max execution timeouts on long imports, no admin session, no plugin UI in the way.

That difference matters most when a site is broken. A fatal error from a bad plugin update locks you out of wp-admin, but the command line still works, and wp plugin deactivate the-culprit brings the site back in about two seconds. We use it daily on servers where the dashboard is unreachable.

Installing WP-CLI in About Five Minutes

You need SSH access, PHP 7.4 or newer (PHP 8.1+ is the sensible target in 2026), and a WordPress install on the same machine. Most managed hosts preinstall it, so run wp --info before you do anything else.

1. Download the Phar archive: curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
2. Check it runs: php wp-cli.phar --info
3. Make it executable: chmod +x wp-cli.phar
4. Move it into your path: sudo mv wp-cli.phar /usr/local/bin/wp
5. Confirm the install with wp --info, which prints the PHP binary, version and config paths

The project is maintained on GitHub and the full command reference lives in the official WP-CLI documentation. Bookmark that page rather than hunting for a PDF cheatsheet; the command list changes with each release.

The Syntax Pattern Behind Every Command

Every WP-CLI command follows the same shape: wp <command> <subcommand> <positional args> --flags. Once that pattern clicks, a beginner can guess most commands correctly on the first try.

So wp plugin install woocommerce --activate reads as command, subcommand, argument, flag. Add --help to anything (wp db --help) and you get the built in manual without opening a browser. Two flags are worth learning immediately: --path= to point at a specific install, and --allow-root when you are operating as root on a VPS.

The Commands That Save the Most Time

You do not need all 200 or so subcommands. These are the ones we reach for most often on production servers:

Related reading: Setting Up CI/CD Pipelines for WordPress Theme Deployment.

Related reading: How to Monitor WordPress PHP Error Logs on the Server.

• wp core update && wp core update-db for core upgrades, including the database schema step people forget
• wp plugin update --all --dry-run to preview exactly which versions will change before committing
• wp db export backup-$(date +%F).sql for a timestamped dump in under ten seconds on a mid sized site
• wp search-replace 'staging.site' 'site.com' --dry-run --all-tables, which handles serialised data that a raw SQL find and replace would corrupt
• wp user create nick nick@example.com --role=administrator when you are locked out and need a fresh admin
• wp cron event list to see whether scheduled tasks are backing up, a common cause of missed emails and stalled queues
• wp transient delete --all and wp cache flush for clearing state after a config change

Pair a few of these in a shell script and routine maintenance on a self hosted WordPress stack drops from half an hour to a single command.

Managing Dozens of Sites With Aliases

This is the part most WP-CLI guides under-serve, and it is where the real server management use sits. A wp-cli.yml file in your home directory can define aliases that point at remote servers over SSH:

@production:
  ssh: deploy@203.0.113.10/var/www/site.com

Now wp @production plugin list runs on that box from your laptop. Group several aliases under @all and one command updates every site you host, sequentially, with output per site. Agencies running 50 or more installs get the most from this, and it pairs naturally with the workflows in our post on bulk managing WordPress plugins across client sites.

WP-CLI in Docker and Deployment Pipelines

The official wp-cli Docker image lets you run commands against a containerised site without installing PHP locally: mount the WordPress volume, pass --network so the container can reach MySQL, and the command behaves exactly as it would on a bare server. The same binary slots into CI jobs.

Because every command returns a standard exit code, a deployment step can fail the build when wp core verify-checksums reports modified files. That single check catches injected malware in core files, which complements the server level rules described in our guide to preventing brute force attacks.

Guardrails Before You Run Anything Destructive

The command line does not ask if you are sure. A mistyped wp db reset --yes empties a production database in well under a second, with no undo.

• Export the database first: wp db export costs you ten seconds and saves a bad afternoon
• Use --dry-run on every search-replace and bulk update, then read the report
• Add --skip-plugins --skip-themes when a broken plugin prevents WP-CLI from bootstrapping at all
• Scope bulk actions with --post_type= or --field= instead of deleting broadly
• Keep a separate SSH user per client so an alias can never touch the wrong install

Write your own commands once the built in set runs out: WP_CLI::add_command() in a small plugin registers a custom WP-CLI command, which is how teams script things like nightly report exports or cache warming on high traffic WordPress infrastructure.

Frequently Asked Questions

What Is the WordPress Command Line Interface (WP-CLI)?

WP-CLI is the official command line interface for WordPress, first released in 2011 and maintained by the WordPress project with around 200 built in subcommands. It lets you install core, manage plugins, users, databases and cron from a terminal over SSH, with no browser involved. The WP-CLI project site tracks current releases.

How Do I Use a CLI Command?

Connect over SSH, change into the WordPress root directory (the folder holding wp-config.php), then type wp followed by a command and subcommand, such as wp plugin list. Append --help to any command for its full flag list, and use --path=/var/www/site if you are running it from somewhere else on the server.

How Do I Install WP-CLI?

Download wp-cli.phar with curl, verify it with php wp-cli.phar --info, run chmod +x, then move it to /usr/local/bin/wp, which takes roughly five minutes on a fresh server. Many managed hosts already ship it, so check with wp --info first. Homebrew and Composer installs work too, though the Phar method is the one the documentation recommends.

What Is the WP-CLI Login Command Server?

The wp login command is a community package (not part of core WP-CLI) that generates one time magic login links, typically valid for 15 minutes. Install it with wp package install aaemnnosttv/wp-cli-login-command, then run wp login as admin --launch. It installs a small companion plugin, so treat it as a support tool rather than something to leave on a public production site.

Get WP-CLI Ready Hosting for Your Sites

Every WebVibo plan includes SSH and WP-CLI preinstalled, so you can run these commands minutes after signup instead of configuring a server first. Compare our business WordPress hosting plans or ask our team which setup fits your current site count.