WordPress has released the Plugin Directory MCP Server, and it matters most if you work inside AI-powered IDEs like Cursor, Claude, or VS Code. Getting from a local dev environment to the official WordPress.org repository has always meant web forms and manual readme checks. This implementation of the Model Context Protocol (MCP) hands your assistant direct context on the directory’s rules and on the state of your own submission.
What the plugin directory MCP server is
The Plugin Directory MCP Server is a standardized interface between the model and the repository. Your AI can read the current state of your plugin as WordPress.org sees it, validate a readme, check submission status, and submit a plugin for review. It also pulls the latest plugin guidelines, so the assistant can flag a compliance problem before you ship it.
I have written before about how to simplify AI WordPress plugin development. This one is different because it sits at the infrastructure level. The guidelines never get pasted into a chat window, the assistant reads them from the source.
The tools it exposes
- Readme validation: check that your
readme.txtmeets the requirements before you upload anything. - Submission status: ask the server where your plugin sits in the review queue instead of refreshing the meta site.
- Guideline context: the AI can cross-reference your code against the official WordPress Plugin Guidelines while you write it.
Setup means adding the server URL to your MCP-compatible tool. In Cursor you drop the endpoint into your project settings, and the model can start calling these tools.
{
"mcpServers": {
"wp-plugin-directory": {
"command": "npx",
"args": ["-y", "@wordpress/mcp-server-plugin-directory"]
}
}
}The part the automation does not cover
None of this moves the responsibility. WordPress is blunt about it: You are responsible for the code. The plugin review team will not care that an AI wrote the race condition or the security hole, because the guidelines apply whoever the author was. Everything your assistant generates still needs reading, refactoring and debugging. The server takes friction out of the process, and that is all it takes out.
I have watched “AI-first” plugins get rejected because the developer never noticed the model had invented a legacy hook that was deprecated back in 5.8. Use the Model Context Protocol to check your assumptions against something real.
If this Plugin Directory MCP Server work is eating your dev hours, hand it to me. I have been wrestling with WordPress since the 4.x days.
Next steps
This points the same way as “Agentic Commerce” and the other automated workflows turning up in the ecosystem. The official announcement is on Make WordPress. If you are modernizing your plugin development stack, wiring this server in is worth an afternoon.
