Wordpress MCP logo

Wordpress MCP

Manage one or more WordPress sites through MCP tools for content, users, settings, plugins, and themes.

Install Wordpress MCP

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": {
      "command": "npx",
      "args": [
        "-y",
        "@cavort-it-systems/wordpress-mcp"
      ],
      "env": {
        "WORDPRESS_SITES": "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.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The wordpress-mcp MCP server connects AI clients to one or more WordPress sites through the WordPress REST API. It supports reading and changing site settings, posts, pages, users, plugins, and themes, with compact responses intended to reduce unnecessary token usage. Configure sites in the WORDPRESS_SITES environment variable and identify targets by site ID. Reach for it when an agent needs authenticated WordPress administration or content workflows across multiple sites.

Use cases

  • Manage posts across multiple WordPress sites
  • Update WordPress pages and site settings
  • Review and manage WordPress users
  • Inspect and control installed plugins
  • Check active themes and site metadata

Key features

  • Multi-site configuration with site IDs
  • WordPress REST API operations
  • Token-reduced responses
  • Application Password authentication
  • Post and page CRUD
  • Plugin and theme management

Tools80

What Wordpress MCP lets your agent do. Expand a tool for its parameters.

Self-reported~741 tokens of context

Security & health

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

ActiveLast checked 3d ago

Recent health check succeeded.

9/9 checks healthy over the last 49d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @cavort-it-systems/wordpress-mcp (npm)

Adoption & maintenance

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

GitHub stars3Stargazers on the source repository.
npm downloads3.5kPackage downloads in the last 30 days.
Last commit16d agoMost recent push to the default branch.
Tools exposed80Callable tools this server registers over MCP.

How Wordpress MCP works

What wordpress-mcp MCP server does

The wordpress-mcp MCP server exposes WordPress management operations to MCP-compatible AI clients. It can inspect site information and settings, list REST API namespaces, and create, read, update, search, or delete posts and pages. User administration is also covered through tools for listing users, checking the authenticated user, and managing user records.

The server includes plugin and theme inspection. Agents can list plugins, retrieve plugin details, and activate, deactivate, or delete plugins using the plugin file path expected by the server, such as akismet/akismet.php. Theme tools list themes, identify the active theme, and retrieve details for a selected theme.

Responses are automatically reduced to essential fields instead of returning the full, verbose WordPress REST payload. The README gives examples of large reductions for post and plugin responses, but the exact response fields depend on the tool.

How it works

A single process can serve multiple WordPress installations. Each configured site has an ID, URL, username, and password. Call list_sites first to discover the available IDs; it returns site IDs and URLs without exposing passwords. Other tools receive the selected site ID as their site argument.

Authentication uses WordPress Application Passwords, available in WordPress 5.6 and later. The MCP process sends authenticated requests to the configured WordPress site and returns trimmed results to the client. Plugin activation, deactivation, and deletion use the mcp/v1 routes provided for those operations.

Setup and configuration

Install the package globally or run it with npx:

Terminal
npm install -g @cavort-it-systems/wordpress-mcp
npx @cavort-it-systems/wordpress-mcp

Set WORDPRESS_SITES to a JSON array containing objects with id, url, username, and password properties. The older single-site variables WORDPRESS_SITE_URL, WORDPRESS_USERNAME, and WORDPRESS_PASSWORD are no longer read.

For each WordPress account, create an Application Password under Users → Profile → Application Passwords. The README instructs users to preserve the spaces in the generated password. Claude Desktop can launch the server with an MCP configuration using npx; Claude Code can add it with claude mcp add and the same environment variable.

Tools and capabilities

The documented standard tools cover:

  • Site information, settings retrieval and updates, and REST namespace discovery
  • Post listing, filtering, searching, creation, editing, retrieval, and deletion
  • Page listing, creation, editing, retrieval, and deletion
  • User listing, current-user lookup, individual lookup, creation, editing, and deletion
  • Plugin listing, detail lookup, activation, deactivation, and deletion
  • Theme listing, active-theme lookup, and theme detail lookup

The wordpress-mcp MCP server also identifies configured sites without returning stored credentials, which is useful when an agent needs to choose a target before making a request.

Limitations and notes

Every tool other than list_sites requires a configured site ID. Credentials are stored in the WORDPRESS_SITES configuration, so access to the MCP process configuration should be restricted appropriately.

Plugin state changes require the relevant mcp/v1 routes and use a plugin file path rather than a plugin slug. The server is intended for WordPress sites that accept the configured Application Password credentials.

Reviews

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

Frequently Asked Questions about Wordpress MCP

wordpress-mcp is an MCP server that connects AI clients to one or more WordPress sites through authenticated REST API requests. Its main tools manage site settings, posts, pages, users, plugins, and themes, while list_sites discovers configured targets and responses are trimmed to reduce unnecessary token usage.

Install it with npm or run it through npx. Use `npm install -g @cavort-it-systems/wordpress-mcp` for a global installation, or run `npx @cavort-it-systems/wordpress-mcp` directly. You can also clone the repository and build it with `npm install && npm run build`.

Set the `WORDPRESS_SITES` environment variable to a JSON array of objects containing `id`, `url`, `username`, and `password`. Start with `list_sites` to see configured IDs, then pass the selected ID as the `site` argument to other tools.

It authenticates with WordPress Application Passwords. Create one under Users → Profile → Application Passwords in WordPress 5.6 or later, then place the generated password in the matching object within `WORDPRESS_SITES`.

Add an MCP server entry that runs `npx @cavort-it-systems/wordpress-mcp` and provide `WORDPRESS_SITES` in the entry's environment settings.

Related MCP servers

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 AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/wordpress-mcp?style=directory)](https://allmcps.com/mcp/wordpress-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/wordpress-mcp"><img src="https://allmcps.com/api/badge/wordpress-mcp?style=directory" alt="Wordpress MCP on AllMCPs" /></a>