Rust-native CLI for managing WordPress sites remotely via the REST API. Inspired by WP-CLI, but built from the ground up for AI agents -- because agents shouldn't need PHP installed to manage a WordPress site.

WP-CLI requires a local PHP runtime, a bootstrapped WordPress installation, and SSH access to run. That's fine for humans on a server, but it's a non-starter for AI coding agents like Claude, Cursor, or Codex that operate remotely over HTTPS. wpx solves this by communicating purely via the WordPress REST API as a single static binary with zero runtime dependencies.

Designed agent-first: structured JSON output, schema introspection, and semantic exit codes let AI agents operate WordPress programmatically. Designed human-friendly: auto-detecting table output, colored terminals, and shell completions make it pleasant for interactive use.

• Full WordPress REST API coverage -- 34 command groups spanning posts, pages, media, users, plugins, themes, menus, widgets, blocks, and more
• Structured output -- JSON, Table, CSV, YAML, and NDJSON formats with automatic TTY detection
• Schema introspection -- wpx schema <command> emits JSON Schema for any command's input/output
• Semantic exit codes -- 11 distinct codes (0-10) so agents can programmatically decide retry/abort/fix strategies
• Multi-site fleet management -- run commands across dozens of sites concurrently with wpx fleet exec
• Application Passwords & OAuth 2.1 -- secure authentication without exposing wp-admin credentials
• Field masking -- --fields id,title,status to reduce payload size for agent consumption
• Automatic pagination -- --all-pages streams every result as NDJSON
• Site discovery -- wpx discover <url> probes a site's REST API capabilities
• Dry-run mode -- --dry-run previews destructive operations before executing

Homebrew (macOS/Linux):

brew tap osodevops/wpx
brew install osodevops/tap/wordpress-cli

Cargo (from source):

cargo install --git https://github.com/osodevops/wordpress-cli wpx-cli

Binary download -- grab the latest release for your platform from the Releases page.

wpx auth set --site production --username admin --password "xxxx xxxx xxxx xxxx"

Credentials are stored in ~/.config/wpx/credentials.toml with restricted file permissions.

wpx auth test --site production

# List recent posts (human-readable table in terminal)
wpx post list --site production

# Same command, but pipe to jq (auto-switches to JSON)
wpx post list --site production | jq '.[0].title'

# List plugins as JSON
wpx plugin list --site production --output json

# Create a draft post
wpx post create --site production --title "Hello from wpx" --status draft

# Global search
wpx search "migration guide" --site production

• User-level: ~/.config/wpx/config.toml
• Project-level: ./.wpx.toml (checked in to your repo for team defaults)
• Credentials: ~/.config/wpx/credentials.toml (never commit this)

Example config.toml:

[default]
output = "json"
timeout = 60
retries = 5

[sites.production]
url = "https://example.com"
auth = "application-password"
username = "admin"

[sites.staging]
url = "https://staging.example.com"
auth = "application-password"
username = "editor"

CLI flags  >  env vars  >  project config (.wpx.toml)  >  user config (~/.config/wpx/config.toml)  >  defaults

WordPress 5.6+ supports Application Passwords natively. No plugins required.

1. Log in to wp-admin and navigate to Users > Profile
2. Scroll to Application Passwords
3. Enter a name (e.g., "wpx CLI") and click Add New Application Password
4. Copy the generated password (spaces are fine -- wpx strips them)
5. Store it with wpx:

wpx auth set --site production --username admin --password "XXXX XXXX XXXX XXXX"

For environments that require OAuth (headless WordPress, enterprise SSO):

wpx auth oauth \
  --site production \
  --client-id "your-client-id" \
  --authorize-url "https://example.com/oauth/authorize" \
  --token-url "https://example.com/oauth/token"

This opens a browser for the authorization code flow with PKCE, then stores the resulting token.

wpx supports six output formats. By default (--output auto), it renders tables when stdout is a TTY and JSON when piped.

# Interactive terminal: auto-renders a table
wpx post list --site production

# Piped to another program: auto-switches to JSON
wpx post list --site production | jq '.[] | .title'

# Force a specific format
wpx plugin list --site production --output csv > plugins.csv

Run commands across multiple WordPress sites concurrently:

# Check plugin status across all configured sites
wpx fleet exec "plugin list" --sites "production,staging,dev"

# Update a plugin everywhere (with concurrency limit)
wpx fleet exec "plugin update --slug akismet" --concurrency 3

# Check fleet health
wpx fleet status

Every wpx command returns a semantic exit code that agents can use for programmatic error handling:

Errors are emitted as structured JSON on stderr:

{
  "error": true,
  "message": "Resource not found: post 99",
  "exit_code": 4,
  "resource": "post",
  "id": "99",
  "suggestion": "Use 'wpx post list' to find valid IDs"
}

Agents can discover the input/output shape of any command at runtime:

# Show schema for a specific command
wpx schema post list

# List all available schemas
wpx schema

wpx binary (6 crates)
├── wpx-cli       CLI parsing (clap), command dispatch, shell completions
├── wpx-core      Resource trait, domain types, semantic exit codes
├── wpx-api       HTTP client (reqwest + rustls), retry, pagination
├── wpx-auth      Application Passwords, OAuth 2.1 (PKCE)
├── wpx-config    TOML config, site profiles, credential store
└── wpx-output    JSON, Table, CSV, YAML, NDJSON rendering

All crates share a workspace version (0.1.0) and are published together.

# Clone
git clone https://github.com/osodevops/wordpress-cli.git
cd wordpress-cli

# Build
cargo build --release

# Run tests
cargo test --workspace

# Lint
cargo clippy --workspace -- -D warnings

# The binary is at target/release/wpx
./target/release/wpx --version

# Bash
wpx completions bash > ~/.local/share/bash-completion/completions/wpx

# Zsh
wpx completions zsh > ~/.zfunc/_wpx

# Fish
wpx completions fish > ~/.config/fish/completions/wpx.fish

Licensed under either of:

• MIT License
• Apache License, Version 2.0

at your option.