Connectors
A connector makes your StyleRef styles usable inside a creative tool, rather than copied into it. Instead of pulling a style, copying the text, and pasting it into a prompt box, you load the style where you already work and it stays in the document.
Available connectors
| Connector | Status | What it does |
|---|---|---|
| ComfyUI | Beta | Load styles as nodes; search the gallery in-canvas; compose prompts per model |
CLI (npx styleref) | Stable | Pull, init, and validate styles from the terminal |
Working in an agent or writing your own integration? The MCP server and REST API cover those directly.
Open source by default
Every connector is MIT licensed in its own public repository. You can read exactly what a plugin does before installing it, fork it, or fix it.
That is a deliberate split. Connectors are thin clients of the public REST API — they contain no logic that only StyleRef could write. Style compilation, extraction, and your library live on the server, so a connector is a well-behaved API consumer and nothing more.
One practical consequence: connectors improve without updates. When StyleRef’s prompt compiler gets better at phrasing for a model, you get that the next time you load a style — no plugin release involved.
What connectors don’t change
A connector inherits the account model exactly as it is:
- No account — search the public gallery, load any public style, compile it for any target.
- Free account — your own private styles, including ones you extracted from images on styleref.io.
- Paid plan — more credits and plan-gated features.
See plans and limits. A connector never adds its own tier or paywall.
Build your own
The same API the ComfyUI nodes use is public and documented. If you want StyleRef inside a tool we haven’t reached yet, see building a connector.