← Back to Skills Marketplace
jordymeow

WordPress MCP

by jordymeow · GitHub ↗ · v3.3.4
cross-platform ⚠ suspicious
2135
Downloads
3
Stars
10
Active Installs
2
Versions
Install in OpenClaw
/install wordpress-mcp
Description
Manage WordPress sites via MCP (Model Context Protocol) through AI Engine. Use for creating/editing posts, SEO analysis, analytics, media management, taxonomy operations, social media scheduling, multilingual content (Polylang), and any WordPress admin task. Requires AI Engine plugin (free) with MCP Server enabled. Also use when asked about WordPress site management, content workflows, or WP-related tasks.
Usage Guidance
This skill appears to be a coherent controller for WordPress sites via AI Engine's MCP, but take these precautions before installing or using it: 1) Treat the Bearer Token as a high‑privilege secret — only use tokens for sites you administrate and avoid storing them in publicly accessible files; prefer short‑lived or scoped tokens if possible and revoke them after use. 2) Limit enabled MCP features on the target site — do not enable Database, Plugins, Themes, or Dynamic REST unless you explicitly need them, because those tools allow writing code and running SQL. 3) Because the package metadata does not declare the needed credential, assume the agent will require you to provide the token in conversation or a local TOOLS.md; avoid pasting tokens into shared chats or documents. 4) Verify the AI Engine plugin installation and inspect which MCP tools are exposed (run tools/list) before asking the agent to make destructive changes. 5) If you need to run sensitive operations (installing plugins, modifying theme files, direct SQL), perform them manually or under strict supervision rather than granting an automated agent broad autonomous privileges. If you want a higher assurance rating, ask the skill author/source for an explicit credential declaration, changelog, and a homepage or repo to verify origin.
Capability Analysis
Type: OpenClaw Skill Name: wordpress-mcp Version: 3.3.4 This skill bundle is classified as suspicious due to the exposure of highly privileged and dangerous capabilities that could lead to Remote Code Execution (RCE) and SQL Injection (SQLi) if misused or exploited. Specifically, the `references/dev-tools.md` and `references/features.md` files document tools like `wp_theme_put_file`, `wp_plugin_put_file` (allowing arbitrary file write to theme/plugin directories) and `wp_db_query` (allowing direct execution of SQL queries). While these tools are presented as intended for WordPress management and development, their power makes them critical vulnerabilities if the AI agent's input is not rigorously sanitized, enabling an attacker to compromise the target WordPress site. There is no evidence of intentional malicious prompt injection against the agent, unauthorized data exfiltration, or obfuscation within the skill bundle itself.
Capability Assessment
Purpose & Capability
The name/description (manage WP via AI Engine MCP) aligns with the documented tools: posts, media, SEO, Polylang, WooCommerce, plugin/theme management and database queries. Those capabilities are appropriate for an administrative WP management skill. However the skill metadata declares no required credential or primary credential while the SKILL.md clearly requires a site URL and a Bearer Token — this mismatch is important (the skill will not function without that secret).
Instruction Scope
SKILL.md explicitly instructs the agent how to call the MCP endpoint and to store URL+Bearer Token in a TOOLS.md file. The documented tools permit extremely powerful actions (write plugin/theme files, install/activate plugins/themes, execute arbitrary SQL via wp_db_query, dynamic REST access). Those actions are coherent for a full admin toolset, but they are high privilege and can alter site code or data. The instructions do not attempt to restrict use of these dangerous operations (beyond a note of caution for SQL), so the agent could perform destructive or invasive actions if invoked with an admin token.
Install Mechanism
Instruction-only skill, no install spec and no code files to run on the agent host — this minimizes local install risk. Nothing is downloaded or written by the skill package itself.
Credentials
Metadata lists no required environment variables or primary credential, but SKILL.md requires a Bearer Token and MCP URL stored in TOOLS.md. The skill therefore implicitly needs a secret (site administrator token) but does not declare it in the registry. This lack of declared credential handling is an incoherence that could cause accidental token exposure (e.g., if stored in a shared doc or memory). The operations the token enables (file writes, SQL, plugin activation) justify needing a high‑privilege secret, but the skill should explicitly declare that requirement and guide secure handling.
Persistence & Privilege
always:false and no install steps that persist on the agent host. The skill can be invoked autonomously by models (default platform behavior), which increases blast radius if combined with other issues, but autonomy alone is not a new red flag here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install wordpress-mcp
  3. After installation, invoke the skill by name or use /wordpress-mcp
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.3.4
- Major update: Skill documentation now reflects modular MCP features and site-specific tool discovery. - Clarified that only WordPress core tools are enabled by default; all other features (SEO, plugins, WooCommerce, etc.) must be enabled per site. - Added table listing available MCP features, with descriptions and enablement status. - Removed long-form tool inventories; referenced new `references/features.md` for per-feature tool details. - Strongly emphasized workflow: always use `tools/list` to check which tools are enabled before use. - Refreshed workflows and tips to align with the modular, feature-based tool system.
v3.3.3
- Improved and clarified setup instructions for connecting to WordPress sites using MCP (Model Context Protocol). - Expanded and reorganized tool documentation, with clear categories and key tools for content, SEO, WooCommerce, social publishing, and multilingual workflows. - Added usage tips, best practices, and example workflows for content audit, publishing, analytics, translation, and multisite management. - Explicitly documents current toolset coverage (143 tools as of v3.3) with plugin requirements and references for advanced operations. - Emphasizes use cases, connectivity verification, and troubleshooting.
Metadata
Slug wordpress-mcp
Version 3.3.4
License
All-time Installs 12
Active Installs 10
Total Versions 2
Frequently Asked Questions

What is WordPress MCP?

Manage WordPress sites via MCP (Model Context Protocol) through AI Engine. Use for creating/editing posts, SEO analysis, analytics, media management, taxonomy operations, social media scheduling, multilingual content (Polylang), and any WordPress admin task. Requires AI Engine plugin (free) with MCP Server enabled. Also use when asked about WordPress site management, content workflows, or WP-related tasks. It is an AI Agent Skill for Claude Code / OpenClaw, with 2135 downloads so far.

How do I install WordPress MCP?

Run "/install wordpress-mcp" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is WordPress MCP free?

Yes, WordPress MCP is completely free (open-source). You can download, install and use it at no cost.

Which platforms does WordPress MCP support?

WordPress MCP is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created WordPress MCP?

It is built and maintained by jordymeow (@jordymeow); the current version is v3.3.4.

💬 Comments