# WordPress MCP Server [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/rnaga/wp-mcp  
**GitHub Stars:** 10  
**npm Downloads (last month):** 289  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wordpress-mcp-server

## Description
MCP server for WordPress. Manage posts, users, comments, terms, metadata, and settings.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "wordpress-mcp-server": {
    "command": "npx",
    "args": ["-y","@rnaga/wp-mcp"],
    "env": {
      "LOCAL_USERNAME": "",
      "LOCAL_CONFIG": "",
      "WP_DB_HOST": "",
      "WP_DB_PORT": "",
      "WP_DB_NAME": "",
      "WP_DB_USER": "",
      "WP_DB_PASSWORD": "",
      "LOCAL_SSL_ENABLED": ""
    }
  }
}
```

**Requires environment variables:** `LOCAL_USERNAME`, `LOCAL_CONFIG`, `WP_DB_HOST`, `WP_DB_PORT`, `WP_DB_NAME`, `WP_DB_USER`, `WP_DB_PASSWORD`, `LOCAL_SSL_ENABLED` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/wordpress-mcp-server/readme_