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.

videowhisper

VideoWhisper Site Manager lets you manage WordPress posts and pages through external AI assistants such as ChatGPT (Custom GPT + Actions), Claude (MCP: web, desktop, mobile, CLI), and Codex (MCP). It exposes authenticated WordPress endpoints and setup guidance while you keep using your own AI account and subscription.
It provides:
<ul>
<li>A secure REST layer for content operations (list, read, create, update, revert, reset)</li>
<li>An MCP (Model Context Protocol) endpoint for Claude.ai, Claude Desktop, Claude CLI, Claude mobile apps, and Codex MCP clients</li>
<li>A generated OpenAPI schema URL for GPT Actions import</li>
<li>Guided onboarding with copy/paste values for ChatGPT Builder, Claude connector setup, and Codex MCP setup</li>
<li>Turnkey OAuth onboarding for shared GPT / shared MCP workflows through a compatible Relay & OAuth Server</li>
<li>WordPress Application Password onboarding for direct site-owned integrations</li>
<li>Frontend user connection shortcode support for connected account workflows</li>
<li>Safety controls: HTTPS enforcement, draft-first behavior, publish gating, read/write rate limiting, write quotas, IP allowlists, audit logs</li>
<li>Extension points through WordPress hooks for custom authentication, tools, settings, content types, and admin UI additions</li>
</ul>
The plugin does not call OpenAI, Anthropic, or any AI provider directly. Your WordPress site exposes authenticated endpoints and setup guidance. You connect it to ChatGPT, Claude, or Codex yourself with your own account and subscription.
<h4>Ideal for</h4>
<ul>
<li>Site owners who want to draft, edit, or review WordPress content by chat</li>
<li>Teams using a dedicated WordPress user (recommended: Editor) for AI-assisted publishing workflows</li>
<li>Mobile workflows: configure on desktop, use the GPT or Claude connector on phone/tablet</li>
<li>Developer workflows where Codex can use MCP tools to inspect and update WordPress content</li>
</ul>
<h4>Supported Authentication</h4>
The onboarding flow recommends using one authentication option for clarity, but development and migration setups can enable more than one.
<ul>
<li>Turnkey OAuth – recommended for most sites. Users connect through a compatible Relay & OAuth Server and can operate one or more connected sites from the same shared GPT or MCP connector.</li>
<li>Application Passwords – direct WordPress authentication over HTTPS using WordPress core Application Passwords. Best for admin-owned custom GPT/MCP setups where credentials are managed by the site operator.</li>
<li>Extension-provided authentication – developers can add custom OAuth, token validation, alternate connector metadata, or other authentication flows with the hooks listed below.</li>
</ul>
<h4>Connecting ChatGPT</h4>
<ol>
<li>Install and activate VideoWhisper Site Manager.</li>
<li>Open VideoWhisper Site Manager > Onboarding.</li>
<li>Create (or link) a dedicated WordPress user (recommended role: Editor).</li>
<li>Choose Turnkey OAuth for a shared GPT workflow, or create an Application Password from the onboarding page for a direct site-owned GPT.</li>
<li>In ChatGPT Builder (desktop), create a Custom GPT and import the plugin OpenAPI schema URL.</li>
<li>Use the provided copy/paste values for Configure, Actions, authentication, and privacy policy fields.</li>
<li>Test on desktop, then use the same GPT on mobile.</li>
</ol>
<h4>Connecting Claude (MCP)</h4>
The free plugin includes an MCP endpoint at <code>/wp-json/videowhisper-site-manager/v1/mcp</code>.
Claude.ai (web):
<ol>
<li>Go to <code>claude.ai/customize/connectors</code>.</li>
<li>Click the + button in the Connectors sidebar → Add custom connector.</li>
<li>Set a name and paste the MCP endpoint URL.</li>
<li>Authorize via Turnkey OAuth when connected to a compatible Relay & OAuth Server, or use an Application Password for direct setup.</li>
<li>The connector also works in the Claude mobile apps (iOS and Android) and desktop once authorized.</li>
</ol>
Claude CLI:
claude mcp add –transport http “YourSiteName” “https://yoursite.com/wp-json/videowhisper-site-manager/v1/mcp”
Automatic OAuth authorization requires a compatible Relay & OAuth Server. Without that connection, use WordPress Application Passwords over HTTPS.
<h4>Connecting Codex (MCP)</h4>
The onboarding flow includes Codex setup values for both direct and Turnkey MCP architectures. Codex can connect to the same Streamable HTTP MCP endpoint at <code>/wp-json/videowhisper-site-manager/v1/mcp</code>.
<ol>
<li>Open VideoWhisper Site Manager > Onboarding and enable Codex in the AI Tools selection step.</li>
<li>Choose Turnkey OAuth for shared relay access, or Application Passwords for direct site-owned MCP access.</li>
<li>Copy the generated Codex <code>config.toml</code> block or OAuth login command from the Codex onboarding tab.</li>
<li>Restart or reload Codex MCP settings, then use <code>/mcp</code> in Codex to confirm the WordPress MCP server is active.</li>
</ol>
<h3>Features</h3>
<ul>
<li>MCP endpoint for Claude.ai, Claude Desktop, Claude CLI, Claude mobile apps, and Codex — implements MCP Streamable HTTP transport (protocol 2025-03-26)</li>
<li>ChatGPT / GPT Actions integration via generated OpenAPI schema URL (<code>/wp-json/videowhisper-site-manager/v1/openapi</code>)</li>
<li>Dynamic agent guide at <code>/wp-json/videowhisper-site-manager/v1/agent-guide</code> with Markdown by default and JSON via <code>?format=json</code>; MCP also exposes guide resources for MCP-aware clients</li>
<li>Shared AI action registry keeps MCP tools and OpenAPI schemas aligned for ChatGPT, Claude, and Codex integrations; extra OpenAPI actions are grouped by module with an <code>action</code> subaction field to stay under GPT operation limits</li>
<li>GPT Actions onboarding aligned with current auth UI, including Application Password and Turnkey OAuth setup paths</li>
<li>One-click Application Password creation for the dedicated operator user (plaintext shown once, not stored long-term)</li>
<li>Guided onboarding with copyable values for:
<ul>
<li>GPT Name, Description, Instructions, Conversation Starters</li>
<li>MCP endpoint URL, Claude connector setup instructions (Claude.ai, Desktop, CLI), and Codex MCP configuration snippets</li>
<li>Action authentication values, Schema URL, Privacy Policy URL</li>
<li><code>curl</code> examples and credential samples</li>
</ul>
</li>
<li>Authentication options:
<ul>
<li><code>Turnkey OAuth</code> for shared GPT / shared MCP workflows through a compatible Relay & OAuth Server</li>
<li><code>Application Passwords</code> for direct site-owned admin integrations</li>
<li>hook-based extension points for additional authentication methods</li>
</ul>
</li>
<li>REST endpoints for listing, reading, creating, and updating WordPress posts/pages</li>
<li>Context endpoint for site and content context used by MCP tools</li>
<li>Optional read-only Live Support Tickets CRM integration for authenticated users to list their own conversations and retrieve messages through OpenAPI/MCP tools</li>
<li>Content revert/reset helpers backed by revision snapshots</li>
<li><code>dry_run</code> support for safer create/update previews before writing</li>
<li>Draft-first workflow and optional publish permission (<code>Allow publish</code>)</li>
<li>HTTPS enforcement for plugin endpoints by default (with dev-only HTTP override setting)</li>
<li>Per-user rate limiting with separate defaults for read traffic (10/minute), write actions (5/minute), and hourly write quotas (30/hour)</li>
<li>FansPaysite support for frontend shortcode styling, dark/light mode, and Pro menu icon fields when the FansPaysite theme is active</li>
<li>IP allowlists for Application Password and Turnkey OAuth traffic</li>
<li>External OAuth URL hardening (HTTPS-only with external-host validation)</li>
<li>Configurable short cache TTL for external bearer-token validation (default: 10s)</li>
<li>Categories and tags support</li>
<li>Generic SEO metadata fields (plugin-owned keys)</li>
<li>Audit logging endpoint for administrators</li>
<li>Settings endpoint for administrators</li>
<li>Public protected resource metadata for OAuth-aware clients</li>
<li>Provider Terms of Use and Privacy Policy links when supplied by connected services</li>
<li>User connection shortcode (<code>[vwsm_user_connect]</code>) for account-based connection flows</li>
<li>Admin notices and onboarding reminders for incomplete setup</li>
<li>Recommended GPT/Claude/Codex capabilities guidance</li>
</ul>
<h3>Current AI Actions and Tools</h3>
The shared registry exposes the same capabilities to ChatGPT Actions, Claude MCP, and Codex MCP when settings and user permissions allow them. OpenAPI may group extra actions by module; MCP lists the individual tool names.
Core tools: <code>get_site_context</code>, <code>list_content</code>, <code>get_content</code>, <code>get_logs</code>, <code>create_content</code>, <code>update_content</code>.
Conditional core tools: <code>revert_action</code>, <code>reset_action</code> when log state tools are enabled.
Plugin integration tools: <code>get_site_context</code> includes brief permission-aware <code>available_integrations</code> metadata, while <code>plugins_list</code> lists compatible plugins, agent instructions, whitelisted option documentation, and plugin-specific tools visible to the authenticated user. Site Manager Pro adds <code>plugin_list_options</code>, <code>plugin_get_options</code>, and <code>plugin_update_option</code> for admin-only whitelisted option configuration. Other plugins can register tools with <code>vwsm_ai_plugin_integrations</code>; Site Manager exposes them automatically through MCP, the dynamic agent guide, and grouped OpenAPI <code>/actions/{module}</code> paths.
Live Support Tickets read-only tools when CRM access is enabled: <code>crm_list_my_conversations</code>, <code>crm_get_my_conversation_messages</code>.
Agent documentation: <code>/wp-json/videowhisper-site-manager/v1/agent-guide</code>, <code>/wp-json/videowhisper-site-manager/v1/agent-guide?surface=mcp</code>, <code>/wp-json/videowhisper-site-manager/v1/agent-guide?surface=actions</code>, and <code>/wp-json/videowhisper-site-manager/v1/agent-guide?format=json</code>.
<h3>Extension Hooks</h3>
Developers can extend this plugin without editing core files. Common hooks include:
<ol>
<li>Settings and admin UI: <code>vwsm_settings_defaults</code>, <code>vwsm_settings_normalized</code>, <code>vwsm_admin_settings_save</code>, <code>vwsm_rest_settings_payload</code>, <code>vwsm_settings_tab_label</code>, <code>vwsm_settings_form_publishing_rows</code>, <code>vwsm_settings_form_security_rows</code>, <code>vwsm_settings_form_rate_limits_rows</code>, <code>vwsm_settings_form_logs_revisions_rows</code>, <code>vwsm_settings_form_turnkey_oauth_rows</code>, <code>vwsm_settings_form_authentication_rows</code>, <code>vwsm_settings_form_application_passwords_rows</code>, <code>vwsm_settings_form_content_rows</code>, <code>vwsm_settings_form_admin_rows</code>, <code>vwsm_settings_form_attachments_rows</code>, <code>vwsm_settings_form_fomantic_rows</code>, <code>vwsm_settings_form_after_core_rows</code>, <code>vwsm_auth_methods_section</code>.</li>
<li>Authentication and OAuth metadata: <code>vwsm_oauth_server_url</code>, <code>vwsm_authorization_server_url</code>, <code>vwsm_rest_401_headers</code>, <code>vwsm_external_oauth_onboarding_urls</code>, <code>vwsm_onboarding_oauth_tab_content</code>, <code>vwsm_handle_external_register_gpt</code>.</li>
<li>OpenAPI, MCP, and tools: <code>vwsm_ai_actions</code>, <code>vwsm_ai_plugin_integrations</code>, <code>vwsm_ai_plugin_option_integrations</code>, <code>vwsm_ai_plugin_action_dispatch</code>, <code>vwsm_ai_action_native_openapi_tools</code>, <code>vwsm_mcp_server_name</code>, <code>vwsm_mcp_extra_tools</code>, <code>vwsm_mcp_dispatch_tool</code>, <code>vwsm_mcp_site_context</code>, <code>vwsm_openapi_components</code>, <code>vwsm_openapi_document</code>, <code>vwsm_write_rate_limit_mcp_tools</code>.</li>
<li>Content and sanitization: <code>vwsm_allowed_content_types</code>, <code>vwsm_revision_limit</code>, <code>vwsm_revision_gradient</code>, <code>vwsm_supported_extra_allowed_html_tags</code>, <code>vwsm_allow_extra_allowed_html_tags</code>.</li>
<li>User connection workflows: <code>vwsm_user_connect_handle_post</code>, <code>vwsm_user_connect_after_sections</code>, <code>vwsm_user_connect_tools_data</code>, <code>vwsm_user_connect_gpt_url</code>.</li>
<li>Operator and environment behavior: <code>vwsm_default_operator_username</code>, <code>vwsm_use_current_user_mode</code>.</li>
</ol>
<h3>Disclaimer</h3>
This plugin provides infrastructure for operating a WordPress site with external AI chatbots and agents. The site owner is solely responsible for the actions enabled through this functionality, including content created or changed by AI tools, credentials and access tokens, backups, privacy compliance, and any publishing or policy consequences.
AI-generated content can be inaccurate, defamatory, plagiarized, non-compliant, or otherwise unsuitable for publication. Review AI output and tool activity before publishing. Keep publishing disabled unless you fully understand and accept the risk.
Use HTTPS, protect Application Passwords and OAuth credentials, restrict access where possible, monitor logs, and maintain independent backups. Use at your own risk.
<h3>Privacy</h3>
This plugin stores the following data on your WordPress site:
<ul>
<li>Plugin settings in WordPress options (for example: publish, rate limit, HTTPS, IP allowlist, authentication, and provider URL settings)</li>
<li>Audit log entries in a custom database table (<code>*_vwsm_audit_logs</code>)</li>
<li>Optional dedicated operator user ID reference in WordPress options (when using onboarding helper)</li>
<li>Short-lived transient for one-time Application Password display after creation (plaintext is not stored long-term)</li>
<li>Short-lived transient cache for external bearer-token validation, when Turnkey OAuth is used</li>
<li>Optional connected service account tokens, site keys, server URLs, and provider policy links used for remote account and Turnkey OAuth workflows</li>
</ul>
Audit logs may include:
<ul>
<li>Authenticated WordPress user ID</li>
<li>Request route and method</li>
<li>Sanitized request/response summaries</li>
<li>Timestamp and IP address</li>
</ul>
This plugin does not send data to third-party AI services by itself. 
This plugin does not include telemetry/analytics tracking by default.
Site owners are responsible for:
<ul>
<li>Securing the site with HTTPS</li>
<li>Managing WordPress users and Application Passwords</li>
<li>Configuring GPT sharing safely (recommended: Only Me)</li>
<li>Reviewing the privacy implications of any external AI service connected to the site’s API</li>
</ul>

AI Site Manager – Using ChatGPT Claude Codex

Manage WordPress content from ChatGPT, Claude, and Codex using secure REST, OpenAPI, MCP, Turnkey OAuth, or WordPress Application Passwords.

KaliCart Bridge – AI Agent Catalog for WooCommerce vs AI Site Manager – Using ChatGPT Claude Codex