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.

strifero

<p>StrifeBridge MCP turns your WordPress site into an MCP (Model Context Protocol) endpoint that AI assistants like Claude can connect to directly. Instead of describing a change to an AI and then applying it yourself, you ask and it happens.</p>
<p>Want to add a blog post? Ask Claude. Need to update a menu item? Ask Claude. Wondering which pages are missing SEO metadata? Ask Claude to check and fix them.</p>
<p>StrifeBridge MCP exposes a structured, token-authenticated REST API and MCP server inside your WordPress install. AI assistants that support MCP (Claude.ai, Claude Desktop, Cursor, Windsurf, and any MCP-capable agent framework) can connect to it and perform tasks across your site through natural language.</p>
<h4>What you can do</h4>
<ul>
<li>Create, update, and delete posts, pages, and custom post types</li>
<li>Upload files to the media library and manage attachments</li>
<li>Read and write WordPress options, with a security blacklist for sensitive keys</li>
<li>Manage navigation menus, taxonomy terms, and widgets</li>
<li>List, activate, deactivate, and delete plugins</li>
<li>List users and inspect their roles</li>
<li>Get site info, flush rewrite rules</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Go to Settings and copy your Connector URL (the bearer token is embedded in the path)</li>
<li>Paste the URL into your AI assistant as a custom MCP connector</li>
<li>Ask the assistant to do things on your site</li>
</ol>
<p>No middleware, no third-party relay service. Every request goes from your AI assistant directly to your own WordPress site. You own the endpoint, you own the token, and you can revoke access at any time from Settings.</p>
<h4>Compatible with</h4>
<ul>
<li>Claude.ai (web and desktop) — primary integration</li>
<li>Claude Desktop app</li>
<li>Cursor</li>
<li>Windsurf</li>
<li>Any MCP-capable agent framework</li>
</ul>
<h4>Security</h4>
<p>StrifeBridge MCP was designed with security as a first-class concern:</p>
<ul>
<li>Bearer token authentication on every request, validated with constant-time <code>hash_equals()</code></li>
<li>WordPress secret keys, auth salts, and the plugin’s own token are blacklisted from the options API</li>
<li>Emergency Lockdown button in Settings disables the entire API with one click</li>
<li>Every tool group (posts, media, menus, etc.) can be individually toggled off from Settings</li>
<li>The plugin includes no outbound network calls, no analytics, and no tracking</li>
</ul>
<h4>Compatibility with self-hosted WordPress</h4>
<p>StrifeBridge MCP works on any self-hosted WordPress installation running WordPress 5.6 or higher. WordPress.com and WordPress Multisite are not currently supported.</p>
<h4>Extending StrifeBridge MCP</h4>
<p>StrifeBridge MCP exposes extension hooks that let add-on plugins register additional MCP tools without modifying the core plugin. Developers can hook into <code>sbmcp_register_rest_routes</code>, <code>sbmcp_mcp_tools</code>, <code>sbmcp_mcp_tool_call</code>, <code>sbmcp_tool_groups</code>, and <code>sbmcp_admin_after_settings</code> to add routes, tools, admin UI, and tool groups. This is how separately distributed add-ons extend the plugin with features like file editing, database queries, and user management.</p>


StrifeBridge MCP

Connect your WordPress site to Claude and other AI assistants through the Model Context Protocol. Manage posts, media, menus, and more in plain Englis …

Airano MCP Bridge vs StrifeBridge MCP