MCP.Market

Wordpress MCP server

by cvrt-jh·io.github.cvrt-jh/wordpress-mcp·v1.0.0·3 stars
No reviews yet

Lightweight WordPress MCP server - 42 tools, token-optimized (95% smaller responses)

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

3 stars511 downloads/wk

Reviews

Write one

Nobody has reviewed Wordpress yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Wordpress tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan27 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Wordpress compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers
Downloads a week
511
more than 88% of 12,191 servers with a package

Install Wordpress in Claude Code, Cursor or VS Code

Runs npx -y @cavort-it-systems/wordpress-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add wordpress-mcp -- npx -y @cavort-it-systems/wordpress-mcp
Add to Cursor

What the publisher says

From the Wordpress repository's README, as published. We do not edit it. Read it on GitHub

wordpress-mcp

Lightweight WordPress MCP server for site management. 249 tools with token-optimized responses - REST API responses automatically slimmed from kilobytes to essentials.

v3.2: legalconsentlogget / legalconsentlogstats / legalconsentlogexport for the cvrt-legal consent decision log (needs cvrt-legal 0.5.0+); legalputconsent takes logenabled.

v3.1: Tools for our own plugins - seo (31) for cvrt-seo-manager, legal (15) for cvrt-legal incl. legallinkpage (cvrt-legal 0.4.2+), and fulfillment_* (8) for cvrt-order-fulfillment.

v3.0 (BREAKING): Multi-site - one server instance manages any number of sites via a single WORDPRESSSITES env var. Every tool now requires a site argument; use the new listsites tool to discover configured ids. The old single-site env vars are removed. wpactivateplugin / wpdeactivateplugin / wpdeleteplugin now use cvrt-mcp-endpoints mcp/v1 routes and take the plugin file path (e.g. akismet/akismet.php) instead of a slug.

v2.1: Now includes Pro modules for ACF and WooCommerce via wp-pilot-pro.

v2.0: Extended tools for the cvrt-mcp-endpoints plugin - install plugins/themes from WordPress.org, database management, full widget/menu control, and more.

Why This Server?

WordPress REST API returns extremely verbose JSON (~5-10KB per post). This server strips it down:

Less tokens = faster responses, lower costs, more context for your AI.

Installation

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

Or run directly:

npx @cavort-it-systems/wordpress-mcp

Configuration

v3.0 is multi-site (BREAKING CHANGE). A single server instance now manages any number of WordPress sites, defined in one WORDPRESSSITES env var as a JSON array of {id, url, username, password} objects. The old single-site env vars (WORDPRESSSITEURL, WORDPRESSUSERNAME, WORDPRESSPASSWORD) are no longer read - set WORDPRESSSITES instead.

Every tool (except listsites) now requires a site argument naming the target site id. Call listsites first to discover which ids are configured - it returns {id, url} for each site (passwords are never returned or logged).

Claude Desktop / Manual

Add to your MCP config (~/.claude.json or Claude Desktop settings):

{
  "mcpServers": {
    "wordpress": {
      "command": "npx",
      "args": ["@cavort-it-systems/wordpress-mcp"],
      "env": {
        "WORDPRESS_SITES": "[{\"id\":\"boardcouture\",\"url\":\"https://boardcouture.shop\",\"username\":\"cavortkonzepte\",\"password\":\"xxxx xxxx xxxx\"}]"
      }
    }
  }
}

Add more sites by appending objects to the WORDPRESS_SITES array - one server instance handles them all.

Claude Code CLI

claude mcp add wordpress \
  -e WORDPRESS_SITES='[{"id":"boardcouture","url":"https://boardcouture.shop","username":"cavortkonzepte","password":"xxxx xxxx xxxx"}]' \
  -- npx @cavort-it-systems/wordpress-mcp

From Source

git clone https://github.com/cvrt-jh/wordpress-mcp.git
cd wordpress-mcp
npm install && npm run build

Authentication

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Wordpress: common questions

Is Wordpress MCP server safe?
Mostly: it is graded B (83/100). Read the Wordpress safety report
How do I install Wordpress?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Wordpress need an API key?
Yes. The registry entry asks for WORDPRESS_PASSWORD.
Is Wordpress maintained?
The last commit was 37 days ago (2026-09-28). The latest release is v1.0.0.
How does Wordpress compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers); downloads a week 511 (more than 88% of 12,191 servers with a package). Full comparison.