Color Input (mtb)

MTB Nodes has its own color type running through several of its nodes - Batch Shape's fill and background colors, and anything else in the pack expecting a COLOR. Color Input is the standalone version of that picker: instead of a color field baked into the node that uses it, you get a dedicated node with a color-picker widget whose output you can wire to as many downstream nodes as you want.

Why you'd use a separate node for this

If you only ever set a color in one place, you don't need this - just use the inline color widget on whatever node actually needs it. Color Input earns its place the moment you want the same color driving more than one thing: a shape's fill and a background overlay's tint sharing one palette choice, say. Set it once here, wire the output to both, and changing your mind about the color later means editing one node instead of hunting down every place you typed the same hex code. It's the same reasoning behind using a variable instead of a magic number scattered through code, applied to a ComfyUI graph.

The input and output

• color (default #ffffff) - a color-picker widget, typed MTB_COLOR on the way in.

Output: a single COLOR - mtb's shared color type, ready to wire into any other mtb node that accepts one (Batch Shape's color, bg_color, and shade_color inputs, for instance).

Installing it

ComfyUI Manager: search MTB Nodes, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/melMass/comfy_mtb

then restart ComfyUI. No dependencies of its own beyond the base pack.

Common issues

The main thing to know is that this outputs mtb's own COLOR type, not a generic hex string - it's meant to plug into other mtb color-aware nodes, not into arbitrary text fields elsewhere in ComfyUI. If you need the actual hex string for something outside the mtb ecosystem (a filename, a text overlay), you'll want a conversion step rather than wiring COLOR directly into a STRING socket.

Beyond that, it's the pack-wide caveat that applies to every mtb node: MTB doesn't crash outright if one of its nodes fails to import - it logs [comfy_mtb] Some nodes (N) could not be loaded at startup and points you at http://127.0.0.1:8188/mtb, then carries on with the rest of the pack working normally. That's a real behavior other users have confirmed in their own install logs, so if Color Input doesn't show up after installing, check that console line before you assume the whole install broke.