Stefano Lissa

<p>The MCP Servers plugin enables WordPress to expose “abilities” – standardized functions that AI agents (such as Claude, Mistral, or ChatGPT) can invoke.</p>
<p>These abilities allow plugins and themes to describe their functionalities and required parameters in a structured way, facilitating seamless interaction with AI agents via the MCP (Model Context Protocol).</p>
<h4>Use Cases</h4>
<ul>
<li>A newsletter plugin can expose abilities to manage subscribers or newsletters.</li>
<li>A form manager can provide abilities to handle forms or process submissions.</li>
<li>No limits: Any functionality can be exposed and utilized by AI agents.</li>
</ul>
<h4>Creating a server</h4>
<p>Go to the “Servers” page and add a server. By default, a new MCP server does not expose any abilities. You can:</p>
<ul>
<li>Select one or more ability categories.</li>
<li>Choose individual abilities to expose.</li>
</ul>
<h4>Best Practices</h4>
<ul>
<li>Avoid exposing all abilities: This can overwhelm AI agents and lead to overlapping functionalities.</li>
<li>Limit abilities to those necessary for your current workflow.</li>
<li>Create multiple MCP servers to enable only the tools required for specific tasks on the agent side.</li>
</ul>
<h4>Connecting to a server</h4>
<p>AI agents can connect to your MCP server(s) in several ways. The simplest method is:</p>
<ul>
<li>Create an administrator user named “mcp”.</li>
<li>Generate an application password for this user in the WordPress dashboard.</li>
<li>Use Basic Authentication with the mcp username and the application password to set up the connection from the AI agent.</li>
</ul>
<h4>Note on Authentication</h4>
<p>Not all AI agents support Basic Authentication. For example, Claude requires OAuth2.</p>
<p>To enable OAuth2, install a compatible plugin (e.g., WP OAuth Server).</p>
<h4>References</h4>
<ul>
<li>The <a href="https://www.satollo.net/plugins/mcpservers" rel="nofollow ugc">MCP Servers official page</a></li>
<li>The <a href="https://github.com/wordpress/mcp-adapter" rel="nofollow ugc">MCP Adapater library/plugin</a></li>
<li>Introduction to the <a href="https://make.wordpress.org/ai/2025/07/17/ai-building-blocks/" rel="nofollow ugc">WP AI building blocks</a></li>
<li>The <a href="https://make.wordpress.org/ai/2025/07/17/ai-experiments-plugin/" rel="nofollow ugc">AI Experiments plugin</a></li>
<li>The <a href="https://www.satollo.net/plugins/monitor" rel="nofollow ugc">Monitor plugin</a></li>
</ul>
<p>The AI Experiments plugin contains the “Ability explorer” a very useful tool.</p>
<h4>Tech details</h4>
<p>The plugin uses the WP MCP Adapter library or the MCP Adapter plugin (if installed), with priority given to the latter.</p>
<p>Once the Adapter plugin is officially available, it will be added as a dependency, and the PHP library will be removed.</p>
<h4>Warning</h4>
<p>Abilities are registered an implemented by plugins and themes: check carefully what they do before exposing!</p>
<p>And be aware that permission checks are up to the single ability.</p>


Satollo MCP Servers

Configure and publish MCP servers to expose abiltities to AI agents

airano

