WordPress just shipped the Plugin Directory MCP Server. The name sounds like one more layer of abstraction, but it is the most practical thing to land for plugin developers in a while. If you have ever read a readme.txt line by line looking for the header you forgot, or refreshed the submission queue more times than you want to admit, this one is aimed at you. It puts the Plugin Directory inside the editor where your AI assistant already lives.
What is the Plugin Directory MCP Server?
The Model Context Protocol (MCP) is an open standard that lets AI models reach external tools and data. It works like a universal adapter, the USB-C port for LLMs. With a dedicated Plugin Directory MCP Server, the WordPress Meta team has given assistants like Claude, Cursor, and VS Code a way to talk to the plugin repository. Your AI can pull the guidelines, check your code against the official standards, and run the submission itself, none of which requires leaving your IDE.
There has been plenty of AI hype in the WordPress space lately, and most of it is a chatbot in a wrapper. This one is plumbing: a real connection between the code on your machine and the repository infrastructure. Anyone who read my earlier notes on simplifying AI WordPress development will see where it fits.
What the server can do right now
- Validate readme checks your
readme.txtfor errors and missing headers before you attempt an upload. - Get plugin status returns where your submission stands, reviewer feedback included, in your terminal or chat window.
- Submit plugin sends the plugin in for review, or updates a submission you already have open.
Getting started with @wporg/mcp
Setup takes almost nothing. You do not have to touch your local environment, you only bring a WordPress.org account and a client that speaks MCP. Authentication goes through Application Passwords, so your main credentials stay out of it. One command starts the connection:
# Initialize the WordPress.org MCP server configuration
npx -y @wporg/mcpOnce it is authorized, the assistant has context it never had before. It stops guessing whether a slug is reserved and asks the Plugin Directory MCP Server instead. That removes most of the hallucination problem, the kind where a tool confidently quotes plugin guidelines from 2021.
One caution before you trust it
Easier submission does not mean less responsibility. Everything that goes through the Plugin Directory MCP Server lands in the same manual review process as before. I have untangled enough legacy code and race conditions to know that an AI will happily produce a technically valid readme.txt sitting on top of insecure logic. Read everything it generates before you hit submit.
If wiring up the Plugin Directory MCP Server is eating your dev hours, I can take it off your plate. I have been working with WordPress since the 4.x days.
Where this is heading
Under the hood the server runs on the new Abilities API, which is the part worth watching. Once that plumbing exists, the same pattern works for forum moderators, theme reviewers, probably Trac contributors before long. The gap between writing code and putting it in front of millions of users keeps getting thinner. Skip these integrations and you are choosing to do the work by hand.
