Overview
KaliCart MCP turns a WordPress site into something AI agents can browse and query directly. It exposes your editorial content — posts, pages and public custom post types — as a standards-based Model Context Protocol (MCP) server over JSON-RPC 2.0, with content delivered as clean GitHub-Flavored Markdown.
It is read-only and self-hosted: there is no LLM, content cloud or external content processing. An agent connects to a single endpoint on your site and can list, search and read your content as structured data.
Endpoint
MCP server
POST /wp-json/kalicart-mcp/v1/mcp
Discovery document
GET /.well-known/kalicart-mcp
Transport is JSON-RPC 2.0 over HTTP POST. The plugin also advertises itself through a <link rel> tag in the site head, a Content-Signal header, and robots.txt entries.
Tools
The server exposes five read-only tools:
Content control
Exclusion is enforced on three levels:
Structural. Attachments and commerce objects (products, variations) are never exposed. MCP is for content, not commerce.
WooCommerce functional pages. Cart, checkout, my account, shop and policy pages are excluded automatically as application UI rather than editorial content.
Per-item. A "Hide from AI agents" checkbox in the editor removes any single post or page. You also choose which post types are exposed from a toggle in the admin screen.
Connect an agent
The admin screen provides a copy-paste Claude Desktop configuration using mcp-remote. Any MCP-compatible client can connect to the endpoint directly.
{
"mcpServers": {
"kalicart-mcp": {
"command": "npx",
"args": ["mcp-remote", "https://your-site.com/wp-json/kalicart-mcp/v1/mcp"]
}
}
}
Replace your-site.com with your own WordPress site.
Updates & privacy
Plugin updates are delivered directly from mcp.kalicart.com. WordPress periodically reads the HTTPS release manifest at https://mcp.kalicart.com/updates/kalicart-mcp.json; update downloads use a versioned ZIP on the same host.
The update request identifies the installed KaliCart MCP version in its User-Agent and exposes ordinary network metadata such as the server IP to the download host. It sends no site URL, post, page, user, credential or API key. MCP endpoint requests remain local to the WordPress site and never trigger an update check.