UniversalInstaller(mki-安装Python包)

UniversalInstaller(mki-安装Python包) does exactly what its name says: it pip-installs a Python package from inside a ComfyUI workflow. You type a package name, hit run, and the node invokes pip in the same Python environment that's running ComfyUI, streams the install log to the console, and shows you a ✅ or ❌ status with the full log in a box on the node. No terminal tab required.

Why it exists. Dependency hell, plain and simple. The KB's ecosystem essay describes the structural problem: every custom node installs into one shared Python environment with no isolation, and the more packs you add, the more likely a workflow comes up missing some transitive dependency that no pack's requirements.txt bothered to pin. When that happens, the old ritual was drop to a terminal, run pip, restart. This node folds that ritual into the graph itself.

For a chunk of the user base, the mirrors are the actual point. The author is a Chinese developer, and the node ships one-click switches for the Tsinghua, Aliyun, Douban, and USTC PyPI mirrors - the difference between a download that takes seconds and one that crawls or times out from behind the Great Firewall.

How it works. It builds a command like sys.executable -m pip install <package> and runs it via subprocess, printing output lines to the ComfyUI console as they arrive, then returns a STRING with the success/failure status and the install log. The pack's frontend extension renders that string in a multiline info box on the node.

The inputs that matter:

• package_name - anything pip accepts, e.g. requests or tipo-kgen==0.2.0.
• backend - pip or uv. The uv option runs python -m uv pip install, which means uv has to already be installed in that Python. It's not bundled - pick uv without uv and you just get a failed install.
• mirror_source - default / tsinghua / aliyun / douban / ustc / custom.
• update_if_no_version - appends -U when the package name has no version specifier.
• extra_index_url - only consulted when mirror_source is custom.

Output: one STRING (the status + log).

Gotchas, and there are two real ones. First: restart ComfyUI after a successful install. The README says it explicitly, and it's not a suggestion - a freshly installed module can't be imported by other nodes until the process restarts, because Python's module table was already built. Second: the node re-runs every queue pass. Its IS_CHANGED always reports a change, so ComfyUI will attempt the install on every single run even when the package is already there. Once it works, bypass the node - leaving it live means pip gets invoked constantly, which is slow and noisy. And worth stating plainly: installing a package is executing arbitrary code, in the same unsandboxed model as everything in custom_nodes land. It's a power tool, not a toy - which is presumably exactly why the author built it.

Install. The node itself needs no extra dependencies - the whole pack's requirements.txt exists for the translation nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/MakkiShizu/ComfyUI-MakkiTools
cd ComfyUI-MakkiTools
..\..\..\python_embeded\python.exe -m pip install -r requirements.txt   # Windows portable
pip install -r requirements.txt                                          # venv/conda

Or search "ComfyUI-MakkiTools" in ComfyUI Manager. Restart, then install packages to your heart's content - and restart again after each one.