Most WordPress connectors hard-code a handful of endpoints and stop where the plugin ecosystem starts. This reads the API at startup instead, so custom post types and plugin routes are there without anyone having written a tool for them.
An MCP server that discovers a WordPress site's REST API at startup and generates one tool per endpoint and method. Tool names follow `<site>_<method>_<endpoint>`: for a site configured as `myblog`, reading posts is `myblog_get_v2_posts` and updating one is `myblog_put_v2_posts_id`. Several sites run from a single configuration.
- Every REST endpoint on the site discovered and exposed, without listing them by hand
- Posts read as a list or one at a time, created, updated and deleted
- The same generated coverage for pages, users, media, comments, plugins and themes
- Multiple WordPress sites managed side by side from one config file
- The tool set narrowed with include and exclude filters, by exact match or by regex
A WordPress Application Password per site — create it under Users → Profile in wp-admin; it is not your login password. List each site in a `wp-sites.json` with its `URL`, `USER` and `PASS`, and point `WP_SITES_PATH` at that file with an absolute path. The README's global-install line names `wp-standalone-mcp`, which npm does not have; the other documented route, `npx github:diazoxide/wp-standalone-mcp start`, fetches straight from the repository. A site with a large REST surface generates a large tool set — use the include and exclude filters to keep it down to what you actually call.