WordPress.org Plugin Directory MCP
- Spec revision targeted:
- Not documented by the project
The MCP 2026-07-28 revision removes the initialize handshake and protocol-level sessions. What it changes for WordPress · Confirmed 2026-07-24
Official WordPress.org server for plugin authors. Validate a readme, check review status, and submit — from your editor.
- readme-validation
- plugin-submission
- review-status
- reference-docs
An official MCP server run by WordPress.org that puts the plugin submission workflow inside AI tooling like Claude, Cursor, or VS Code. It exposes three tools — validate a `readme.txt` for errors and warnings before submission, retrieve a plugin's current review status and any reviewer feedback, and submit a new plugin or update one still under review — plus reference material covering the plugin guidelines, FAQs, and the reserved-slugs list. Setup runs through `npx -y @wporg/mcp`, which walks you through authorizing a WordPress.org account and creating an application password. Announced March 2026 and maintained by Konstantin Obenland; it is itself built on the Abilities API and the MCP Adapter.
Pros
- Official WordPress.org service — no third party in the submission path
- Catches readme errors before they cost you a review cycle
- Review status and reviewer feedback without waiting on email
- One-command setup, free, no infrastructure to run
Cons
- Narrow by design — plugin-directory workflow only, nothing about running a site
- Only useful if you publish plugins on WordPress.org
- Initial toolset; the maintainer has signalled more tools are expected
Status semantics
GA: published, documented, intended for production use. Beta: feature-complete but rough edges. Alpha: usable for evaluation, expect breaking changes. Experimental: research-only, not safe for production.
Capability tags
Capability tags reflect what an agent can do via the MCP server, not what the underlying WordPress install supports. A "post-management" capability means the MCP server exposes posts as MCP tools; whether the agent has permission to use them depends on the authentication model.