dcc-mcp-rizomuv
Headless RizomUV adapter for DCC-MCP: batch UV unwrapping and packing driven by an AI agent, with no window ever appearing.
Why headless
RizomUV 2027 ships a headless mode (-hl / --headless) in which the whole
scripting surface runs with nothing on screen. For agent-driven work that is the
difference between a batch that finishes and a batch that hangs:
- no window, no panel, no dialog, no message box
- no modal can stop a run waiting for a click
- console output and clean exit codes for reliable orchestration
- user settings are not touched, so runs are reproducible
- the command log is a replayable script: drive the GUI once, replay it headless
Install
pip install dcc-mcp-rizomuv
Requires RizomUV 2027.0.417 or later. RizomUVLink ships inside that
installation, so installing RizomUV is enough on Windows and macOS. On Linux
there is no install registration: extract the package from the AppImage and
point RIZOMUV_LINK_DIR at it.
| Variable | Purpose |
|---|---|
RIZOMUV_EXE |
Pin a specific RizomUV executable. Required on Linux. |
RIZOMUV_LINK_DIR |
Point at an extracted RizomUVLink package. |
DCC_MCP_RIZOMUV_ALLOWED_ROOTS |
os.pathsep-separated roots that reads and writes are confined to. |
Usage
# Is headless RizomUV usable here?
dcc-mcp-rizomuv doctor --json
# Run the MCP server
dcc-mcp-rizomuv
from dcc_mcp_rizomuv import RizomuvSession
with RizomuvSession() as session:
print(session.unwrap_file("mesh.obj", "mesh_unwrapped.obj"))
print(session.unwrap_batch(["a.obj", "b.fbx"], "out/"))
Supported input: .obj, .fbx, .usd, .usda, .usdc, .gltf, .glb.
Important constraints
Headless is not displayless. RizomUV still needs a desktop session to start — an X display on Linux, a logged-in session on Windows. It will not run in a container with no X server, nor as a Windows service. Under CI or Docker, provide Xvfb or equivalent.
A failed Load does not raise. It returns {"Error": {"Msg", "Code"}}.
Check the result; otherwise the run carries on and fails later with a
misleading "no UV set".
Dialogs are auto-answered, and a question you would have answered "yes" to is answered "no" — a script that did not ask for something must not get it.
Licensing. Headless uses the normal RizomUV license. Several instances can run concurrently, but with a floating license each instance takes a token.
License
MIT. See LICENSE.
Metadata
Release files for dcc-mcp-rizomuv 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dcc_mcp_rizomuv-0.1.1.tar.gz | 23.3 kB | With provenance | Details for dcc_mcp_rizomuv-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dcc_mcp_rizomuv-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for dcc_mcp_rizomuv-0.1.1-py3-none-any.whl |
Total release size: 46.0 kB
Release files / dcc_mcp_rizomuv-0.1.1.tar.gz
| Download URL | dcc_mcp_rizomuv-0.1.1.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
082f64968a7dd577581a120dfab757cc57226806f39d242af6f6eb22359df137
|
|
BLAKE2b-256 checksum How to use checksums |
9cdb70a7ba5b3a59ef79836c485adb1371d6d5187e3cdb093b5fe56cdd8d5a0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / dcc_mcp_rizomuv-0.1.1-py3-none-any.whl
| Download URL | dcc_mcp_rizomuv-0.1.1-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ba602b499596a3a5a32a501295bbb97bc6c773b7493da8a8d628709e61b49b7
|
|
BLAKE2b-256 checksum How to use checksums |
554f3f7353d660ffdb846a2128b1e3b68d9c24639590e89a40463f61013dc003
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logSecurity for dcc-mcp-rizomuv 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dcc_mcp_rizomuv-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
