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.

dudaster

AICOM – AI Commander connects your WordPress site to any AI agent via MCP (Model Context Protocol) or OpenAPI. Use your existing AI subscription — Claude Code, OpenAI Codex, ChatGPT Custom GPTs, Copilot Studio, Dify, n8n, OpenClaw, Celine, Goose, or any MCP-compatible client — to manage content, build pages, run audits, and automate repetitive tasks, all without leaving your AI interface.
No more copy-pasting between your AI assistant and the WordPress dashboard. Describe what you want, and your agent does it — safely, with a full record of every action.
<h4>Content Management</h4>
Create, update, and publish posts, pages, and custom post types directly from your AI agent. Build and duplicate Elementor pages, manage menus, upload media, update taxonomies, and handle bulk SEO fields including Yoast SEO meta, titles, and social previews — all in a single conversation. What used to take hours of dashboard work can be delegated to your AI in minutes.
<h4>Safety You Control</h4>
AICOM puts you in charge at every level:
<ul>
<li>Scope-based API keys — each key grants access only to the operations you explicitly allow. One key for read-only content review, another for full publishing access.</li>
<li>Soft Lock / Hard Lock — freeze all write operations (Soft) or block everything except public tools (Hard) with one click from the admin bar or Safety page.</li>
<li>Working Hours Schedule — automatically apply Soft or Hard Lock outside your configured working hours and days. Agents can’t make changes at night or on weekends unless you explicitly override it.</li>
<li>Dry-run mode — test any operation before it runs. See exactly what would change without touching live data.</li>
<li>Confirm flag — destructive operations require an explicit <code>"confirm": true</code> parameter. Accidental deletions are prevented by design.</li>
</ul>
<h4>Backup & Restore</h4>
Before every significant change, your agent can snapshot the current state of a post or term. If something goes wrong, restore the exact previous version in one call. Backups are stored in the database, organised by session, and can be cleaned up automatically based on age or total size.
<h4>Full Audit Trail</h4>
Every request is logged: timestamp, remote IP, API key label, tool used, parameters, result, and response time. Logs are grouped into named sessions — when an agent opens a session, all its actions are recorded together so you can review, replay, or undo an entire workflow at once. The Audit Logs page includes a session activity chart and a direct Restore button for each session.
<h4>Accessibility Audits — New in v3.2.0</h4>
AICOM now includes a dedicated Accessibility module so your AI agent can audit and fix WCAG issues across your entire site — no external tools or services required:
<ul>
<li>Site report — instantly see how many images are missing alt text across your entire media library, with a ranked preview of the top offenders and a percentage score.</li>
<li>Post audit — scan any post or page for heading hierarchy errors (missing H1, skipped heading levels), images without alt text, and links with non-descriptive anchor text (“click here”, “read more”). Each issue is rated by severity and the post receives an overall accessibility score from 0 to 100.</li>
<li>Fix in place — set alt text on any media library image in one call. Pass an empty string to correctly mark it as decorative (<code>aria-hidden</code>). Full dry-run support so you can preview changes before saving.</li>
<li>Screenshot before & after — combine AICOM’s audit tools with your AI agent’s browser capabilities to capture a visual record of the page before and after remediation.</li>
</ul>
A typical AI-driven accessibility workflow: run the site report, get the list of problem images, let the agent analyse each image visually and write descriptive alt text, apply the fixes — then run the audit again to confirm the score improved. All in one session, with a full audit trail.
<h4>Supported Modules</h4>
<ul>
<li>WordPress Core — posts, pages, custom post types, terms, meta, options, menus, plugins</li>
<li>Media — upload, update, delete media; direct file system access</li>
<li>Users & Roles — create, update, manage users and role assignments</li>
<li>Backup — per-post and per-term snapshots, session-based restore</li>
<li>Sessions — named audit sessions with grouped action history</li>
<li>Accessibility — site-wide alt text audit, post-level WCAG check, alt text fixes</li>
<li>WooCommerce (optional) — products, categories, settings</li>
<li>Elementor (optional) — page creation from template, widget inspection, theme builder conditions</li>
<li>Polylang (optional) — translations, language assignment, string management</li>
<li>Yoast SEO (optional) — read and write SEO titles, meta descriptions, Open Graph and Twitter card fields; bulk audit across all posts in one session</li>
<li>Clautron (optional) — blueprint management, capability catalog, event analytics</li>
<li>ECS (optional) — Ele Custom Skin color schemes, font schemes, custom looks</li>
</ul>
<h4>Who is this for?</h4>
<ul>
<li>Content teams using Claude, ChatGPT, or any AI assistant who want it to publish and update WordPress content directly</li>
<li>Agencies managing multiple client sites and wanting AI-assisted workflows with a full paper trail</li>
<li>Developers building AI-powered WordPress tools or automation pipelines</li>
<li>Accessibility specialists who want to audit and remediate WCAG issues at scale with AI assistance</li>
<li>Claude Code users — point AICOM as an MCP server from your terminal and control WordPress alongside your code</li>
<li>OpenAI Codex users — connect Codex to your site via AICOM’s MCP endpoint and let it manage content as part of your dev workflow</li>
<li>ChatGPT, Copilot Studio, Dify, n8n users — import the OpenAPI schema URL into any OpenAPI-compatible client; all tools are discovered automatically with Bearer auth</li>
<li>OpenClaw / Celine / Goose users — native MCP connector, works out of the box</li>
</ul>
<h4>How it works</h4>
AICOM exposes a secure HTTP endpoint on your WordPress site. Your AI agent sends structured MCP requests, AICOM authenticates the request, checks scopes and lock state, executes the operation, logs it, and returns a structured response.
<pre><code>AI Agent → AICOM Endpoint → WordPress
</code></pre>
<h4>API Key Scopes</h4>
Each API key is granted specific scopes — you control exactly what each AI agent can and cannot do:
<pre><code>read.wp, `write.wp.posts`, `manage.taxonomies`, `manage.meta`, `manage.wordpress.settings`, `manage.media`, `manage.files`, `manage.users`, `manage.plugins`, `manage.backups`, `manage.a11y`, `manage.woocommerce.products`, `manage.woocommerce.settings`, `manage.elementor`, `manage.polylang`, `manage.yoast`, `manage.clautron`
</code></pre>
<h4>Endpoint</h4>
REST API: 
 POST /wp-json/aicom/v1/mcp
Fallback (no mod_rewrite required): 
 POST /?aicom=1
Health check: 
 GET /?aicom=1
<h4>Authentication</h4>
<pre><code>Authorization: Bearer aicom_XXXXXXXX_<secret>
</code></pre>
or:
<pre><code>X-API-Key: aicom_XXXXXXXX_<secret>
</code></pre>
<h4>MCP Request Example</h4>
<pre><code>{"jsonrpc":"2.0","method":"tools/call","params":{"name":"wp.posts.list","arguments":{"post_type":"post","posts_per_page":10}},"id":1}
</code></pre>

AICOM – AI Commander

Use your AI subscription to manage WordPress: create Elementor pages, update content, automate tasks, and stay fully in control.

KaliCart Bridge – AI Agent Catalog for WooCommerce vs AICOM – AI Commander