Generic MCP Installation

This release contains one host-neutral stdio MCP server and the complete canonical BJD CMS content skill. Python 3.10 or newer is required; no third-party Python package is needed.

Install

Verify the downloaded archive against SHA256SUMS, extract it, then either keep that immutable directory or run the bundled installer:

sh install/install.sh

The installer never reads or writes CMS credentials. It creates a versioned directory and prints the exact plugin and skill paths. On Windows use:

powershell -ExecutionPolicy RemoteSigned -File install/install.ps1

Configure the CMS connection

Run the helper from the installed skill directory:

python3 skill/bjd-cms-content/scripts/cms_api.py configure

The helper prints the private per-user configuration path. Edit only the blank AI_CONTENT_API_TOKEN= value in that file. Never put the token in an MCP config, shell argument, chat message, source repository, installer, or log.

Register stdio MCP

Map these four values into the Agent host's native MCP configuration syntax:

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

Do not add AI_CONTENT_API_TOKEN to this shareable configuration. The helper loads it from the user's private config file.

If the host supports skills, also register or copy the complete installed skill/bjd-cms-content directory using that host's normal local-skill mechanism. MCP remains functional without a proprietary skill loader, but the Agent should be instructed to read the bundled README.md and SKILL.md before content work.

Verify

Before any CMS request, run the adjacent fallback client:

python3 plugin/bjd-cms-content/scripts/client.py native-smoke
python3 plugin/bjd-cms-content/scripts/client.py --result-only call cms_doctor

For release 0.6.1, require server 0.6.1, client 1.8.0, 23 tools, and bundled_pair_verified=true. Then run the read-only connection check:

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. Complete write acceptance belongs in the disposable test environment; the first production write should be a reviewed, real business draft.

Upgrade and rollback

Install every new release into a new immutable version directory, switch the host registration or current pointer, restart the Agent host, and rerun native-smoke. Keep the previous version until the new release is accepted.

Switching the plugin back does not undo CMS writes. Use the site-scoped audit preview/apply workflow to correct eligible content changes.

2.8 KiB Raw Blame History