Summary
Two tools, the whole REST API.
Most WordPress servers enumerate a fixed set of operations and stop where their author stopped. This one discovers what a site actually exposes and calls it, so custom post types and plugin routes are in scope; the cost is that you work in endpoints rather than named actions.
What it is
A Node MCP server that talks to WordPress sites through the REST API using two general tools: discover what a site exposes, then call it.
What you get
- Every REST endpoint on a site mapped, with its methods and namespaces
- Any of those endpoints called with GET, POST, PUT, DELETE or PATCH and a parameters or body object
- Several sites connected at once, each addressed by an alias from a JSON configuration file
- Endpoint discovery done dynamically, so plugin-provided routes are reachable without waiting for support
- Application-password authentication per site
Requirements
Npm install server-wp-mcp, or install through Smithery. Each site needs an application password created under Users then Profile — a WordPress new enough to offer them, served over HTTPS — and an alias in the JSON configuration file.
Setup effort
One command plus a key — npm install server-wp-mcp, then supply credentials