WordPress

Install the WordPress CLI and MCP server

Install the WordPress CLI with npm, make an application password in wp-admin and sign in.

Get wordpress running on your computer and connected to your WordPress site in about five minutes. WordPress lets a program in through an application password that you make in your own profile, and this page walks you through it.

Once it is done, an agent on this computer reads your posts and pages when you ask, and writes drafts as far as your permissions allow.

On this page:

  1. What you need
  2. Install the tool
  3. Make an application password in WordPress
  4. Sign in
  5. Check it works
  6. Sign out or change the password

What you need

  • A self-hosted WordPress site, version 5.7 or later, reached over https. WordPress makes application passwords only there. WordPress.com sites are not supported.
  • A user on the site. For a full copy, the user should be an Administrator. An Editor gets every post and page, but WordPress lists the users to an Administrator only. An Author or Contributor gets only part of the site: WordPress refuses them the pages list, so the posts sync stays partial. A Contributor also sees only their own posts.
  • For the command line: Node.js 22.16 or a later 22.x, or Node.js 24 or later. Node 23 is not supported.

Install the tool

Install wordpress once on each computer where you or an agent use it.

npm install -g @wirecat/wordpress-cli
wordpress --version
wordpress skill install   # the agent skill, for Claude Code, Codex, Gemini CLI and OpenClaw
wordpress doctor

The command is wordpress, not wp: the official WP-CLI already uses wp, and both can live on one computer.

doctor needs no network and opens no keyring. It shows the version, where settings live, the profiles that exist, and whether other users of the computer can read the settings.

An agent with no terminal, such as Claude Desktop or Cursor, uses wordpress over MCP instead of the skill.

Make an application password in WordPress

WordPress describes these steps in its Application Passwords guide.

  1. Log in to your site's wp-admin.
  2. Open Users → Profile.
  3. Scroll to Application Passwords.
  4. Type a name for the new password, such as WireCat, and click Add Application Password.
  5. Copy the password WordPress shows. It shows it once only.

The password can do what your user can, no more. It works until you revoke it in the same place.

If the section is missing, the site is not on https, or a plugin or the host turned application passwords off. Ask the site's admin.

Sign in

A profile is a name you choose for one site and one user, such as blog. It is the first word of every command that uses an account. No command picks one for you.

wordpress blog session start --site blog.example.com --login anna

--site is your site's address, with or without https://. --login is your WordPress user name. wordpress asks for the application password without showing it, checks it with your site and keeps it, with the site, in the system keyring. A password the site refuses is not kept. The password goes to that site alone, never to another site on the same host.

On a computer with no keyring, add --credential-storage file to keep it in a private file instead. An agent or a script can pipe the password in on stdin. The password is never taken as an argument, so it does not land in your shell history.

Check it works

wordpress blog session status --check   # asks your site whose password it is
wordpress blog sync                     # copies your posts, pages, tags and authors
wordpress blog posts list status:draft

The first sync reads every post and page, so a large site takes a while. Later syncs read only what changed. If something fails, see when something goes wrong.

Sign out or change the password

wordpress blog session end

session end forgets the password on this computer. The password itself still works on your site until you revoke it: Users → Profile → Application Passwords, Revoke. To change it, run session start again with the new one.

Next: use it, or connect an app over MCP.