MCP.Market

WordPress MCP Server

by rnaga·io.github.rnaga/wp-mcp·v1.0.9·9 stars

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

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
Growing

9 stars40 downloads/wk

Reviews

Write one

Nobody has reviewed WordPress MCP Server yet.

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

WordPress MCP Server tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • echo

    Returns the input string.

Public scan report

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

no findings
  • Code scan130 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 65 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How WordPress MCP Server compares

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

Safety score
78/100
higher than 57% of 48,243 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
9
more than 87% of 28,706 servers
Downloads a week
40
more than 30% of 12,306 servers with a package

What its tools let an agent do: 1 read

Install WordPress MCP Server in Claude Code, Cursor or VS Code

Runs npx -y @rnaga/wp-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add wp-mcp -- npx -y @rnaga/wp-mcp
Add to Cursor

What the publisher says

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

wp-mcp

@rnaga/wp-mcp is a Model Context Protocol (MCP) server for WordPress that turns your site into an AI-operable surface. By exposing WordPress CRUD primitives to clients like Claude Desktop, an assistant can draft a post on demand, refine it collaboratively, and publish it straight into your database—no trip through wp-admin required.

Here are a few common scenarios this unlocks:

  • Draft, revise, and publish posts directly from MCP clients such as Claude Desktop.
  • Inspect WordPress users, their roles, and capabilities to audit site permissions or generate access reports.

Built on top of @rnaga/wp-node, the server ships with a curated MCP toolset covering posts, users, comments, terms, revisions, metadata, options, and site settings. The MCP server can manage the following database tables/resources:

You can spin up a STDIO server for direct database access or host a Streamable HTTP MCP server for remote access. For convenience, layer on the CLI proxy whenever your MCP client needs a local bridge to the HTTP server. The proxy behaves like a local MCP server while relaying requests to the HTTP endpoint—perfect for clients that lack OAuth or WordPress Application Password support—so you can fit MCP workflows into existing editorial pipelines without re-implementing WordPress business logic.

The project includes a CLI (wp-mcp) that helps you:

  • configure and launch a local STDIO MCP server that connects straight to your WordPress database;
  • scaffold and initialize an Express-based Streamable HTTP MCP server (with env/TS boilerplate);
  • authenticate against a remote WordPress environment (OAuth or Application Password) and run a JSON-RPC proxy so MCP clients can reach it securely;
  • inspect available MCP primitives and manage the credentials stored under ~/.wp-mcp.

Run this command to list the available CLI commands:

npx @rnaga/wp-mcp -- --help
Usage: <command> <subcommand> [options]

Commands:
   local            Local MCP (stdio) server commands
   utils            Utility commands for configuration, debugging, and MCP inspection
   http             Scaffold a TypeScript project for the MCP streamable HTTP server and related tooling.
   remote           Remote MCP server commands

Together, the server, CLI utilities, and proxy tooling let you CRUD WordPress content, manage users, and sync settings through the MCP standard without re-implementing WordPress logic.

Getting Started

Local STDIO server

Run the STDIO server when you can reach the database directly. The CLI launches an MCP process that assumes a WordPress user locally and exposes your site's tools over STDIO to the MCP client.

flowchart LR
  client(["MCP Client<br/>(e.g. Claude Desktop)"])
  stdio(["Local STDIO MCP Server<br/>(wp-mcp CLI)"])
  db(["WordPress Database"])

  client <--> stdio
  stdio <--> db

Shortened. The full README is on GitHub.

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

WordPress MCP Server: common questions

Is WordPress MCP Server safe?
Mostly: it is graded B (78/100). Read the WordPress MCP Server safety report
How do I install WordPress MCP Server?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does WordPress MCP Server need an API key?
Yes. The registry entry asks for WP_DB_PASSWORD.
Is WordPress MCP Server maintained?
The last commit was 106 days ago (2026-07-22). The latest release is v1.0.9.
How does WordPress MCP Server compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,243 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.