Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Publish and manage WordPress pages, posts, media
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
WORDPRESS_BASE_URL, WORDPRESS_BASIC_AUTH, WORDPRESS_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE, WORDPRESS_USER_AGENTValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
WORDPRESS_BASE_URL envPRINTING_PRESS_CLIENT_PROFILE envWORDPRESS_USER_AGENT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: WORDPRESS_BASIC_AUTH, WORDPRESS_MCP_HTTP_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.9) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Unofficial. Community-built Claude Code Skill and MCP server for the WordPress
API. Not affiliated with, endorsed by, or sponsored by WordPress Foundation.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Publish and manage WordPress pages, posts, media Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build checks a token, but it
predates the fix release's request size and time limits. The MCP tools can
also make changes with your credentials. Use the default stdio transport. If
you set up a tunnel for a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the WordPress skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register wordpress-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add wordpress-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add wordpress-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs wordpress-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionwordpress-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setWORDPRESS_CLI_PATHto an existing binary). Details: #331.
Download WordPress MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every WordPress release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills
/plugin install wordpress@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the WordPress Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/wordpress/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/wordpress/install.ps1 | iex. Then authenticate per the README and runwordpress-cli --helpto explore.
The same prompt works in any agent that can run shell.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/wordpress/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/wordpress/install.sh)
The installer drops both wordpress-cli (the CLI) and wordpress-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
wordpress-cli --version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/wordpress/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/wordpress/install.ps1 | iex
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update wordpress@msp-skills.
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/wordpress --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/wordpress --force
Hermes speaks MCP natively, so it can also use the wordpress-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the wordpress skill from https://github.com/servosity/msp-skills/tree/main/skills/wordpress. The skill defines how its required CLI (
wordpress-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Set the credentials the CLI needs (from your WordPress portal):
WORDPRESS_BASIC_AUTH=<value> wordpress-cli doctor
doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
| Question your MSP keeps asking | Command |
|---|---|
| Publish a landing page from HTML without opening wp-admin? | wordpress-cli pages create --title "Spring Promo" --content " Spring Promo " --status publish |
| Which pages are still sitting in draft? | wordpress-cli pages list --status draft |
| Update a live page's content in place? | wordpress-cli pages update 42 --content " Updated copy " |
| Upload a hero image and get its media id? | wordpress-cli media upload ./hero.png --alt-text "Spring promo hero" |
| Mirror the whole site locally for offline search and backup? | wordpress-cli workflow archive |
Find every page or post that mentions an old phrase (after a workflow archive)? | wordpress-cli search "summer sale" |
| Publish a blog post with categories and tags? | wordpress-cli posts create --title "Patch Tuesday recap" --content " This month... " --status publish |
| Which authors can I assign content to? | wordpress-cli users list |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most WordPress integrations and MCP servers proxy each question into a live API call. That's fine for editing one record. It gets slow and noisy when you ask "find every page and post across the whole site that still mentions last year's pricing or a dead promo link."
This skill syncs WordPress into a local SQLite mirror with full-text search. That cross-content question becomes one instant offline query, and the AI sees the matching rows, not a dump of every page's HTML. Compound commands like workflow archive and workflow status mirror and inventory every page, post, media item, category, tag, and user in one pass - work a stateless API wrapper can't do.
Routine site edits - swap a promo banner, fix a phone number, push a new landing page - mean logging into wp-admin and clicking through the block editor screen by screen. The Classic Editor plugin still reports over 10 million active installs on the WordPress.org plugin directory: a standing vote against that editor for everyday content work. Across a stack of client sites that browser-clicking is unbillable busywork, and the official WP-CLI - the scriptable alternative - needs SSH access to the server's shell that many managed or hosted sites never give you.
This skill closes that gap from the terminal or your AI agent, over the REST API your site already exposes:
wordpress-cli pages create / wordpress-cli pages update / wordpress-cli posts create, no wp-admin and no SSH.wordpress-cli pages list --status draft surfaces every page still waiting to ship.wordpress-cli workflow archive mirrors the site, then wordpress-cli search "old pricing" finds every page or post that still mentions it.Only the beginning is shown; read the rest in the repo