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 分