[WordPress] 外掛分享: KaliCart MCP

首頁外掛目錄 › KaliCart MCP
WordPress 外掛 KaliCart MCP 的封面圖片
全新外掛
安裝啟用
尚無評分
22 天前
最後更新
問題解決
WordPress 6.0+ PHP 8.0+ v0.2.11 上架:2026-06-20

外掛標籤

開發者團隊

⬇ 下載最新版 (v0.2.11) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「KaliCart MCP」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

Help AI assistants find, read and cite your WordPress content. 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 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:

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 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.

延伸相關外掛

文章
Filter
Mastodon