list_postsLABSCO SUMMARY
The site-side plugin is what buys the reach — and it is also what you are installing on a live site.
WordPress's REST API covers less than people expect, particularly around SEO fields and redirects, which live in other plugins. A companion plugin closes that gap, at the cost of putting code on the server you are trying to manage. Multi-site config is the practical draw for anyone running client sites — one connection, many installations — and the same reason to be careful: a mistake reaches all of them. Scope the WordPress user, not just the connection.
What it is
A proxy server that sits between the agent and a WordPress installation, talking to a companion plugin on the site itself rather than only to the REST API.
What you get
- Posts, pages and media management
- SEO fields, comments and redirects
- Multi-site configuration, so one connection reaches several installations
Requirements
Python for the proxy, plus a must-use plugin installed on each WordPress site. MIT licensed.
Setup effort
Build from source — git clone https://github.com/5unnykum4r/wordpress-mcp
USE CASES
01
Publishing without the admin screen
Posts, pages and media from the conversation.
02
Fixing SEO fields and redirects
The parts the core REST API does not reach.
03
Running several sites
One connection across the installations you configure.
46 tools
Listed in project docs. Your client may show a different list.
read_postcreate_postupdate_postdelete_postbulk_update_statuslist_revisionsrestore_revisionsearch_replacelist_categoriescreate_categoryupdate_categorydelete_categorylist_tagscreate_tagupdate_tagdelete_tagupload_imagelist_mediaupdate_mediadelete_medialist_commentsupdate_commentdelete_commentlist_redirectionscreate_redirectionupdate_redirectiondelete_redirectionlist_block_typeslist_patternsread_patterncreate_patternupdate_patterndelete_patternlist_tablepress_tablesread_tablepress_tablecreate_tablepress_tableupdate_tablepress_tabledelete_tablepress_tablelist_pluginstoggle_pluginlist_usersmanage_optionsclear_cacheget_infolist_sitesBEFORE YOU INSTALL
What to know first
Tools you get
46 tools named in the project's documentation.
Requires
- Python 3.10+
- uv on PATH
- PHP 7.4+
- Composer
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
Build the adapter's PHP dependencies locally
TERMINAL
git clone https://github.com/5unnykum4r/wordpress-mcp
cd wordpress-mcp/wordpress
composer install
zip -r mcp-vendor.zip vendor/Upload the vendor packages to your server
Upload mcp-vendor.zip to your WordPress root (the folder containing wp-config.php), extract it, and check that vendor/autoload.php exists
Upload the must-use plugin
Upload wordpress/load-mcp-adapter.php into wp-content/mu-plugins/ on the server, creating the mu-plugins folder if it does not exist
Create an Application Password
In WordPress Admin open Users > Profile > Application Passwords, add a new one and copy it with its spaces
Add the site to sites.json
TERMINAL
cd ..
cp sites.json.example sites.jsonIn sites.json set url to <YOUR_SERVER_URL>/wp-json/mcp/mcp-adapter-default-server, username to your WordPress admin username and password to the Application Password
MCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"wordpress": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--with",
"fastmcp",
"--with",
"httpx",
"python",
"<YOUR_PATH_TO_WORDPRESS_MCP>/server.py"
]
}
}
}
