IlluGen

io.github.dokaNc由 GitHub 账号 dokaNc 发布v0.1.1更新于 Oct 24, 2026

Build, edit and render JangaFX IlluGen node graphs (textures, VFX) from your AI agent.

已验证STDIO仅桌面开发者工具媒体与设计

概览

AI 生成的概览

本地 MCP 服务器,让 AI 助手在 Windows 上构建、编辑、校验并渲染 JangaFX IlluGen 的纹理与 VFX 节点图。

可以做什么
检查 IlluGen 安装、运行实例与节点目录版本,浏览节点类型、参数、引脚及自带预设的默认值和取值范围。从空白或预设的可编辑副本创建项目,读取节点、连线、设置、曲线与渐变。增删改节点和连线,设置曲线、渐变与样条控制点,暴露子图参数,添加分组框与注释。设置 FPS、循环区间、默认纹理尺寸等项目设置并生成缩略图。离线校验项目,或以真实加载加试导出方式校验,渲染所有导出节点并返回文件与内嵌预览,截图,以及规范化项目。
适用场景
适合在 Windows 上使用 JangaFX IlluGen 时,让助手把纹理、程序化遮罩或 VFX 翻页图的自然语言描述变成可用的节点图,或检查、调整并重新渲染已有的 .illugen 项目。
运行要求
Windows,已安装并激活的 IlluGen 1.2.x 及有效的 JangaFX 许可证;Python 3.10+,推荐使用 uv。以本地 stdio 进程运行。若 IlluGen 不在默认安装目录,需设置 ILLUGEN_EXE。渲染会启动一个独立的 IlluGen 实例。
安装前请注意
需要自备已授权的 IlluGen,本项目与 JangaFX 无关联。会在指定位置写入项目文件和渲染结果,并在 %LOCALAPPDATA% 下使用临时目录(可用 ILLUGEN_MCP_HOME 覆盖),project_normalize 会保留 .bak 备份。渲染会启动 IlluGen 并触发其导出,失败与警告会返回给助手。仅在 Windows 上测试。

安装

在 SourceWeft 中

  1. 打开 控制台中的 IlluGen,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

IlluGen MCP

Let your AI agent build, edit and render JangaFX IlluGen node graphs.

Describe a texture, a VFX flipbook or a procedural mask in plain words: your agent creates the .illugen project, wires the nodes, checks it and renders it with your own IlluGen. No clicks, no window.

[MIT license] [Python 3.10+] [MCP] [Windows] [CI]

Quick start · What it can do · Tools · How it works · FAQ


[An AI agent builds three IlluGen graphs (lava, underwater caustics, energy web) through illugen-mcp and renders them]

Real tool calls and timings, real IlluGen renders. Reproduce them with examples/demo_scenes.py.


Quick start

1. Requirements

  • Windows with IlluGen 1.2.x installed and activated (a valid JangaFX license: this project does not include or replace IlluGen).
  • Python 3.10+. uv is recommended (no manual install needed).

2. Add it to your agent

Claude Desktop: one click

Download illugen-mcp-<version>.mcpb from the latest release and open it (or drag it into Claude Desktop › Settings › Extensions). Needs uv on your PATH. If IlluGen is installed elsewhere, set its path in the extension settings.

Claude Code

bash
claude mcp add illugen -s user -- uvx --from git+https://github.com/dokaNc/illugen-mcp illugen-mcp

Claude Desktop, Cursor, Windsurf, VS Code, Gemini CLI… (any MCP client): add this to the client's MCP configuration (claude_desktop_config.json, .cursor/mcp.json, …):

json
{  "mcpServers": {    "illugen": {      "command": "uvx",      "args": ["--from", "git+https://github.com/dokaNc/illugen-mcp", "illugen-mcp"]    }  }}
Without uv (plain pip)
bash
pip install git+https://github.com/dokaNc/illugen-mcpclaude mcp add illugen -s user -- illugen-mcp

or "command": "illugen-mcp" in the JSON configuration.

IlluGen installed somewhere else?

Set ILLUGEN_EXE to the full path of IlluGen.exe:

bash
claude mcp add illugen -s user -e ILLUGEN_EXE="D:\Apps\IlluGen\IlluGen.exe" -- uvx --from git+https://github.com/dokaNc/illugen-mcp illugen-mcp
json
"env": { "ILLUGEN_EXE": "D:\\Apps\\IlluGen\\IlluGen.exe" }

3. Ask

Restart your agent, then try:

text
Check that IlluGen is reachable with illugen_status, then build me a tileable stone maskand render it to C:\Users\me\Desktop\stone.

What it can do

  • Build graphs from scratch: all 157 node types of IlluGen 1.2.1 (Grayscale, Color, UV, Geometry, Islands, Utils, signals, import/export…), with their real defaults, every legal enum value, ranges, units and descriptions.
  • Wire them safely: pin types (Grayscale, Color, UV, Normal, Islands, GeometryBuffer…) are checked before IlluGen sees the file, and the error suggests a converter node when types don't match.
  • Go beyond plain parameters: curves, color gradients, spline / lattice control points, subgraphs with exposed parameters, signal modulation (Oscillator → Scale…), framed groups and notes.
  • Start from the shipped examples: copy any of IlluGen's 120+ example presets and modify it.
  • Validate for real: project_validate(engine=true) loads the project in IlluGen, runs a trial export and reports dropped nodes or links, log errors and a screenshot of any warning dialog.
  • Render: project_render runs File › Export on every export node (PNG, JPG, TGA, EXR, HDR, RAW, R16, R8, OBJ, FBX, flipbook sequences…), returns the produced files and an inline preview.
  • Stay out of your way: rendering uses a private, invisible IlluGen instance. An IlluGen you have open keeps running untouched, and nothing steals your mouse or keyboard focus.

