wp_discover_endpointsLABSCO 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 credentials — npm install server-wp-mcp, then supply credentials
USE CASES
01
Finding out what a site's API actually offers
Map the endpoints, methods and namespaces before assuming anything is available.
02
Publishing or updating a post
Call the posts endpoint with the method and body you need.
03
Reaching a route a plugin added
Discover the plugin's namespace, then call it like any other endpoint.
04
Working across several sites in one session
Address each by its configured alias instead of running a server per site.
2 tools
Listed in project docs. Your client may show a different list.
wp_call_endpointBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
node on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install server-wp-mcpIn each WordPress site (5.6 or later, served over HTTPS), go to Users → Profile → Application Passwords, add one named e.g. "MCP Server" and copy the password it generates
Create a JSON file such as wp-sites.json with one entry per site, keyed by the alias you will use in requests: {"myblog": {"URL": "https://myblog.com", "USER": "<YOUR_USER>", "PASS": "abcd 1234 efgh 5678"}} — URL must include https://, USER is the WordPress username, PASS the application password
Add the Claude Desktop block to claude_desktop_config.json, with WP_SITES_PATH set to the absolute path of that file
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"wordpress": {
"command": "node",
"args": [
"<YOUR_PROJECT_DIRECTORY>/node_modules/server-wp-mcp/dist/index.js"
],
"env": {
"WP_SITES_PATH": "<YOUR_WP_SITES_PATH>"
}
}
}
}
