bjd-cms-content/install/generic-mcp.md

Universal Local stdio MCP Registration

This release has one host-neutral MCP server and one complete matching skill. It requires Python 3.10 or newer and no third-party Python packages.

Install or update

After checking the selected Release archive against SHA256SUMS, extract it and run exactly one wrapper:

sh install/install.sh [--prefix /absolute/user/path] [--python /path/to/python3]
powershell -ExecutionPolicy RemoteSigned -File install/install.ps1 [-Prefix C:\absolute\user\path] [-Python C:\path\python.exe]

The same command handles first install, update, and already-installed verification. Its one-line JSON result is authoritative. It installs each version beside earlier versions, runs the bundled native-smoke, switches the current pointer only after success, and returns the exact runtime paths. Do not repeat its internal version or file checks.

Register

Map the returned values to the host's normal local stdio MCP configuration:

{
  "command": "<python_executable>",
  "args": ["<plugin_path>/scripts/server.py"],
  "cwd": "<plugin_path>"
}

Add or update only the bjd-cms-content entry. The release layout discovers the sibling skill automatically, so do not set BJD_CMS_SKILL_ROOT. Do not put AI_CONTENT_API_TOKEN or any other CMS credential in the MCP configuration.

If the host supports local skills, register the complete returned skill_path directory. If it does not, the stdio MCP still works; the matching skill remains available beside the plugin for an Agent to read before later content work.

The host must keep this stdio process alive across a deletion prepare/apply pair. The API deletion intent remains private in that process and only a one-use, maximum-540-second delete_handle crosses the MCP boundary. If the host cannot preserve one process, use the bundled client.py session; its one-shot call mode deliberately refuses both deletion tools.

If the host has a built-in non-destructive MCP connection test, run it once and require 25 tools. The installer has already completed the protocol-level smoke test, so do not rerun the fallback client, list every tool, set up a CMS connection, or make a CMS request during installation.

Never stop or restart a host from inside that host's current process. If the registration needs an external reload or restart, installation is complete: report the required action and have the user open a new session afterward.