convez.ai
MCP ServerDesenvolvimento WebIntermediário
DanielBoring

Unlock MCP Potential para WordPress

DanielBoring/unlock-mcp-potential

Controle editorial de WordPress para agentes de IA via MCP

Ver no GitHub
InicialPluginScore · de 0 a 100

Plugin 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-potential

1 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

Estrelas
1
Forks
0
Acompanhando
0
Saúde
85%
Último commit
há 2 dias
Versão
v3.1.0
Issues abertas
1
Contribuidores
2

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-abilities and 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.

Before

With this plugin

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

After


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.

RolePlugin-relevant capabilities providedSuitable for
SubscriberreadRead-only taxonomy browsing
Authoredit_posts, delete_posts, upload_filesCreating and managing the agent's own posts and media
Editor ✓All Author caps + edit_pages, delete_pages, manage_categories, moderate_commentsFull editorial control — recommended default
AdministratorAll Editor caps, plus list_users, manage_options, activate_plugins, and other administrative capabilitiesUser 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 unless edit_others_posts is also present. An Editor account (which has edit_others_posts) sees all content site-wide. Use Author only if the agent should be limited to content it created.


Posts

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/list-postsList posts with filters (status, search, author, category, pagination)edit_postsAuthor †
unlock-mcp-potential/get-postGet a single post by IDedit_postAuthor †
unlock-mcp-potential/create-postCreate a new post with title, content, status, categories, tagsedit_postsAuthor
unlock-mcp-potential/update-postUpdate an existing postedit_postAuthor †
unlock-mcp-potential/delete-postMove a post to trashdelete_postAuthor †
unlock-mcp-potential/restore-postRestore a post from trashdelete_postAuthor †

† Returns or acts on the service account's own posts only. Use Editor to manage all posts site-wide.

Pages

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/list-pagesList pages with filtersedit_pagesEditor
unlock-mcp-potential/get-pageGet a single page by IDedit_postEditor
unlock-mcp-potential/create-pageCreate a new pageedit_pagesEditor
unlock-mcp-potential/update-pageUpdate an existing pageedit_postEditor
unlock-mcp-potential/delete-pageMove a page to trashdelete_postEditor
unlock-mcp-potential/restore-pageRestore a page from trashdelete_postEditor

Taxonomy

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/list-categoriesList all categoriesreadSubscriber
unlock-mcp-potential/list-tagsList all tagsreadSubscriber
unlock-mcp-potential/create-categoryCreate a new categorymanage_categoriesEditor
unlock-mcp-potential/create-tagCreate a new tagmanage_categoriesEditor
unlock-mcp-potential/delete-categoryPermanently delete a category by IDmanage_categoriesEditor
unlock-mcp-potential/delete-tagPermanently delete a tag by IDmanage_categoriesEditor

Comments

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/list-commentsList comments with filters (post, status, search)moderate_commentsEditor
unlock-mcp-potential/approve-commentApprove a commentmoderate_commentsEditor
unlock-mcp-potential/trash-commentMove a comment to trashmoderate_commentsEditor
unlock-mcp-potential/spam-commentMark a comment as spammoderate_commentsEditor

Media

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/list-mediaList media items with filters (MIME type, search, pagination)upload_filesAuthor
unlock-mcp-potential/get-mediaGet a single media item by IDedit_postAuthor †
unlock-mcp-potential/update-mediaUpdate media alt text, title, and captionedit_postAuthor †
unlock-mcp-potential/delete-mediaPermanently delete a media itemdelete_postAuthor †

† Author-role access is scoped to media owned by the authenticated user. Use Editor to manage media site-wide.

Users

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/list-usersList users with filters (role, search, pagination)list_usersAdministrator
unlock-mcp-potential/get-userGet a single user by IDlist_usersAdministrator

Plugins

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/list-pluginsList installed plugins with version, activation state, network activation, auto-update, and update availabilityactivate_pluginsAdministrator
unlock-mcp-potential/activate-pluginActivate a plugin by canonical plugin basename, or by slug when it resolves to exactly one pluginactivate_pluginsAdministrator
unlock-mcp-potential/deactivate-pluginDeactivate a plugin by canonical plugin basename, with protected-plugin and multisite safeguardsactivate_pluginsAdministrator

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

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/site-health-checkRun WordPress's built-in health tests; returns results grouped by severity (critical / recommended / good)manage_optionsAdministrator

Security Audit

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/security-auditCheck for common security issues: debug mode, file editor, SSL, admin username, WP/plugin version currency, XMLRPC, and auth key strengthmanage_optionsAdministrator

Returns findings in fail / warn / pass buckets with actionable descriptions.

SEO Analysis

AbilityDescriptionRequired CapabilityMin. Role
unlock-mcp-potential/seo-analyze-postAnalyze a single post or page: title length, word count, meta description, focus keyword placement, image alt text, internal links, slug lengthedit_postAuthor †
unlock-mcp-potential/seo-site-overviewSite-wide SEO snapshot: sitemap and robots.txt accessibility, count of published posts missing Yoast focus keyword or meta descriptionmanage_optionsAdministrator

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

RequirementVersion
WordPress6.9+
PHP8.0+
MCP Adapter pluginLatest
Yoast SEOOptional — 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)

  1. 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/*'
    
  2. In WP Admin, go to Plugins → Add New → Upload Plugin
  3. Upload unlock-mcp-potential.zip and click Install Now
  4. 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.

  1. In WP Admin, go to Users → Add New User
  2. Fill in a username (e.g. ai-editor) and email address
  3. Set the Role to Editor
  4. 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, and moderate_comments). User lookup, plugin management, and sensitive site-audit abilities require Administrator capabilities such as list_users, activate_plugins, or manage_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.

  1. In WP Admin, go to Users → All Users and click the dedicated user you just created
  2. Scroll down to the Application Passwords section
  3. Enter a name for the password (e.g. Claude Code) and click Add New Application Password
  4. 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.

ClientHow to invoke
Claude Code / Claude DesktopAsk Claude: "Call mcp-adapter-discover-abilities"
GitHub Copilot (VS Code / CLI)Ask Copilot in chat: "Use the mcp-adapter-discover-abilities tool"
CodexAsk Codex: "Run mcp-adapter-discover-abilities"
Windsurf / Gemini CLIAsk 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-audit with an Administrator service account — "Run a security audit of my WordPress site"
  • unlock-mcp-potential/site-health-check with an Administrator service account — "Check WordPress site health"
  • unlock-mcp-potential/list-plugins with 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-post and delete-page move content to trash, not permanent deletion. Use restore-post and restore-page to untrash content.
  • Plugin activation and deactivation require activate_plugins; network-wide changes require multisite and manage_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.
Ver o original no GitHub

Bom para

Relacionados