<p><strong>Airano MCP Bridge</strong> is the official companion plugin for <a href="https://mcp.palebluedot.live" rel="nofollow ugc">MCP Hub</a> (<a href="https://github.com/airano-ir/mcphub" rel="nofollow ugc">source</a>) — the AI-native management hub for WordPress, WooCommerce, and self-hosted services. It extends the WordPress REST API with dedicated routes that AI agents (Claude, ChatGPT, Cursor, VS Code Copilot) and the MCP Hub server rely on:</p>
<ul>
<li><strong>SEO meta routes</strong> — read and write Rank Math SEO and Yoast SEO metadata for posts, pages, and WooCommerce products.</li>
<li><strong>Media upload helper routes</strong> — accept raw-binary uploads via <code>php://input</code>, which bypasses the <code>upload_max_filesize</code> PHP limit (still bounded by <code>post_max_size</code>). Unlocks reliable hero-image and large-asset uploads for AI-agent workflows.</li>
<li><strong>Capability probe</strong> — reports the effective PHP + WordPress upload limits so MCP Hub can pick the right upload path automatically.</li>
</ul>
<p><strong>Features:</strong></p>
<ul>
<li><strong>Rank Math SEO Support</strong> — Full access to all Rank Math meta fields</li>
<li><strong>Yoast SEO Support</strong> — Full access to all Yoast SEO meta fields</li>
<li><strong>WooCommerce Compatible</strong> — Works with product post types</li>
<li><strong>MCP Hub media pipeline</strong> — bypasses <code>upload_max_filesize</code> for AI-agent uploads</li>
<li><strong>Secure</strong> — Requires WordPress Application Password + capability checks on every route</li>
<li><strong>Auto-Detection</strong> — Automatically detects active SEO plugin and advertises capabilities</li>
<li><strong>Zero Configuration</strong> — Works out of the box after activation</li>
</ul>
<p><strong>REST API Endpoints:</strong></p>
<p><em>SEO meta (namespace <code>airano-mcp-bridge/v1</code>)</em></p>
<ul>
<li><code>GET/POST /wp-json/airano-mcp-bridge/v1/posts/{id}/seo</code> — Post SEO data</li>
<li><code>GET/POST /wp-json/airano-mcp-bridge/v1/pages/{id}/seo</code> — Page SEO data</li>
<li><code>GET/POST /wp-json/airano-mcp-bridge/v1/products/{id}/seo</code> — Product SEO data (WooCommerce)</li>
<li><code>GET /wp-json/airano-mcp-bridge/v1/status</code> — Plugin status + active SEO plugins</li>
</ul>
<p><em>MCP Bridge helpers (namespace <code>airano-mcp/v1</code>, added in 2.0.0)</em></p>
<ul>
<li><code>GET /wp-json/airano-mcp/v1/upload-limits</code> — Effective PHP + WP upload limits</li>
<li><code>POST /wp-json/airano-mcp/v1/upload-chunk</code> — Raw-body media upload (bypasses <code>upload_max_filesize</code>)</li>
<li><code>GET /wp-json/airano-mcp/v1/capabilities</code> — Effective capabilities + feature flags + available routes (added in 2.1.0)</li>
<li><code>POST /wp-json/airano-mcp/v1/bulk-meta</code> — Batch post/product meta writes in a single HTTP round-trip (added in 2.2.0)</li>
<li><code>GET /wp-json/airano-mcp/v1/export</code> — Structured JSON export: posts, pages, products + media + terms + meta, with post_type/status/since/limit/offset paging (added in 2.3.0)</li>
<li><code>POST /wp-json/airano-mcp/v1/cache-purge</code> — Auto-detects active cache plugins (LiteSpeed, WP Rocket, W3TC, Super Cache, Fastest Cache, SG Optimizer) and invokes their purge API; always flushes object cache (added in 2.4.0)</li>
<li><code>POST /wp-json/airano-mcp/v1/transient-flush</code> — Native transient cleanup with scope=expired/all/pattern (glob); optional site-transient handling on multisite (added in 2.5.0)</li>
<li><code>GET /wp-json/airano-mcp/v1/site-health</code> — Unified site-health snapshot: PHP/MySQL/WP versions, extensions, disk free, active plugins + theme, writability checks (added in 2.6.0)</li>
<li><code>GET|POST|DELETE /wp-json/airano-mcp/v1/audit-hook</code> — Configure + query a webhook that forwards WordPress action events to MCP Hub (HMAC-SHA256 signed, non-blocking) (added in 2.7.0)</li>
<li><code>POST /wp-json/airano-mcp/v1/regenerate-thumbnails</code> — Regenerate attachment sub-sizes via <code>wp_generate_attachment_metadata</code> for a list of IDs or in paged batch mode (added in 2.8.0)</li>
<li><code>POST /wp-json/airano-mcp/v1/upload-and-attach</code> — Raw-body upload + metadata + attach-to-post + set-featured in a single REST call (added in 2.9.0). Query params: <code>attach_to_post</code>, <code>set_featured</code>, <code>title</code>, <code>alt_text</code>, <code>caption</code>, <code>description</code>. Permission: <code>upload_files</code> + <code>edit_post</code> on the target post.</li>
<li><code>POST /wp-json/airano-mcp/v1/opcache-reset</code> — Reset PHP OPcache after a theme/plugin deploy (added in 2.11.0). Permission: <code>manage_options</code>.</li>
<li><code>GET /wp-json/airano-mcp/v1/transients</code> — Read-only inventory of transient keys + expirations; values intentionally never returned (added in 2.11.0). Capped at 500 per call. Permission: <code>manage_options</code>.</li>
<li><code>POST /wp-json/airano-mcp/v1/term-update</code> — Mutate a taxonomy term via <code>wp_update_term</code> (added in 2.11.0). Accepts <code>taxonomy</code> (canonical name or REST base), <code>term_id</code>, and any of <code>name</code>/<code>slug</code>/<code>description</code>/<code>parent</code>. Permission: the taxonomy’s own <code>edit_terms</code> capability, enforced at the route gate.</li>
<li><code>POST /wp-json/airano-mcp/v1/cache-purge</code> — As of 2.11.0 accepts an optional <code>scope</code> body parameter (<code>all</code> / <code>page</code> / <code>object</code>, default <code>all</code>).</li>
</ul>
<p><strong>Designed for <a href="https://mcp.palebluedot.live" rel="nofollow ugc">MCP Hub</a></strong> — the AI-native management hub for WordPress and self-hosted services. <a href="https://mcp.palebluedot.live" rel="nofollow ugc">Try the live platform</a> · <a href="https://github.com/airano-ir/mcphub" rel="nofollow ugc">Source on GitHub</a>.</p>


Airano MCP Bridge

Companion plugin for MCP Hub. REST API routes for SEO meta and raw-binary media uploads that bypass upload_max_filesize.

Satollo MCP Servers vs Airano MCP Bridge