Tools

ToolWhat it doesStarts IlluGen?
illugen_statusInstallation, running instances, catalog versionno
list_node_types, describe_node_typeBrowse node types; parameters, defaults, enums, typed pins, curvesno
list_presetsIlluGen's shipped example projectsno
project_newEmpty project, or an editable copy of a presetno
project_summary, node_getRead the graph (nodes, links, settings, curves, gradients…)no
node_add, node_set, node_removeEdit nodes (values validated against IlluGen's definitions)no
link_add, link_removeConnections, parameter pins, optional inputs, modulation rangesno
curve_set, gradient_set, spline_setCurves, gradients, control pointsno
subgraph_expose_paramExpose an inner parameter on a subgraph nodeno
annotation_add, annotation_removeFramed groups and notesno
project_set_settingsFPS, loop region, default texture sizeno
node_set_dataRaw access to any other node fieldno
project_thumbnailThumbnail embedded in the fileno
project_validateOffline checks; with engine=true, a real load + trial exportwith engine=true (~5 s)
project_renderExport everything, optionally to output_dir; files + previewyes (~7 s)
project_screenshotScreenshot of the project open in IlluGen (viewport + graph)yes
project_normalizeLoad + save in IlluGen (fills defaults, refreshes the thumbnail), keeps a .bakyes

Typical flow: project_new → node_add … → link_add … → project_validate(engine=true) → project_render.

Showcase

[Lava, underwater caustics and energy web textures rendered by IlluGen through illugen-mcp]

Lava (Voronoi noise → levels → color ramp → glow), caustics (polygon fractal → caustics → ramp) and an energy web (Voronoi edges → ramp → glow): 4 to 5 nodes each, built and rendered by the agent in about 15 seconds. The exact graphs are in examples/demo_scenes.py.

Example prompts

text
Open the "brick_wall" preset, make it 2048x2048, make the bricks darker and render it.
text
Create a 64-frame looping smoke flipbook (8x8 atlas), export as TGA to D:\fx\smoke.
text
Build a subgraph "edge wear" (noise + levels + blur) with its seed exposed, use it twice withdifferent seeds and blend the results.
text
Explain what every node in C:\projects\lava.illugen does and suggest how to make it less noisy.

How it works

  • Editing happens directly on the file. .illugen projects are read and written losslessly (a file saved without changes is byte-identical), so offline edits are instant and safe. Node definitions come from bundled tables matching IlluGen 1.2.1.
  • Rendering uses IlluGen itself. The server starts a private copy of IlluGen in its own folder, hidden from the screen and the taskbar, loads the project and triggers IlluGen's own export shortcut. It follows progress through IlluGen's log and closes it when done. Your settings and open IlluGen windows are not touched.
  • Errors come back to the agent. Failed exports and loading warnings are detected and returned with a screenshot, so the agent can fix the graph by itself.

Files written by the server: projects and renders where you ask, plus a scratch folder in %LOCALAPPDATA%\illugen-mcp (override with ILLUGEN_MCP_HOME).

Updating IlluGen

The bundled node tables target IlluGen 1.2.1. After an IlluGen update, rebuild the catalog from your installation (takes a few minutes, IlluGen runs invisibly):

bash
uvx --from git+https://github.com/dokaNc/illugen-mcp python -m illugen_mcp.build_catalog

The new catalog is stored in %LOCALAPPDATA%\illugen-mcp\data and takes precedence over the bundled one.

FAQ

Does it work on macOS or Linux? Not yet: rendering drives the Windows build of IlluGen. Offline editing (project_*, node_*, link_*) is pure Python and should work elsewhere, but only Windows is tested.

Will it mess with the IlluGen I have open? No. Each render runs in its own private instance with its own configuration and recovery file.

IlluGen did not finish starting Start IlluGen once by hand (activate the license, close the welcome screen), check the path with illugen_status, and look at the latest log in %LOCALAPPDATA%\JangaFX\illugen\logs. If it persists, open an issue with that log.

A render says "Nodes failed to export". Usually a graph problem (pin type mismatch, disconnected input). The screenshot returned with the error shows the node in warning; describe_node_type lists the expected pin types.

I changed IlluGen's keyboard shortcuts. Supported: the server reads them from IlluGen's config.ini.

Development

bash
git clone https://github.com/dokaNc/illugen-mcpcd illugen-mcppip install -e ".[dev]"pytest                      # tests needing IlluGen are skipped automatically if it isn't installedruff check .

Contributions are welcome: see CONTRIBUTING.md.

Disclaimer

IlluGen MCP is an independent community project. It is not affiliated with, endorsed by or supported by JangaFX. IlluGen and JangaFX are trademarks of their respective owner. You need your own licensed copy of IlluGen; this project neither includes nor modifies it.

License

MIT

来源:README.md,提交 3f92b8a

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

2
  1. v0.1.1最新Oct 15, 2026
  2. v0.1.0Oct 15, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分