Autodesk

Flue-based control of Autodesk desktop applications lets a coding agent operate professional software such as 3ds Max directly from the shell, without standing up an MCP server. The bridge follows a simple stdin/stdout contract: the agent shell invokes an adapter script (for example, adapters/3dsmax_adapter/3dsmax_bridge.py), which drives MAXScript or Python inside the running application and returns a JSON result. That round trip lets an agent inspect an open scene (objects, modifiers, materials, and the current selection) and make bounded edits or run small scripts that a command-line agent could not otherwise perform inside a GUI application.

Reach for this capability when a human is working inside an Autodesk desktop app and asks for scene inspection or scripted changes. The recommended flow is to read FLUE.md in the skill directory first to understand the bridge contract, safety expectations, and a worked example, then identify which Autodesk app is in use (currently 3ds Max) and pick the matching adapter. When Flue is already installed, the operational contract also lives in the installed flue SKILL.md and each adapter's APP.md.

Installation is a two-step command, pip install flue && flue setup, but it should never be run without explicit approval in the session. Although the current focus is 3ds Max, one Flue install covers many creative and productivity tools through the same contract, including Photoshop, Illustrator, Premiere, After Effects, InDesign, Audition, Blender, Houdini, Unity, and Microsoft Office. Because it acts inside live professional software, the guidance favors small, inspectable steps and avoids destructive actions unless explicitly requested. Flue is MIT-licensed and reviewable on GitHub and PyPI before use.