KaliCart MCP

KaliCart MCP makes your WordPress site agent-ready: it turns your editorial content into something AI agents and assistants — such as ChatGPT, Claude, Gemini, Perplexity and any MCP-capable client — can browse, search and read directly. It exposes your posts, pages and public custom post types as a standards-based Model Context Protocol (MCP) server over JSON-RPC 2.0, alongside clean Markdown output and a lightweight presence/discovery layer. No LLM, no cloud, no external calls — everything runs on your own server. It is read-only: an agent connects to a single endpoint on your site and can list, search, and read your published content as structured data — it never creates, edits, or deletes anything. What it does

• Serves a JSON-RPC 2.0 MCP endpoint at /wp-json/kalicart-mcp/v1/mcp.
• Exposes five tools: site_info, site_map, list_content, search_content, get_content.
• Converts post content to clean GitHub-Flavored Markdown, including tables.
• Advertises itself through a <link rel> tag, a /.well-known/kalicart-mcp discovery document, a Content-Signal header, and robots.txt entries.

Content stays under your control Exclusion works on three levels, all enforced:

1. Structural - attachments and commerce objects (products, variations) are never exposed. MCP is for content, not commerce.
2. WooCommerce functional pages - cart, checkout, my account, shop, and policy pages are excluded automatically as application UI rather than editorial content.
3. Per-item - a "Hide from AI agents" checkbox in the editor lets you remove any single post or page.

You choose which post types are exposed from a simple toggle in the admin screen. WooCommerce coexistence KaliCart MCP is the content companion to the KaliCart Bridge commerce plugin. The two are fully independent - separate namespaces, separate code - and can run side by side. MCP handles editorial content; Bridge handles products and commerce.

0.2.10

• Compliance: admin page styles and scripts are now enqueued via wp_enqueue_style / wp_enqueue_script on admin_enqueue_scripts (scoped to the plugin's own screen) instead of being printed inline. Dynamic values reach the script through wp_localize_script.
• Compliance: unified every plugin-owned identifier (options, post meta, query var, nonces, classes, constants) under a single kcmcp_ prefix. No new behavior; no database migration.
• Robustness: the admin category list and the site_info term counts now restrict to the primary language through the same multilingual helper used by the content tools, so WPML sites (not only Polylang) show one language. No-op on monolingual sites.

0.2.9

• Multilingual support: on sites running a multilingual plugin (Polylang or WPML), KaliCart MCP now serves content in the site's primary language only. This removes duplicate posts, pages and categories from listings, search and the site map, so agents receive one clean, coherent set of content instead of the same item repeated once per language. The served language is declared in the JSON (language / served_language) so agents never have to guess; agents translate on demand for the end user.
• Admin: the category exclusion list now shows only primary-language categories (no more ambiguous per-language duplicates), with an explanatory notice on multilingual sites. Monolingual sites are unaffected.
• Content: list and search results now include each item's taxonomy terms (categories, tags), so the JSON is self-contained — an agent sees an article's category without a follow-up request.

0.2.8

• Hardening: reviewed all REST routes for WordPress.org compliance. Read-only public MCP endpoints declare an explicit public permission_callback (__return_true); admin endpoints require manage_options plus a per-item capability check and a wp_rest nonce. No behavioral change.
• Maintenance: removed the manual load_plugin_textdomain() call (translations are loaded automatically for plugins hosted on WordPress.org since WP 4.6).

0.2.7

• Fix: site_map no longer surfaces WooCommerce navigation (shop, product categories/tags); menu filtering matches linked objects, not URL slugs, so it is language-independent.
• Fix: list_content returns an explicit error for a non-exposed post_type instead of silently falling back to posts.
• Add: when WooCommerce is detected, the initialize instructions state the content-only policy and point agents to KaliCart Bridge for catalog data.

0.2.6

• Admin: finalized the KaliCart MCP brand logo in the page header.
• Maintenance: corrected the readme Contributors entry.

0.2.5

• Admin: new KaliCart MCP brand logo in the page header.

0.2.4

• Fix: restore toggle switch styling (a clipping rule was hiding the switch track); switch styles are now unified across both toggle sections.

0.2.3

• Fix: the "Content exposure" toggles now react only to the switch, not to clicks on the type label — same scheme as the exclusion list.

0.2.2

• Fix: clicking a row's title no longer toggles it — the hidden checkbox is now confined to the switch control instead of overflowing the whole row.

0.2.1

• Fix: sidebar menu icon now uses the same inline-SVG scheme as KaliCart Bridge (correct alignment, no CSS mask).
• Fix: exclusion row toggles switch only via the switch control, not by clicking the row.

0.2.0

• Admin: content exclusion controls — hide categories, individual posts and pages from AI agents via instant toggles, plus a per-item "Hide from AI agents" switch in the editor sidebar.
• Admin: unified post/page search with AJAX toggles and a live-updating "currently hidden" list.
• WooCommerce functional pages (cart, checkout, account, shop) are now excluded from agent-readable content automatically.
• Internationalization: Italian, German, French and Spanish translations; translation loader added.
• Fix: row toggles now switch only when the switch itself is clicked, not the whole row.
• Fix: sidebar menu icon alignment.

0.1.0

• Initial release.
• JSON-RPC 2.0 MCP server with five tools (site_info, site_map, list_content, search_content, get_content).
• Content data layer with three-level exclusion (structural, WooCommerce functional pages, per-item opt-out).
• HTML to GitHub-Flavored Markdown conversion, including tables.
• Presence and discovery layer: link rel, .well-known document, Content-Signal header, robots.txt entries.
• Admin screen: server status, content-exposure toggles, endpoint with copy, Claude Desktop config, WooCommerce coexistence card.
• Per-item "Hide from AI agents" control in the editor.