airano

Airano MCP Bridge 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:
<ul>
<li>SEO meta routes — read and write Rank Math SEO and Yoast SEO metadata for posts, pages, and WooCommerce products.</li>
<li>Media upload helper routes — 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>Capability probe — reports the effective PHP + WordPress upload limits so MCP Hub can pick the right upload path automatically.</li>
</ul>
Features:
<ul>
<li>Rank Math SEO Support — Full access to all Rank Math meta fields</li>
<li>Yoast SEO Support — Full access to all Yoast SEO meta fields</li>
<li>WooCommerce Compatible — Works with product post types</li>
<li>MCP Hub media pipeline — bypasses <code>upload_max_filesize</code> for AI-agent uploads</li>
<li>Secure — Requires WordPress Application Password + capability checks on every route</li>
<li>Auto-Detection — Automatically detects active SEO plugin and advertises capabilities</li>
<li>Zero Configuration — Works out of the box after activation</li>
</ul>
REST API Endpoints:
SEO meta (namespace <code>airano-mcp-bridge/v1</code>)
<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>
MCP Bridge helpers (namespace <code>airano-mcp/v1</code>, added in 2.0.0)
<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>
Designed for <a href="https://mcp.palebluedot.live" rel="nofollow ugc">MCP Hub</a> — 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>.

Airano MCP Bridge

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

Giuseppe Socci

KaliCart Bridge makes your WooCommerce product catalog computable: it exposes a structured, normalized REST API and an MCP server that AI shopping agents and assistants — such as ChatGPT, Claude, Gemini, Perplexity and any MCP-capable client — can read and act on directly. No LLM runs on your server; the plugin only turns your existing catalog into clean, computable data.
Documentation: https://bridge.kalicart.com/docs/
What it does:
<ul>
<li>Exposes a <code>/discovery</code> endpoint — the single entry point any agent needs to understand your catalog</li>
<li>Provides <code>/catalog/search</code>, <code>/catalog/products</code>, <code>/catalog/product/{id}</code>, <code>/catalog/categories</code> endpoints</li>
<li>Exposes a Model Context Protocol (MCP) server at <code>/wp-json/kalicart/v1/mcp</code> (JSON-RPC 2.0) so MCP-capable agents can call the catalog as tools — same data as the REST endpoints, no API key</li>
<li>Computationally normalizes product data: prices (min/max for variables, sale %, discount), stock, gender inference, color family mapping, size type detection</li>
<li>Exposes WooCommerce shipping-zone policy for agent reasoning; checkout remains the final authority for exact destination/cart shipping cost</li>
<li>Exposes active product/category-compatible coupons as conditional checkout savings; coupons never replace the catalog price</li>
<li>Category tree nodes include direct <code>products_url</code> and <code>search_url_template</code> fields so agents can navigate without constructing URLs manually</li>
<li>Dashboard issue cards and suggestions link to filtered product lists for direct remediation</li>
<li>Uses your merchant taxonomy — no global remapping, products stay in your WooCommerce categories</li>
<li>Injects a <code><link rel="kalicart-agent"></code> in your site <code><head></code> for agent auto-discovery</li>
<li>Adds an “agent ready” badge in the footer</li>
<li>Injects <code>Allow: /wp-json/kalicart/</code> in <code>robots.txt</code></li>
<li>Generates <code>/kalicart-sitemap.xml</code> linked from the WP sitemap index</li>
<li>Shows a catalog health dashboard in wp-admin with quarantine tracking and improvement suggestions</li>
</ul>
What it does NOT do:
<ul>
<li>No LLM calls</li>
<li>No cloud dependency for core functionality</li>
<li>No data sent anywhere outside your server by default — the only optional exception is the Federated Catalog feature (see “External services” below), which you turn on explicitly</li>
<li>No API key required for public endpoints</li>
</ul>
Normalization engine:
<ul>
<li>Price: regular, sale, current, discount %, currency — variable products get min/max ranges</li>
<li>Stock: status, in_stock bool, quantity if managed, backorder policy</li>
<li>Gender: inferred from <code>pa_gender</code> attribute, category paths, tags, product name (multilingual keywords: IT/EN/FR/DE/ES)</li>
<li>Color: mapped to 13 color families via keyword matching on <code>pa_color</code>/<code>pa_colore</code> and product metadata</li>
<li>Size: detected from <code>pa_size</code>/<code>pa_taglia</code>, type auto-detected (clothing S/M/L, numeric EU, shoes EU half-sizes)</li>
</ul>
Catalog health / quarantine:
Products are scored 0–100 based on: title quality, description length, category assignment, price validity, image presence and SKU presence. Quarantine is reserved for blocking computability issues: ambiguous/too-short titles, missing or very short descriptions, missing real categories, and missing or zero prices. Missing images and SKUs remain clickable improvement suggestions but do not quarantine products.
Checkout sessions (optional):
When enabled in WP Admin → KaliCart → Settings, agents can create checkout sessions containing one or more products. Each session returns cart_url (lands on WooCommerce cart for review) and checkout_url (goes directly to checkout). Sessions expire after 30 minutes. No OAuth, no PII, no payment on the agent side.
Model Context Protocol (MCP) endpoint:
The same read-only catalog is also exposed as an MCP server at <code>/wp-json/kalicart/v1/mcp</code> (JSON-RPC 2.0 over HTTP POST). MCP-capable agents and assistants connect to it and call the catalog as tools: <code>search_products</code>, <code>list_products</code>, <code>get_product</code>, <code>list_categories</code>, <code>get_meta</code>. It is read-only and needs no authentication, exactly like the public REST endpoints — it adds a second transport, not new data. No LLM, no external calls. Checkout and payment are never exposed over MCP.
<h3>External services</h3>
This plugin works fully standalone. It connects to one external service only if you explicitly opt in by activating the optional Federated Catalog feature in WP Admin → KaliCart Bridge.
Service: KaliCart Global (https://dashboard.kalicart.com)
When data is sent: Only when an administrator clicks “Activate Federated Catalog” (and, symmetrically, “Revoke consent”). Nothing is sent automatically, on activation, or in the background. With the feature off, the plugin makes no external requests.
What is sent: A single value — your site’s public URL (e.g. https://yourstore.com). On revoke, the same URL is sent to withdraw. No customer data, orders, personal data, credentials, or API keys are ever transmitted.
What the service does: The URL tells KaliCart Global your store wishes to be discovered. KaliCart Global then periodically reads your already-public catalog (the same data exposed by the Bridge’s public REST endpoints) and includes it in federated agent search. It only reads; it never writes to your store. Revoking stops this and parks your catalog.
Privacy notice: https://bridge.kalicart.com/privacy/ 
Terms / documentation: https://bridge.kalicart.com/docs/

KaliCart Bridge – AI Agent Catalog for WooCommerce

Makes your WooCommerce catalog computable and readable by AI agents and MCP clients like ChatGPT, Claude and Gemini. No API key.

Airano MCP Bridge vs KaliCart Bridge – AI Agent Catalog for WooCommerce