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.

strifero

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.
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.
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.
<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>
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.
<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>
StrifeBridge MCP was designed with security as a first-class concern:
<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>
StrifeBridge MCP works on any self-hosted WordPress installation running WordPress 5.6 or higher. WordPress.com and WordPress Multisite are not currently supported.
<h4>Extending StrifeBridge MCP</h4>
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.

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 …

KaliCart Bridge – AI Agent Catalog for WooCommerce vs StrifeBridge MCP