Skip to main content
Glama

scaffold_custom_node

Generate a starter pack for a ComfyUI custom node, including required files, a sample node, and optional frontend and CI workflow for publishing.

Instructions

Generate a new ComfyUI custom-node pack from a template into <COMFYUI_PATH>/custom_nodes//. Writes pyproject.toml (with the [tool.comfy] PublisherId/DisplayName/Icon table the Comfy Registry requires), init.py exporting NODE_CLASS_MAPPINGS / NODE_DISPLAY_NAME_MAPPINGS, and src/nodes.py containing a runnable sample node (INPUT_TYPES/RETURN_TYPES/FUNCTION/CATEGORY), plus .comfyignore and .gitignore. Optionally emits a web/js frontend stub (wiring WEB_DIRECTORY) and a GitHub Actions publish workflow (with_ci). This is the FIRST step of the author loop: scaffold here, then restart_comfyui to load it, test it, and finally publish_custom_node. LOCAL-ONLY: it writes to your local ComfyUI install and requires COMFYUI_PATH (it does nothing for a remote --comfyui-url target). Names must be a safe lowercase slug and cannot escape custom_nodes/; an existing non-empty directory is left untouched unless overwrite is true. Use this to CREATE a pack you author — to install someone else's pack use install_custom_node instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPack folder name — a safe lowercase slug (letters, digits, hyphens, underscores), e.g. 'my-cool-nodes'. Becomes the directory under custom_nodes/ and the pyproject [project].name.
display_nameYesHuman-readable name shown in the ComfyUI node menu and the registry listing.
categoryNoNode menu category for the sample node (default 'custom').
descriptionNoShort description written to pyproject [project].description.
publisher_idNoYour Comfy Registry publisher id, stamped into [tool.comfy].PublisherId. If omitted a placeholder is written that you must replace before publishing.
with_frontendNoIf true, also generate a web/js/<name>.js extension stub and set WEB_DIRECTORY (default false).
with_ciNoIf true, also generate .github/workflows/publish_action.yml (Comfy-Org/publish-node-action; needs the REGISTRY_ACCESS_TOKEN repo secret) so pushing a pyproject.toml version bump auto-publishes (default false).
overwriteNoIf true, overwrite template files in an existing pack directory instead of refusing (default false).
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses local-only behavior, name constraints, non-destructive default with overwrite flag, and files generated. Could mention if COMFYUI_PATH is unset, but otherwise transparent.

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?

Single paragraph is somewhat long but front-loaded with main action. Every sentence adds value; no fluff. Could be slightly more structured but remains clear.

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 purpose, generated files, constraints, and relationship to other tools. No output schema, so return values not explained, which is acceptable. Could mention error handling (e.g., missing COMFYUI_PATH) but not required.

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 100% and description adds context beyond basic schema: explains default values, implications (e.g., placeholder for publisher_id), and relationships (e.g., with_frontend wiring WEB_DIRECTORY). All 8 parameters are clearly contextualized.

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?

Clearly states it generates a ComfyUI custom-node pack with specific files (pyproject.toml, __init__.py, src/nodes.py, etc.). Distinguishes from sibling tools like install_custom_node and positions it as the first step of the author loop.

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

Usage Guidelines5/5

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

Explicitly tells when to use (first step of author loop) and when not to (local-only, for remote use nothing). Provides alternative: 'to install someone else's pack use install_custom_node instead.'

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