
WordPress MCP server
Publish and manage WordPress pages, posts, media
B75/100grade B
Adoption
Growing
41 stars
Reviews
Write oneNobody has reviewed WordPress MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
WordPress MCP tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
The registry entry has no remote endpoint or installable package.
WordPress MCP: common questions
- Is WordPress MCP server safe?
- Mostly: it is graded B (75/100). Read the WordPress MCP safety report
- Does WordPress MCP need an API key?
- Yes. The registry entry asks for
WORDPRESS_BASIC_AUTH. - Is WordPress MCP maintained?
- The last commit was in the last day (2026-09-18). The latest release is v0.1.4.