Unlock MCP Potential para WordPress
DanielBoring/unlock-mcp-potential
Controle editorial de WordPress para agentes de IA via MCP
Ver no GitHubPlugin WordPress que expande as capacidades do MCP Adapter, permitindo que agentes de IA gerenciem posts, páginas, mídia, comentários, SEO e segurança. Funciona como camada de abilities complementar ao oficial MCP Adapter, oferecendo controle editorial completo via protocolo MCP.
Instalação
npx convez-ai DanielBoring/unlock-mcp-potential1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Agentes de IA redigindo, editando e publicando posts e páginas automaticamente
- Auditorias de segurança e saúde do site integradas ao workflow de conteúdo
- Análise de SEO automatizada durante criação de conteúdo
- Gerenciamento de mídia, comentários e usuários via AI agent
Veredito

MCP server robusto que transforma WordPress em plataforma controlável por IA, com segurança via roles e application passwords. Requer instalação de dois plugins (MCP Adapter + este), idealizando o use case de editorial automation com agentes Claude.
README
A tradução para o português deste README ainda está na fila.
Quickstart • Architecture • MCP Abilities • Requirements • Versioning • Installation • Verification • Security
Unlock MCP Potential is a WordPress plugin that adds MCP-powered content management abilities for posts, pages, media, comments, plugins, SEO checks, site health, security audits, and user lookup. It works with the official MCP Adapter plugin, which provides the transport layer while this plugin registers the abilities an AI agent can call.
- You want an AI agent to draft, update, or publish posts and pages
- You want to ask an AI to audit your site's security or health posture
- You want SEO analysis integrated into your content workflow
- You open
mcp-adapter-discover-abilitiesand see only the adapter's own meta abilities, with no content tools
Without this plugin
Only the MCP Adapter's 3 meta/discovery abilities are visible — no content tools.

With this plugin
All abilities available: full editorial access to posts, pages, taxonomy, comments, media, plugin management, user lookup, security, and SEO.

