Skip to main content
Glama
artokun

ComfyUI MCP

by artokun
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

download_civitai_model

Downloads a CivitAI model to ComfyUI's models folder by resolving the model or version ID via the CivitAI API. Supports local streaming or remote dispatch via ComfyUI-Manager.

Instructions

Download a model from CivitAI into the connected ComfyUI's models/ directory. Resolves a CivitAI model id (latest version) or a model-version id to a download URL via the CivitAI REST API. LOCAL ComfyUI (COMFYUI_PATH set): streams the file to disk under /models// and returns the saved absolute path. REMOTE ComfyUI: dispatches the download to the ComfyUI host via the ComfyUI-Manager install-model HTTP API (fetched server-side). Provide at least one of model_id or model_version_id. Gated/early-access models require CIVITAI_API_TOKEN locally (sent as a bearer header, never in the URL); remote Manager-side fetches rely on tokens configured on the ComfyUI host. NOTE (remote): the server-side install requires the host's ComfyUI-Manager to run with network_mode=personal_cloud (or loopback) and a permissive security level; a stricter gate silently rejects the download, and Manager reports the queue task 'done' even on failure — so a remote dispatch does not guarantee the file landed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameNoOverride the saved filename (defaults to the CivitAI file name, or the URL basename).
model_idNoCivitAI model id. The latest version is used unless model_version_id is also provided.
model_version_idNoCivitAI model-version id (from the URL ?modelVersionId=...). If both model_id and model_version_id are given, this selects the specific version of that model.
target_subfolderYesTarget subfolder under ComfyUI models/. Standard names: checkpoints, loras, vae, upscale_models, controlnet, embeddings, clip, diffusers, diffusion_models, gligen, hypernetworks, photomaker, style_models, text_encoders, unet. Any other relative subfolder (incl. nested like 'loras/<subdir>') is allowed; absolute paths and '..' escapes are rejected.

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

With no annotations, description fully bears transparency burden. Discloses streaming vs HTTP dispatch, token handling (bearer header, not URL), and remote failure modes (silent rejection, misleading queue status). Comprehensive behavioral coverage.

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

Conciseness4/5

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

Well-structured with clear sections for local, remote, and notes. Every sentence adds information, though slightly verbose. Could be trimmed without losing clarity, but earns its length.

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

Completeness4/5

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

Covers input parameters thoroughly and explains return behavior (local: absolute path; remote: no guarantee). Acknowledges limitations for remote. No output schema, so return description is adequate. Slightly incomplete on remote return, but good overall.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). Description adds value beyond schema: explains model_id uses latest version unless model_version_id given, filename defaults, and target_subfolder allows nesting but rejects absolute paths. Justifies a 4.

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?

Description clearly identifies verb (download), resource (model from CivitAI into ComfyUI models/), and scope (local vs remote, resolving IDs). Distinguishes from sibling 'download_model' by specifying CivitAI-specific resolution and the two deployment modes.

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?

Provides explicit requirement to provide at least one of model_id or model_version_id, and explains local vs remote behavior. However, lacks comparative guidance against sibling tools like search_models or the generic download_model, so when-to-use vs alternatives is implicit.

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