WordPress

WordPress MCP server and CLI with offline posts

Copy your WordPress posts and pages to your computer, so your AI agent reads them and writes drafts.

Write and check your blog without opening wp-admin. wordpress gives the AI agent you already use, such as Claude Code, Codex or Claude Desktop, a copy of your WordPress posts and pages on your computer, so it answers from that copy, even offline. It writes drafts on your site, and publishes them when you allow it.

Ask what you published last month, which drafts wait, or what a page says today. Hand the agent your notes, and it makes a draft with a title, an excerpt and tags. You need a self-hosted WordPress site, 5.7 or later over https, and a user on it.

On this page:

  1. What you get
  2. Things a newcomer would not guess
  3. How it looks
  4. Why wordpress
  5. What it can do
  6. How it works
  7. Start in a few minutes
  8. Limits
  9. Find a guide for your task

What you get

  • The answer, not the search. Ask about a post in your own words. The agent finds it by its title and text, with its status, tags and author, read from your computer.
  • Every draft and scheduled post in one list. Filter by status, tag, author or the day a post went out.
  • Drafts from your notes. A Markdown file becomes a draft on your site, with a title, an excerpt and tags.
  • Publish now or later. Publish a draft at once, schedule it, or take a post back to a draft.
  • The trash too. Posts in the trash stay in the copy with their status, so nothing you threw away is lost from view.
  • Your posts beside your chats. They sit in the same local store as the messages, mail and meetings that the other WireCat tools keep on your computer.

Things a newcomer would not guess

  • An application password is your key. WordPress lets a program in with a password you make in your profile, apart from the one you log in with. It can do what your user can, no more. Install shows where to click.
  • blog is a name you choose. It names one site and one user, and it is the first word of every command. No command picks a site for you.
  • Reads use a copy, writes go to the site. sync copies your posts and pages. posts list, posts search and posts show answer from that copy. posts create, update, publish, unpublish and delete change your site.
  • Your role decides what you see. An Administrator gets the whole site. An Editor gets every post and page, but not the users list. An Author or Contributor gets only part of it: see limits.
  • Over MCP, "ask" goes ahead. MCP is the way apps such as Claude Desktop call a tool, and nobody sits at a terminal there to answer a question. So an agent over MCP can publish. Set posts.publish to deny if you want to publish yourself: permissions.

How it looks

You:    What did I publish in October?
Agent:  (runs wordpress blog posts list status:published "published:[2026-10-01 TO 2026-10-31]")
        · 38 "Release notes for version 2", published on 3 October
        · 40 "How we test with a fake WordPress", published on 17 October
You:    Schedule draft 63 for Monday 9:00.
Agent:  (runs wordpress blog posts publish 63 --at-time 2026-11-23T09:00:00Z)
        Draft 63 is scheduled for Monday, 23 November, 09:00 UTC.

Invented posts, illustrative output.

Why wordpress

  • A copy of your site on your computer. Lists and search answer from it with no request to your site, also offline.
  • Safe to hand to an agent. Creating, changing, publishing and deleting each have their own permission, and each asks first at a terminal. One line keeps publishing yours.
  • Safe edits. A write stops if the post changed on the site since the last sync. A post with galleries or embeds keeps its body unless you say to replace it.
  • The password stays in your system keyring. It never shows in output, errors or logs.
  • Ready for any agent. A skill for agents with a terminal, an MCP server for Claude Desktop and Cursor, and a secure link for ChatGPT and Claude in the browser.
  • Free and open source. Apache 2.0.

What it can do

  • Posts and pages: list them by status, type, tag, author or date, search their words, show one with its text as Markdown. Use it
  • Tags, categories and authors: list them with the ids the other commands take. Use it
  • Drafts: write a new draft from a Markdown file, change its title, excerpt, tags or text. Use it
  • Publishing: publish now, schedule, take back to a draft, move to the trash. Use it
  • Any WordPress API operation from a terminal, with the same permission checks. Use it

How it works

  • A copy on your computer. sync puts your posts and pages, with every status, and their tags, categories and authors into the WireCat local store, the one file on your computer that every WireCat tool shares. Text is kept as Markdown. Later syncs read only what changed.
  • Sign-in with an application password. It is kept with its site in the system keyring, or in a private file on a computer without one.
  • Made for scripts and agents. --json gives a JSON answer, and an error comes with a code to branch on. MCP
  • What is stored and what goes over the network. Security

Start in a few minutes

Paste this into your agent:

Request
Install wordpress with npm install -g @wirecat/wordpress-cli. Help me make a WordPress application password and run wordpress blog session start --site blog.example.com --login anna to connect my site, then sync and show my drafts.

Or in a terminal:

npm install -g @wirecat/wordpress-cli
wordpress skill install          # teaches Claude Code, Codex and Gemini CLI to use wordpress
wordpress blog session start --site blog.example.com --login anna   # paste the application password
wordpress blog sync              # copy your posts, pages, tags and authors
wordpress blog posts list status:draft

You need Node.js 22.16 or a later 22.x, or Node.js 24 or later. Install shows how to make the password.

Limits

  • Only self-hosted WordPress with application passwords. WordPress.com sites are not supported.
  • You paste the application password. Sign-in through the browser is on the roadmap.
  • An Author or Contributor gets only part of the site. WordPress refuses the pages list to both, so the posts sync stays partial and changes on the site do not reach the copy. A Contributor also sees only their own posts. Only an Administrator gets the users list. Sync reports each of these as a gap.
  • No view counts. WordPress itself keeps none, and Jetpack stats are not supported. posts stats shows only what the copy has.
  • Plugin fields, such as those of SEO or custom field plugins, have no flags. The api group sends them in a raw --body.
  • The writes work on posts. Comments and menus are reached through the api group. The api group sends JSON only, so it cannot upload a file to the media library.

Find a guide for your task

TaskGuide
Install and connect a siteInstall
Read, write and publish postsUse it
Connect an app that uses MCPMCP
Decide what an agent may changePermissions
An exact command or optionCommands
Change a settingSettings
Something does not workWhen something goes wrong
What is stored and sentSecurity
What comes nextRoadmap