Public, host-neutral distribution of the BJD CMS Content skill and its local stdio MCP server. It works with MCP-capable Agent hosts such as Codex, Claude Desktop, OpenCode, and other standard stdio MCP clients.

Current stable release: 0.7.0

MCP server: 0.7.0
Bundled fallback client: 1.9.0
Python: 3.10+
Tools: 23
Runtime dependency: Python standard library only

Download immutable release assets from the Releases page. Do not install the floating main branch.

One prompt to install or update

Copy the complete prompt below into your Agent for either a first installation or any later upgrade. The prompt itself does not change between releases:

请从公共仓库 https://git.justconn.top/gitea-admin/bjd-cms-content 安装或更新 BJD CMS Content。先完整阅读仓库根目录的 AGENT_INSTALL.md，并严格按它执行。检测当前操作系统、Python 版本、Agent 宿主，以及是否已经安装或注册 bjd-cms-content；如果已安装，先记录原安装前缀、版本、plugin/skill 路径、current 指针和宿主注册，保留旧版本作为回滚目标，不读取或改写私有 CMS 凭证。只选择最新稳定、非草稿、非预发布的 Gitea Release；解析后将本次版本、标签、Release URL 和 SHA256SUMS 固定到本次操作，不从浮动 main 安装，也不在执行途中切换版本。下载正确平台的单个归档和 SHA256SUMS，校验 SHA-256 后解压到新临时目录；首次安装使用默认用户前缀，升级必须复用原绝对前缀并通过随包 POSIX 或 Windows 安装器并排安装，绝不覆盖或删除旧版本；如果目标版本已经存在，则校验并复用，不重复安装。先用新版本相邻的 client.py 运行 native-smoke，确认结果与 RELEASE.json 的 server/client 版本和 tool_count 完全一致且 bundled_pair_verified=true；失败时恢复旧 current 指针和宿主注册并停止。验证通过后，只新增或更新 bjd-cms-content 的本地 stdio MCP 注册和完整 skill 注册，保留所有无关宿主配置，按宿主要求重载或重启并再次核对运行身份。升级时原样复用现有私有 helper 配置，不要仅因升级而运行 configure；首次安装或确实缺少配置时才运行 skill 自带 helper 的 configure，再运行不联网且脱敏的 doctor。若 AI_CONTENT_API_TOKEN 尚未配置，只告诉我私有配置文件的准确路径并暂停，让我在本机填写；绝不要要求我把 Token 发到聊天、命令、MCP 配置或日志里。已有 Token 或等我确认已保存后，只执行 GET /api/ai/content/schema/news 作为连接验收，不创建测试内容、不调用写工具。最后报告本次是首次安装、升级还是已为最新版校验，并报告旧/新版本、绝对路径、宿主配置变更、校验和、冒烟结果及保留的回滚路径。任何下载、校验、版本、宿主配置或验收不一致都停止并报告，不绕过检查。

This one prompt installs, upgrades side by side, or verifies an already-current installation. Production CMS credentials are intentionally provisioned separately; an Agent must never download or invent a credential.

Manual installation

Download the .tar.gz archive on Linux/macOS/WSL or .zip on Windows, together with SHA256SUMS.
Verify the selected archive against SHA256SUMS before extraction.

Extract the archive and run:

Linux, macOS, or WSL:

sh install/install.sh

Windows PowerShell:

powershell -ExecutionPolicy RemoteSigned -File install/install.ps1

Read install/generic-mcp.md and the adapter document for your host.

Run the credential-free acceptance check:

python3 plugin/bjd-cms-content/scripts/client.py native-smoke

Run the redacted offline doctor from the installed skill directory. On a first installation or only when configuration is missing, run configure; an upgrade reuses the existing private configuration unchanged:

python3 skill/bjd-cms-content/scripts/cms_api.py doctor
python3 skill/bjd-cms-content/scripts/cms_api.py configure  # only if missing
python3 skill/bjd-cms-content/scripts/cms_api.py doctor     # after configure

After an administrator independently provisions your private CMS Token and you save it in the helper's private configuration file, run only:
```
python3 skill/bjd-cms-content/scripts/cms_api.py GET /api/ai/content/schema/news
```

Do not create dummy production content as an installation test.

Standard MCP process

Every supported host starts the same local process:

{
  "command": "python3",
  "args": ["/absolute/version/path/plugin/bjd-cms-content/scripts/server.py"],
  "cwd": "/absolute/version/path/plugin/bjd-cms-content"
}

Never place AI_CONTENT_API_TOKEN in this shareable MCP configuration. The complete skill must be installed together with the plugin. The standard release discovers its sibling skill automatically; set BJD_CMS_SKILL_ROOT only for a split or otherwise nonstandard installation.

Security boundaries

This repository contains no website source, database, production dump, private key, or CMS credential.
Gitea download access and CMS API authorization are separate boundaries.
Each user or Agent receives an independently expiring and revocable CMS Token with server-enforced site and operation scopes.
Publishing, live updates, rollback, and cache operations retain their explicit confirmation and verification requirements on every Agent host.
Software rollback never rolls back CMS content; use the documented site-scoped audit workflow for eligible corrections.

See AGENT_INSTALL.md for the normative automated install procedure and install/ for host-specific configuration notes.