Log inSubmit server
WordPress MCP Server logo

WordPress MCP Server

Manage WordPress content, users, comments, taxonomies, metadata, revisions, and settings through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install WordPress MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "wordpress-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@rnaga/wp-mcp"
      ],
      "env": {
        "LOCAL_USERNAME": "YOUR_VALUE_HERE",
        "LOCAL_CONFIG": "YOUR_VALUE_HERE",
        "WP_DB_HOST": "YOUR_VALUE_HERE",
        "WP_DB_PORT": "YOUR_VALUE_HERE",
        "WP_DB_NAME": "YOUR_VALUE_HERE",
        "WP_DB_USER": "YOUR_VALUE_HERE",
        "WP_DB_PASSWORD": "YOUR_VALUE_HERE",
        "LOCAL_SSL_ENABLED": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @rnaga/wp-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

WordPress MCP Server MCP server exposes WordPress content and administration operations through MCP tools. It supports local STDIO access to a WordPress database, Streamable HTTP hosting, and a CLI proxy for remote clients. Available operations depend on the assumed WordPress user's roles and capabilities. Use it when an MCP client needs to create or manage WordPress data without relying on wp-admin.

Use cases

  • Draft and publish WordPress posts from an MCP client
  • Audit WordPress users, roles, and capabilities
  • Moderate comments and create generated replies
  • Manage categories, tags, and custom taxonomies
  • Update WordPress metadata and site settings

Key features

  • CRUD operations for posts and revisions
  • User, role, and capability inspection
  • Comment and taxonomy management
  • Metadata, options, and settings support
  • STDIO, Streamable HTTP, and CLI proxy modes
  • Capability-based tool filtering

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 34d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @rnaga/wp-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars10Stargazers on the source repository.
npm downloads289Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How WordPress MCP Server works

What WordPress MCP Server MCP server does

WordPress MCP Server MCP server connects MCP clients with a WordPress database and exposes CRUD-style operations for common WordPress resources. It is built on @rnaga/wp-node and is intended for workflows such as drafting and publishing posts, reviewing users and permissions, moderating comments, and maintaining site configuration.

Supported resources include posts and revisions, comments, users, terms, metadata, options, and site settings. Metadata operations cover post, user, comment, term, and site metadata. Terms can represent categories, tags, and custom taxonomies.

The server can expose operations according to a WordPress user's native capabilities. An administrator may receive broad create, update, and delete access, while a subscriber may see a smaller set of tools.

How it works

The local mode starts a STDIO MCP process that connects directly to the WordPress database. An MCP client launches that process and communicates with it over STDIO. The local configuration wizard collects database connection details, including optional SSL certificate paths for secured database access.

The Streamable HTTP mode provides a remotely reachable MCP endpoint. The included CLI can scaffold an Express and TypeScript project for this server. When a client cannot handle OAuth or WordPress Application Password authentication, the CLI proxy can run locally and forward MCP requests to a remote HTTP server.

WordPress MCP Server MCP server uses the selected WordPress username to determine which primitives are available. The utils list-prims command displays each primitive, its description, and its required capabilities or roles.

Setup and configuration

Install and invoke the CLI with npx @rnaga/wp-mcp -- --help. For a local deployment, run npx @rnaga/wp-mcp -- local config-set and provide the database host, port, name, user, and password. Start the local process with local start, passing the WordPress username through LOCAL_USERNAME or the --username option.

A custom WordPress configuration manifest can be supplied with LOCAL_CONFIG or --file. Database settings can be saved through the CLI or exported as environment variables. Use the MCP Inspector to test tools and inspect responses through a browser interface at http://localhost:6274.

Remote deployments can use OAuth or WordPress Application Password authentication. The CLI stores credentials under ~/.wp-mcp and provides remote commands for authentication and proxy operation.

Tools and capabilities

WordPress MCP Server MCP server provides tools for:

  • Creating, reading, updating, and deleting posts and revisions.
  • Inspecting and managing WordPress users, roles, and capabilities.
  • Reading and moderating comments, including creating replies.
  • Managing categories, tags, and custom taxonomy terms.
  • Inspecting, creating, updating, and deleting supported metadata.
  • Changing site-level options and settings.
  • Listing available MCP primitives and their access requirements.

The exact tool set is filtered by the active user's WordPress permissions, so a client may not see every operation in every deployment.

Limitations and notes

Direct local access requires connectivity to the WordPress database and a suitable database configuration. Remote use requires an HTTP deployment plus supported authentication through OAuth or an Application Password.

Capability filtering reduces access to privileged operations, but the chosen WordPress account still determines what the client can do. Review the available primitives before connecting an agent to a production site, and take care when granting accounts write or administrative capabilities.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about WordPress MCP Server

WordPress MCP Server is an MCP server that connects AI clients to a WordPress database through STDIO or Streamable HTTP. Its main tools manage posts, revisions, users, comments, terms, metadata, options, and site settings, with access filtered by the selected WordPress user's roles and capabilities.

Run it through `npx @rnaga/wp-mcp`, then use `local config-set` to configure a database connection or scaffold an HTTP project with the `http` commands. Configure your MCP client to launch `local start` for a local STDIO deployment.

Yes, WordPress MCP Server works with Claude Desktop through its STDIO mode. Add an MCP server entry that runs `npx -y @rnaga/wp-mcp -- local start`, set `LOCAL_USERNAME`, then restart Claude Desktop so the WordPress tools become available.

Yes, it can connect to a remote environment through a Streamable HTTP server and CLI proxy. Remote authentication supports OAuth or WordPress Application Passwords, and the proxy gives clients a local MCP endpoint that relays requests to the HTTP server.

It filters available MCP primitives according to the selected WordPress user's capabilities and roles. Use `npx @rnaga/wp-mcp -- utils list-prims` to inspect each primitive and its required permissions before connecting a client.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWordPress MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/wordpress-mcp-server?style=directory)](https://allmcps.com/mcp/wordpress-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/wordpress-mcp-server"><img src="https://allmcps.com/api/badge/wordpress-mcp-server?style=directory" alt="WordPress MCP Server on AllMCPs" /></a>