wp_discover_endpointsLABSCO SUMMARY
One server that fits whatever your WordPress happens to expose.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Follow the published steps
USE CASES
01
Finding out what a site can actually do
Discover the endpoints first, then decide which generated tools you care about.
02
Reviewing what is published
List the posts on the site, then open the one you mean.
03
Publishing without opening wp-admin
Create the post directly through the generated endpoint tool.
04
Fixing a live post
Read it by ID, then write the correction back.
05
Taking down content that should not be there
Find it in the list and delete it by ID.
06
Working across several sites at once
Discover the endpoints for each configured site — the prefix on every tool name is the site key you gave it.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Requires
- npx on PATH
- Node.js 16+
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
In wp-admin go to Users → Profile, scroll to Application Passwords, add one (for example "MCP Server") and copy it. This needs WordPress 5.6 or later over HTTPS, and it is not your login password.
Create a wp-sites.json file with one entry per site, keyed by the alias that prefixes its tool names: {"myblog": {"URL": "https://myblog.com", "USER": "<YOUR_USER>", "PASS": "<YOUR_PASS>"}}. Put in your site URL, your WordPress username and the Application Password.
MCP Clients
Claude Desktop
Set WP_SITES_PATH to the absolute path of the wp-sites.json you created:
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": [
"-y",
"github:diazoxide/wp-standalone-mcp",
"start"
],
"env": {
"WP_SITES_PATH": "<YOUR_WP_SITES_PATH>"
}
}
}
}
