site2app

Site2App provides a stable MCP URL for ChatGPT and other AI clients, plus gateway-hosted demo tools and ChatGPT widgets.
This plugin is a standalone WordPress client for the Site2App gateway. It stores credentials in <code>wp_options</code> only and does not modify your WordPress database schema.
What happens automatically: On activation, one HTTPS request registers your site URL with site2app.live and stores a per-install secret locally. Provisioning, status refresh, the external console link, and billing each require an explicit click in wp-admin.
<h3>External Services</h3>
This plugin connects to third-party services. By installing and activating this plugin, you authorize these connections when the described actions occur.
<h3>site2app.live (Site2App gateway)</h3>
Purpose: Registers your WordPress install, provisions MCP gateway sites and demo tool packs, loads site status and tool lists via API, mints console sessions, and opens the external Site2App console in a new browser tab when you click Open full console.
Data sent:
<ul>
<li>On activation: your public site URL (<code>siteUrl</code>).</li>
<li>On provision (admin click): install ID, install secret, site URL, business category slug, and site name.</li>
<li>On status refresh (admin page load after provision): install ID and install secret (HMAC-signed handshake), then Bearer session token for <code>GET /api/sites/{id}</code> and <code>/tools</code>.</li>
<li>On console open (admin click): install ID and install secret (HMAC-signed handshake); session token passed to site2app.live in a new tab URL.</li>
<li>On Go Live checkout (admin click): gateway site ID and selected package name.</li>
</ul>
When sent: Activation runs once automatically. Provision, status, console handshake, and checkout run only after an administrator clicks the corresponding button or loads the provisioned admin page in wp-admin.
Service provider: <a href="https://site2app.live" rel="nofollow ugc">site2app.live</a>
<a href="https://site2app.live/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://site2app.live/privacy" rel="nofollow ugc">Privacy Policy</a>
<h3>Stripe (payment processing via Site2App gateway)</h3>
Purpose: Optional paid plans (“Go Live”) when you choose to upgrade. The plugin requests a checkout URL from the Site2App gateway; payment is completed on Stripe’s site.
Data sent: Gateway site ID, package tier, and billing cycle are sent to site2app.live, which creates a Stripe Checkout session. Stripe receives payment details directly from you on their hosted checkout page.
When sent: Only when an administrator clicks Activate plan in wp-admin.
Service provider: <a href="https://stripe.com" rel="nofollow ugc">Stripe</a>
<a href="https://stripe.com/legal" rel="nofollow ugc">Terms of Service</a> | <a href="https://stripe.com/privacy" rel="nofollow ugc">Privacy Policy</a>
<h3>site2app.live demo assets (optional)</h3>
Purpose: The included sample REST route (<code>/wp-json/site2app/v1/demo-carousel</code>) may return a placeholder image URL hosted on site2app.live for demo ChatGPT widgets.
Data sent: None from WordPress unless an AI client or browser loads that image URL.
When sent: Only when something requests the demo carousel endpoint or the placeholder image URL.
Service provider: <a href="https://site2app.live" rel="nofollow ugc">site2app.live</a>
<a href="https://site2app.live/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://site2app.live/privacy" rel="nofollow ugc">Privacy Policy</a>
<h3>Privacy</h3>
See the External Services section above. Site2App’s privacy policy: https://site2app.live/privacy

Site2App MCP Gateway

Connect your WordPress site to the Site2App MCP gateway for ChatGPT apps, demo tools, and widgets.

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.

Site2App MCP Gateway vs KaliCart Bridge – AI Agent Catalog for WooCommerce