WordPress MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 90 installs a week from npm. Last commit 23 Jul 2026.
MCP server for WordPress. Manage posts, users, comments, terms, metadata, and settings.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
execSync(`npm i -S ${dependencies.join(" ")}`, { stdio: "inherit" });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add wp-mcp -e 'LOCAL_USERNAME=<LOCAL_USERNAME>' -e 'WP_DB_HOST=<WP_DB_HOST>' -e 'WP_DB_NAME=<WP_DB_NAME>' -e 'WP_DB_USER=<WP_DB_USER>' -e 'WP_DB_PASSWORD=<WP_DB_PASSWORD>' -- npx -y @rnaga/wp-mcp
{
"mcpServers": {
"wp-mcp": {
"command": "npx",
"args": [
"-y",
"@rnaga/wp-mcp"
],
"env": {
"LOCAL_USERNAME": "<LOCAL_USERNAME>",
"WP_DB_HOST": "<WP_DB_HOST>",
"WP_DB_NAME": "<WP_DB_NAME>",
"WP_DB_PASSWORD": "<WP_DB_PASSWORD>",
"WP_DB_USER": "<WP_DB_USER>"
}
}
}
}
[mcp_servers.wp-mcp]
command = "npx"
args = ["-y", "@rnaga/wp-mcp"]
env = { LOCAL_USERNAME = "<LOCAL_USERNAME>", WP_DB_HOST = "<WP_DB_HOST>", WP_DB_NAME = "<WP_DB_NAME>", WP_DB_USER = "<WP_DB_USER>", WP_DB_PASSWORD = "<WP_DB_PASSWORD>" }
{
"mcpServers": {
"wp-mcp": {
"command": "npx",
"args": [
"-y",
"@rnaga/wp-mcp"
],
"env": {
"LOCAL_USERNAME": "<LOCAL_USERNAME>",
"WP_DB_HOST": "<WP_DB_HOST>",
"WP_DB_NAME": "<WP_DB_NAME>",
"WP_DB_PASSWORD": "<WP_DB_PASSWORD>",
"WP_DB_USER": "<WP_DB_USER>"
}
}
}
}
{
"servers": {
"wp-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@rnaga/wp-mcp"
],
"env": {
"LOCAL_USERNAME": "<LOCAL_USERNAME>",
"WP_DB_HOST": "<WP_DB_HOST>",
"WP_DB_NAME": "<WP_DB_NAME>",
"WP_DB_PASSWORD": "<WP_DB_PASSWORD>",
"WP_DB_USER": "<WP_DB_USER>"
}
}
}
}
Put your own values in place of
<LOCAL_USERNAME> (WordPress username to assume for capability checks), <WP_DB_HOST> (WordPress database host), <WP_DB_NAME> (WordPress database name), <WP_DB_USER> (WordPress database user), <WP_DB_PASSWORD> (WordPress database password).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
WP_DB_PORT (WordPress database port), LOCAL_MULTISITE (Enable WordPress multisite mode), LOCAL_DEFAULT_BLOG_ID (Default blog ID for multisite), LOCAL_DEFAULT_SITE_ID (Default site ID for multisite), LOCAL_SSL_ENABLED (Enable SSL for database connection), LOCAL_SSL_CA_FILEPATH (Path to SSL CA certificate file), LOCAL_SSL_CERT_FILEPATH (Path to SSL certificate file), LOCAL_SSL_KEY_FILEPATH (Path to SSL key file).
Read and manage courses, members, orders, events, posts, and settings for Loopwise-powered sites.
Secure MCP server for WordPress content management
MCP server for Microsoft SharePoint — manage folders, documents, and metadata.
Read-only MCP server for WordPress + WooCommerce products, orders, sales, and posts.
Publish and manage WordPress pages, posts, media
MCP server for Ghost CMS: manage posts, pages, tags, SEO, members and newsletters via the Admin API.
MCP server for SocialAPI — manage social media comments, DMs, reviews, and mentions across platforms
MCP server for Plesk: manage domains, DNS, mail, SSL, backups, databases and WordPress via AI.
Answers built from our own checks of this server.