NibWP CLI · free & open source

Your WordPress site, from the terminal

One command connects a site: your browser opens, your site asks what to allow, and you approve. No configuration file to edit, no password stored anywhere — and every ability your site exposes becomes something you can script.

See pricing →Source on GitHub
curl -fsSL https://raw.githubusercontent.com/nibwp/nibwp-cli/main/install.sh | sh
NibWP CLI — your WordPress site from the terminal

AI clients aren't the only thing that can drive your site. The same connection NibWP gives Claude, Cursor and ChatGPT is available to you directly — as a command line. Everything your site exposes over MCP becomes a typed, scriptable command: discover abilities by intent, run them with structured input, and pipe the results anywhere with –json.

It shares one brain with your AI clients: the same typed abilities, the same approvals, the same audit log. Script the repeatable parts here; let Claude Code, Cursor or ChatGPT handle the conversational parts. Both start from the same five-minute connection, and the ability reference shows everything either one can call.

Every ability, scriptable

The same 132 typed tools your AI agents call, available as commands — add –json to anything you want to pipe somewhere else. Comments are kept out of the copy; the orange site address follows whatever you type above.

Type your site address once — every command below updates, and Copy grabs the block ready to paste.

Connect a site

Browser sign-in, scoped. Reading can never write.

nibwp auth login https://yoursite.com

# read-only, for anything you want kept safe
nibwp auth login https://yoursite.com --scope read

# everything, including files and code
nibwp auth login https://yoursite.com --scope read,write,manage,files,code

Find and run

Ask the site what it can do, then do it.

nibwp discover "build a landing page"
nibwp describe nibwp/find-tools
nibwp run nibwp/find-tools --input '{"query":"updates"}'

Set up your editor

Writes the connection in for you — no JSON hand-editing.

nibwp agent add cursor
nibwp agent add vscode --project
nibwp agent add claude-code

Every site at once

One command across everything you look after.

nibwp auth list
nibwp --all doctor
nibwp --site staging discover

Edit a theme locally

Your own editor, then send back only what changed.

nibwp pull wp-content/themes/acme ./acme
nibwp push ./acme --dry-run
nibwp push ./acme

Do it once, repeat it

Record what was done, then replay it elsewhere.

nibwp tape pull --since 45m -o build.tape.json
nibwp replay build.tape.json --all --dry-run
nibwp replay build.tape.json --all

Put things back

Save what you are about to change, restore if needed.

nibwp snapshot create --post-type page -o before.json
nibwp snapshot restore before.json

Check a connection

Says what is wrong and how to fix it.

nibwp doctor
nibwp auth status
nibwp init  # writes what this site is into your project

Safe by default

The CLI inherits NibWP's whole control model:

  • Scopes are enforced by the site, not the client — read-only means read-only.
  • Every call goes through the same typed abilities and lands in the same audit log as your AI agents.
  • Credentials are per-site, approved in the browser by a named administrator, revocable in one click.
  • Dry-run flags on push and replay show the diff before anything is written.

What it needs

  • Node.js 20 or newer — the installer checks for you.
  • NibWP active on the site, with AI Abilities switched on.
  • Administrator access — you approve the connection as yourself.
  • Nothing else: free and open source (GPL) — source on GitHub, package on npm; nibwp –help lists everything.
FAQ

Questions, answered

The terminal side of NibWP, explained.

How is this different from WP-CLI?
WP-CLI runs on the server over SSH and can do anything PHP can. NibWP CLI runs on your machine over HTTPS and can only do what the site approved, calling the same typed abilities your agents call. Use WP-CLI for server work like database exports and core updates; use NibWP CLI for scoped, auditable operations from anywhere — including CI, on sites you cannot SSH into.
Is the CLI free?
Yes — free and open source under GPL, on GitHub and npm. It drives whatever abilities your site’s NibWP install exposes: the WordPress content abilities come with the free plugin, while file operations, sandboxed PHP and the premium integrations come with Pro.
How is this different from connecting Claude or Cursor?
Same connection, same typed abilities, same approvals — different hands. AI clients decide what to call at runtime; the CLI is you (or your scripts and CI) calling abilities deterministically. Most teams use both.
Can a read-only connection ever write?
No. Scopes are enforced by the site, not by the CLI — a connection approved for reading is rejected server-side on any write, whatever flags you pass.
Does it work across multiple sites?
Yes — authenticate each site once, then target one with –site or run a command across every connected site with –all. nibwp auth list shows everything you’re connected to.

Your site, one command away.

The CLI is free and open source. The abilities it drives come with NibWP — start free, upgrade when you need write access and the full toolset.

See pricing →Connect your site