Skip to main content
Glama

install_comfyui

Install ComfyUI into an empty directory with Python dependencies and optional ComfyUI-Manager. Returns a detailed report upon completion.

Instructions

Install ComfyUI locally: git-clone it into a target directory, create a dedicated workspace virtualenv (/.venv), and install Python requirements INTO that venv (never the Python running this MCP server) via pip or uv. ComfyUI-Manager is installed from manager_requirements.txt when present, else git-cloned as a fallback. Mirrors comfy-cli install. LOCAL, subprocess-only and independent of any remote --comfyui-url target; the target dir must be empty or non-existent (an existing install is never overwritten). Runs SYNCHRONOUSLY and can take several minutes (large git clone + full torch/dependency install); the call blocks until done. On success returns a JSON report { installed, targetPath, venvPath, comfyuiUrl, managerInstalled, managerVia, version, pythonInstaller, steps[] }. Does NOT start ComfyUI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
use_uvNoIf true, prefer `uv pip install` over plain pip when uv is available on PATH. Falls back to pip if uv is missing. Default false.
versionNoComfyUI version to install (comfy-cli semantics): "nightly" (default-branch HEAD), "latest" (newest release tag), or a semantic version like "0.3.40" (checked out as tag v0.3.40). Raw git refs/branches are rejected. Omit to track the default branch HEAD.
target_pathYesAbsolute path to the workspace directory to install ComfyUI into. Must be empty or non-existent.
skip_managerNoIf true, do not clone/install ComfyUI-Manager. Default false (Manager is installed).
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses behavior: synchronous operation, potential long runtime, no overwrite of existing installations, local subprocess-only execution, and that it does not start ComfyUI. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise despite thoroughness, with each sentence providing essential information. It is front-loaded with the main action and structured logically, avoiding redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description details the return JSON structure, steps array, and key fields. It covers prerequisites (empty target), side effects (no overwrite), and performance (synchronous, minutes), making it complete for a complex install tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant semantic value: explains version semantics (nightly, latest, semver), clarifies skip_manager and use_uv defaults, and details target_path requirements (empty or non-existent).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool installs ComfyUI locally, specifying cloning, virtual environment creation, and package installation. It distinguishes itself from sibling tools like update_comfyui by focusing on initial installation, not updates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool (for local installation) and references comfy-cli, but does not explicitly compare with sibling tools like update_comfyui or install_custom_node. It provides context but lacks clear exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/artokun/comfyui-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server