Quickstart
1. Install Official WordPress MCP Adapter Plugin Download the latest release zip → WP Admin → Plugins → Add New → Upload Plugin → Install & Activate
2. Install Unlock MCP Potential Plugin Download the latest release zip → WP Admin → Plugins → Add New → Upload Plugin → Install & Activate
3. Create a dedicated Editor user WP Admin → Users → Add New → set Role to Editor → Add New User
4. Create an application password WP Admin → Users → edit the user → Application Passwords → enter a name → Add → copy the password
5. Configure your MCP client See Step 5 — Connect your MCP client for config snippets covering Claude Code, Claude Desktop, GitHub Copilot (VS Code), GitHub Copilot CLI, Codex, Windsurf, Gemini CLI, and ChatGPT.
6. Verify
Ask your MCP client or agent to call mcp-adapter-discover-abilities — you should see additional abilities enabled by this companion plugin.
Architecture
AI Agent (e.g. Claude Code, Codex, etc)
│
│ MCP Protocol (JSON-RPC over HTTP)
▼
@automattic/mcp-wordpress-remote ← MCP server (npm process, runs locally)
│
│ HTTPS · WordPress REST API
│ POST /wp-json/mcp/mcp-adapter-default-server
▼
MCP Adapter plugin ← framework: registers the REST endpoint,
(WordPress/mcp-adapter) handles the MCP session, routes calls
│
│ calls wp_register_ability() handlers at runtime
▼
Unlock MCP Potential plugin ← this plugin: registers the actual
(this repo) abilities the AI can call
│
│ WordPress core APIs (no direct DB queries)
▼
WordPress database
The MCP Adapter handles the transport layer. This plugin handles the content — it registers abilities using wp_register_ability() that the adapter then exposes as MCP tools.
MCP Abilities
New abilities and feature requests are tracked in GitHub Issues.
Role overview
Each ability enforces a WordPress capability check. The table below maps standard WordPress roles to the plugin-relevant capabilities they provide so you can choose the right role for your MCP service account.
| Role | Plugin-relevant capabilities provided | Suitable for |
|---|---|---|
| Subscriber | read | Read-only taxonomy browsing |
| Author | edit_posts, delete_posts, upload_files | Creating and managing the agent's own posts and media |
| Editor ✓ | All Author caps + edit_pages, delete_pages, manage_categories, moderate_comments | Full editorial control — recommended default |
| Administrator | All Editor caps, plus list_users, manage_options, activate_plugins, and other administrative capabilities | User lookup, plugin management, and sensitive site-audit workflows |
Scope note for
edit_posts: This capability is available to Authors and above, but WordPress scopes query results to the authenticated user's own content unlessedit_others_postsis also present. An Editor account (which hasedit_others_posts) sees all content site-wide. Use Author only if the agent should be limited to content it created.
Posts
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/list-posts | List posts with filters (status, search, author, category, pagination) | edit_posts | Author † |
unlock-mcp-potential/get-post | Get a single post by ID | edit_post | Author † |
unlock-mcp-potential/create-post | Create a new post with title, content, status, categories, tags | edit_posts | Author |
unlock-mcp-potential/update-post | Update an existing post | edit_post | Author † |
unlock-mcp-potential/delete-post | Move a post to trash | delete_post | Author † |
unlock-mcp-potential/restore-post | Restore a post from trash | delete_post | Author † |
† Returns or acts on the service account's own posts only. Use Editor to manage all posts site-wide.
Pages
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/list-pages | List pages with filters | edit_pages | Editor |
unlock-mcp-potential/get-page | Get a single page by ID | edit_post | Editor |
unlock-mcp-potential/create-page | Create a new page | edit_pages | Editor |
unlock-mcp-potential/update-page | Update an existing page | edit_post | Editor |
unlock-mcp-potential/delete-page | Move a page to trash | delete_post | Editor |
unlock-mcp-potential/restore-page | Restore a page from trash | delete_post | Editor |
Taxonomy
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/list-categories | List all categories | read | Subscriber |
unlock-mcp-potential/list-tags | List all tags | read | Subscriber |
unlock-mcp-potential/create-category | Create a new category | manage_categories | Editor |
unlock-mcp-potential/create-tag | Create a new tag | manage_categories | Editor |
unlock-mcp-potential/delete-category | Permanently delete a category by ID | manage_categories | Editor |
unlock-mcp-potential/delete-tag | Permanently delete a tag by ID | manage_categories | Editor |
Comments
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/list-comments | List comments with filters (post, status, search) | moderate_comments | Editor |
unlock-mcp-potential/approve-comment | Approve a comment | moderate_comments | Editor |
unlock-mcp-potential/trash-comment | Move a comment to trash | moderate_comments | Editor |
unlock-mcp-potential/spam-comment | Mark a comment as spam | moderate_comments | Editor |
Media
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/list-media | List media items with filters (MIME type, search, pagination) | upload_files | Author |
unlock-mcp-potential/get-media | Get a single media item by ID | edit_post | Author † |
unlock-mcp-potential/update-media | Update media alt text, title, and caption | edit_post | Author † |
unlock-mcp-potential/delete-media | Permanently delete a media item | delete_post | Author † |
† Author-role access is scoped to media owned by the authenticated user. Use Editor to manage media site-wide.
Users
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/list-users | List users with filters (role, search, pagination) | list_users | Administrator |
unlock-mcp-potential/get-user | Get a single user by ID | list_users | Administrator |
Plugins
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/list-plugins | List installed plugins with version, activation state, network activation, auto-update, and update availability | activate_plugins | Administrator |
unlock-mcp-potential/activate-plugin | Activate a plugin by canonical plugin basename, or by slug when it resolves to exactly one plugin | activate_plugins | Administrator |
unlock-mcp-potential/deactivate-plugin | Deactivate a plugin by canonical plugin basename, with protected-plugin and multisite safeguards | activate_plugins | Administrator |
Plugin management abilities require Administrator-level plugin capabilities. Network-wide activation or deactivation is only available on multisite installations and requires manage_network_plugins.
Site Health
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/site-health-check | Run WordPress's built-in health tests; returns results grouped by severity (critical / recommended / good) | manage_options | Administrator |
Security Audit
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/security-audit | Check for common security issues: debug mode, file editor, SSL, admin username, WP/plugin version currency, XMLRPC, and auth key strength | manage_options | Administrator |
Returns findings in fail / warn / pass buckets with actionable descriptions.
SEO Analysis
| Ability | Description | Required Capability | Min. Role |
|---|---|---|---|
unlock-mcp-potential/seo-analyze-post | Analyze a single post or page: title length, word count, meta description, focus keyword placement, image alt text, internal links, slug length | edit_post | Author † |
unlock-mcp-potential/seo-site-overview | Site-wide SEO snapshot: sitemap and robots.txt accessibility, count of published posts missing Yoast focus keyword or meta description | manage_options | Administrator |
With Yoast SEO installed: all checks run fully, including meta description and focus keyword analysis per post, site-wide counts of unoptimized content, and Yoast sitemap verification.
Without Yoast SEO: structural checks work correctly (title length, word count, image alt text, internal links, slug length, robots.txt). However, seo-analyze-post will always warn about missing meta description and focus keyword on every post, and seo-site-overview will report every published post as unoptimized — because those Yoast meta fields are never populated. The sitemap check will also fail since it targets the Yoast-specific /sitemap_index.xml URL. Treat those specific findings as not applicable if Yoast is not installed.
Requirements
| Requirement | Version |
|---|---|
| WordPress | 6.9+ |
| PHP | 8.0+ |
| MCP Adapter plugin | Latest |
| Yoast SEO | Optional — structural SEO checks work without it; meta description, focus keyword, and sitemap checks require it |
Self-hosted WordPress only. Both this plugin and the MCP Adapter require a WordPress installation where custom plugins can be installed — self-hosted WordPress or a managed host (WP Engine, Kinsta, Flywheel, etc.). They are not compatible with WordPress.com Free, Personal, or Premium plans, which do not allow custom plugin installation.
Versioning
This project follows Semantic Versioning (MAJOR.MINOR.PATCH):
- MAJOR (
X.0.0) for breaking changes that can impact existing MCP clients. - MINOR (
1.X.0) for new backward-compatible abilities/features. - PATCH (
1.4.X) for backward-compatible fixes (including security and bug fixes).
See CONTRIBUTING.md for the full release/versioning policy.
Installation
1. Install the MCP Adapter plugin
This plugin depends on MCP Adapter being installed and active. Install it first from the official WordPress MCP Adapter project or its latest release, then upload and activate it in WP Admin → Plugins → Add New → Upload Plugin.
2. Install Unlock MCP Potential
Coming soon to the WordPress Plugin Directory — this plugin has been submitted for review. Once approved, you'll be able to install it directly from WP Admin → Plugins → Add New by searching "Unlock MCP Potential". Until then, use one of the options below.
Option A — Upload zip (recommended for most sites)
- Download or build the zip:
git clone https://github.com/DanielBoring/unlock-mcp-potential.git unlock-mcp-potential zip -r unlock-mcp-potential.zip unlock-mcp-potential --exclude='unlock-mcp-potential/.git/*' - In WP Admin, go to Plugins → Add New → Upload Plugin
- Upload
unlock-mcp-potential.zipand click Install Now - Click Activate Plugin
Option B — Direct file copy (server access)
cp -r unlock-mcp-potential /var/www/html/wp-content/plugins/
wp plugin activate unlock-mcp-potential
3. Create a dedicated WordPress user
It is recommended to create a dedicated user for your AI agent rather than using your personal admin account. This limits what the agent can do and makes it easy to revoke access later.
- In WP Admin, go to Users → Add New User
- Fill in a username (e.g.
ai-editor) and email address - Set the Role to Editor
- Click Add New User
Why Editor and not Administrator? Editor is still the recommended default for content workflows and covers the editorial capabilities used by posts, pages, taxonomy, comments, and media (
edit_posts,edit_pages,delete_posts,delete_pages,upload_files,manage_categories, andmoderate_comments). User lookup, plugin management, and sensitive site-audit abilities require Administrator capabilities such aslist_users,activate_plugins, ormanage_options. Use a separate dedicated Administrator service account for those workflows and keep the Editor account for day-to-day content operations. See the Role overview for the full breakdown.
4. Create an application password
Application passwords are separate from the user's login password and can be revoked independently.
- In WP Admin, go to Users → All Users and click the dedicated user you just created
- Scroll down to the Application Passwords section
- Enter a name for the password (e.g.
Claude Code) and click Add New Application Password - Copy the generated password immediately — it is only shown once
The password will be in the format xxxx xxxx xxxx xxxx xxxx xxxx. Keep the spaces when using it in your MCP config.
5. Connect your MCP client
Configure @automattic/mcp-wordpress-remote to point at the MCP Adapter endpoint on your WordPress site. The published package reads WP_API_URL, WP_API_USERNAME, and WP_API_PASSWORD; set WP_API_URL to the full /wp-json/mcp/mcp-adapter-default-server URL. Select your client below:
Add to ~/.claude/settings.json:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
"WP_API_USERNAME": "ai-editor",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
"WP_API_USERNAME": "ai-editor",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}
Requires VS Code 1.99+. Add to .vscode/mcp.json in your project (workspace-scoped) or your VS Code user profile (global).
Note: VS Code uses
"servers"as the root key, not"mcpServers". Copying a Claude or Cursor config without changing this key is the most common setup mistake.
{
"servers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
"WP_API_USERNAME": "ai-editor",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}
Add to ~/.copilot/mcp-config.json:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
"WP_API_USERNAME": "ai-editor",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}
Add to ~/.codex/config.toml (global) or .codex/config.toml in your project root (project-scoped, trusted projects only):
[mcp_servers.wordpress]
command = "npx"
args = ["-y", "@automattic/mcp-wordpress-remote@latest"]
[mcp_servers.wordpress.env]
WP_API_URL = "https://your-site.com/wp-json/mcp/mcp-adapter-default-server"
WP_API_USERNAME = "ai-editor"
WP_API_PASSWORD = "xxxx xxxx xxxx xxxx xxxx xxxx"
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
"WP_API_USERNAME": "ai-editor",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}
Add to ~/.gemini/settings.json:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
"WP_API_USERNAME": "ai-editor",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}
ChatGPT's MCP integration works differently from the tools above. Rather than a local config file, it is configured through Settings → Connected Apps in the ChatGPT web interface, and it connects to remote HTTP endpoints rather than local stdio processes.
@automattic/mcp-wordpress-remote runs as a local npm process and cannot be connected from ChatGPT directly without hosting the server at a public URL. ChatGPT MCP support is also currently limited to Business, Enterprise, and Edu plans. If you have a publicly hosted MCP endpoint and an eligible plan, add it via the Connected Apps UI.
Verification
mcp-adapter-discover-abilities is an MCP tool registered by the WordPress MCP Adapter plugin — it is not a CLI command. Invoke it through your AI assistant's chat interface by asking your agent to call it. The tool name and behaviour are the same across all supported clients; only the invocation method differs.
| Client | How to invoke |
|---|---|
| Claude Code / Claude Desktop | Ask Claude: "Call mcp-adapter-discover-abilities" |
| GitHub Copilot (VS Code / CLI) | Ask Copilot in chat: "Use the mcp-adapter-discover-abilities tool" |
| Codex | Ask Codex: "Run mcp-adapter-discover-abilities" |
| Windsurf / Gemini CLI | Ask the assistant to call mcp-adapter-discover-abilities |
You should see the MCP Adapter's built-in meta/discovery abilities plus all abilities registered by this plugin.
To confirm everything is working, ask your agent to call a few abilities:
unlock-mcp-potential/list-posts— "List the 5 most recent published posts"unlock-mcp-potential/security-auditwith an Administrator service account — "Run a security audit of my WordPress site"unlock-mcp-potential/site-health-checkwith an Administrator service account — "Check WordPress site health"unlock-mcp-potential/list-pluginswith an Administrator service account — "List installed plugins and their activation state"
Security
- All abilities enforce WordPress capability checks via
permission_callback. The ability list reflects what the authenticated user is actually allowed to do — an editor cannot call abilities that require admin caps. delete-postanddelete-pagemove content to trash, not permanent deletion. Userestore-postandrestore-pageto untrash content.- Plugin activation and deactivation require
activate_plugins; network-wide changes require multisite andmanage_network_plugins. Deactivation is blocked for protected plugins unless explicitly forced. - Content is sanitized on write:
sanitize_text_field()for strings,wp_kses_post()for HTML content,absint()for IDs, and enum validation for status fields. - No direct database queries — all reads and writes go through the WordPress API.