MediaKit Environment Check

If you install the MediaKit Toolkit and don't run this node first, you're doing it backwards. Every other node in the pack uploads your video to Volcengine's cloud and fails after you've waited for an upload. This one checks the CLI, the auth, and the environment up front - and it does it for free, without sending a single frame anywhere. It's the pack's own "run doctor before you complain" button, wrapped in a node.

What it is

A pure diagnostics node that lives under MediaKit/Diagnostics rather than MediaKit/Video AI, because it processes nothing - it inspects the machine and reports. The README's first piece of advice is literally "run MediaKit Environment Check" before anything else, and for once the manual is right.

It takes exactly one input: run_doctor (BOOLEAN, default true). Leave it on. It decides whether the node also runs the CLI's doctor command, which validates the cloud connection and local dependencies, instead of just locating the binary.

What comes out

Two STRING outputs:

• status - ready, warning, or not_ready. One glance tells you whether to keep going or start fixing.
• details_json - a JSON blob with platform, architecture, python, node, npm, whether mediakit-cli was found and its version, and, when run_doctor is on, the redacted doctor output and whether it exited cleanly. If anything throws, you get the redacted error and a not_ready status instead of a crashed graph.

The README promises it never outputs your API key, and the source backs that up: the same redaction pass the cloud nodes use (which strips keys and signed-URL query params) runs over the doctor output before it's printed.

How to read the failure

The node tells you which of the three classic problems you have, which is the whole point:

• mediakit_cli missing or null in the JSON → the CLI isn't on the PATH of the process running ComfyUI.
• CLI found but doctor_ok is false → auth or cloud-connect problem, usually a bad or uninitialized key.
• Everything green but a cloud node still fails → it's not the environment, it's the task or the bill.

Install and the cloud setup it checks

The pack installs like any custom node - ComfyUI Manager, search "MediaKit Toolkit" or mediakit-toolkit, then fully restart - or:

cd ComfyUI/custom_nodes
git clone https://github.com/fudanll-sys/comfyui-mediakit-toolkit.git

There are no Python dependencies and no model downloads (the requirements file is empty; this pack wraps Volcengine's CLI, it doesn't load weights). What it does need, before the check turns ready, is a Volcengine account with an activated AI MediaKit service, an API key, and the CLI installed in the environment that launches ComfyUI:

npx @volcengine/mediakit-cli install -y
mediakit-cli init --mode cloud-first --api-key "YOUR_MEDIAKIT_API_KEY" --credential-store config --yes

or set MEDIAKIT_API_KEY for the ComfyUI process instead. Your key never lands in the workflow JSON.

Honest notes

The pack is 0.3.0 and essentially invisible in the community right now - there's no crowd of bug reports to learn from, so this node is your debugging basecamp. If the check passes, your problem is downstream; if it fails, the JSON names the culprit. One quirk: node and npm are reported as installed-or-not, because you need Node 18+ only to install the CLI, not to run these nodes afterward - so a missing Node entry is worth a look but isn't fatal once mediakit-cli already exists.