dcc-mcp-mari
Production-oriented DCC-MCP adapter for Foundry Mari. It exposes project, geometry, channel, node graph, layer, shader, image, and texture-export workflows as typed tools without arbitrary Python execution. The host plugin supports Mari 5.0 and newer while keeping the DCC-MCP runtime in a separately installed Python 3.9+ sidecar.
Architecture
Mari loads a small standard-library plugin on its GUI thread. The plugin owns an authenticated loopback socket and starts the separately installed DCC-MCP sidecar. A Qt timer executes bounded Mari API commands on the host thread, while networking, discovery, jobs, and Gateway integration stay outside Mari's bundled Python environment.
Install
The authoritative agent-first lifecycle, platform paths, stable JSON schema,
exit codes, recovery behavior, and troubleshooting are in
install.md.
python -m pip install dcc-mcp-mari
dcc-mcp-mari install --dcc-path <mari-executable> --python <python> --dry-run --json
dcc-mcp-mari install --dcc-path <mari-executable> --python <python> --yes --json
Restart Mari after installation. The default Windows target is
Documents/Mari/Scripts. Override it for a custom MARI_SCRIPT_PATH:
dcc-mcp-mari install --dcc-path <mari-executable> --python <python> --script-dir "D:/Mari/Scripts" --yes --json
Uninstall only this adapter's startup files:
dcc-mcp-mari uninstall --dcc-path <mari-executable> --python <python> --yes --json
Capability groups
mari-session: connection and full project lifecycle, including archive, rename, duplicate, and removal.mari-geometry: geometry and channel lifecycle.mari-nodegraph: nodes, connections, and layer stacks.mari-lookdev: shaders, images, export items, and texture export.
All host mutations require a live Mari process. File inputs must be existing absolute paths, output parents must already exist, and destructive operations are explicitly annotated for DCC-MCP clients.
Development
python -m pip install -e ".[dev]"
python -m ruff check src tests
python -m ruff format --check src tests
python -m pytest
python -m build
python -m twine check dist/*
Mari Python API reference: Using Python in Mari.
Metadata
Release files for dcc-mcp-mari 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dcc_mcp_mari-0.3.0.tar.gz | 44.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dcc_mcp_mari-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 98.9 kB
Release files / dcc_mcp_mari-0.3.0.tar.gz
| Download URL | dcc_mcp_mari-0.3.0.tar.gz |
|---|---|
| Size | 44.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f0daf2af28dcb85964fcca59bf5c59b74413b96b87c93783d634ffb32c3e66c
|
|
BLAKE2b-256 checksum How to use checksums |
855ca5d25d820db2df0f46e72108e96748b7daf9a4fdfe9f6b2b9d4a1aed3178
|
| 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 Aug 25, 2026.
Transparency logRelease files / dcc_mcp_mari-0.3.0-py3-none-any.whl
| Download URL | dcc_mcp_mari-0.3.0-py3-none-any.whl |
|---|---|
| Size | 54.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e38dc9b396134ca23b5e386e5527493f8f86ec2b7b2ded5894ffa652c07b0a7d
|
|
BLAKE2b-256 checksum How to use checksums |
1370f4f59d0f29ddd64d4202e3b50c5de9426329cd542f97c53999ef70b73f11
|
| 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 Aug 25, 2026.
Transparency log