3dsmax-mcp

A production oriented MCP server that connects AI agents to Autodesk 3ds Max. Works with any MCP-compatible client.

Features

• Native C++ Bridge — 76 handlers running inside 3ds Max as a GUP plugin, 86-130x faster than MAXScript
• One-step installer — uv run python install.py handles everything
• Quad-view capture — Screenshotting is fast and supports multi views.
• Full default tool surface — full MCP profile exposes core and specialty scene/object/material/pipeline tools by default
• 116 tools in full profile across scene, objects, materials, modifiers, controllers, viewport, introspection.
• Bundled MAXScript reference — 10 topic files for agents to write correct MAXScript

Architecture

Agent  <-->  FastMCP (Python/stdio)  <-->  Named Pipe  <-->  C++ GUP Plugin  <-->  3ds Max SDK
                                      |
                                      +--> TCP:8765 fallback --> MAXScript listener

The native bridge runs inside 3ds Max as a Global Utility Plugin. It reads the scene graph directly through the C++ SDK and communicates over Windows named pipes. 76 native handlers for scene, objects, materials, modifiers, controllers, viewport, introspection, and more.

Requirements

• Python 3.10+
• uv
• Autodesk 3ds Max 2026 (2024/2025 supported via MAXScript fallback)

Installation

git clone https://github.com/cl0nazepamm/3dsmax-mcp.git
cd 3dsmax-mcp
uv sync
uv run python install.py

Updating

git pull
uv sync
uv run python install.py

To install without copying or building the agent skill files:

uv run python install.py --skip-skill

MCP Tool Profile

The external MCP server defaults to the full profile so specialty modules such as Data Channel, effects, floor-plan generation, tyFlow, RailClone, wire params, and standalone-chat driver tools are available without extra setup. Use the core profile only when you want a smaller common-tool surface.

$env:MCP_TOOL_PROFILE = "core"
python -m src.server

Skill

The skill file teaches agents how to use the tools, what pitfalls to avoid, and how 3ds Max works. Without it, agents will guess wrong on material workflows, controller paths, and plugin APIs. The installer builds and deploys it automatically.

However Anthropic models seem to REALLY like using maxscript instead of using the native tooling unlike Codex which uses the right tool most of the time.

If you need to rebuild manually:

python scripts/build_skill.py

Safe mode

Both the native bridge and the MAXScript listener read from a shared config:

%LOCALAPPDATA%\3dsmax-mcp\mcp_config.ini

[mcp]
safe_mode = true

When enabled (default), these commands are blocked: DOSCommand, ShellLaunch, deleteFile, python.Execute, createFile

To disable, set safe_mode = false and restart 3ds Max.

Scope — read this

safe_mode is an accident preventer, not a sandbox. It's a case-insensitive substring blocklist, so a determined author (or a sufficiently clever LLM) can bypass it with string concatenation, DotNet reflection, etc. It catches the obvious shapes — LLM hallucinates deleteFile → rejected — not an adversarial MaxScript author.

What it doesn't cover:

• Native C++ handlers run unfiltered: delete_objects, manage_scene (reset/new/open), render_scene, merge_from_file, write_osl_shader, capture_* (disk writes). If the LLM hallucinates them they run.
• The \\.\pipe\3dsmax-mcp named pipe uses the default ACL — any process running as your user can open it and send commands. Fine on a single-user dev machine; if you need multi-user isolation, gate on GetNamedPipeClientProcessId.

The v0.7.0 chat window runs your configured LLM with direct scene-editing tools. Treat it l

... View full README on GitHub