MaxForge MCP
Related Servers
Alternatives to MaxForge MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to directly control Autodesk 3ds Max for modeling, shading, rigging, animation, rendering, baking, and engine export through MCP.375MIT
- AlicenseAqualityCmaintenanceEnables MCP clients and AI assistants to inspect and modify a live Autodesk 3ds Max session — reading the selection, querying objects and layers, capturing the viewport, and running MAXScript or Python in the open scene. Every request is logged and each scene change becomes a named undo record, so the AI can only undo its own steps and the user can audit and reverse everything.10MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to inspect and control running 3ds Max scenes across versions 2016–2025, including object queries, property edits, object creation and deletion, screenshots, file import/export, and MAXScript execution. It also provides API discovery and local documentation search to help verify available classes and properties before scripting.15MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to connect to Autodesk 3ds Max via the Model Context Protocol, allowing natural-language control of scene creation, modeling, materials, viewport capture, and plugin introspection through dedicated MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceConnect AI agents to Autodesk 3ds Max through the Model Context Protocol, enabling natural language control of scene creation, materials, modifiers, rendering, and plugin workflows.253 PyPI348MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to directly control Autodesk 3ds Max through natural language to create models, set materials, adjust lighting, and automate animations. It bridges the Model Context Protocol with 3ds Max via a TCP socket to execute Python and MAXScript commands.2418MIT
TDQS
Scored across 17 tools
Every tool targets a distinct operation in the 3ds Max domain: scene state, materials, animation, scripting, selection, object creation, transformation, properties, deletion, export, and saving. Even the two scripting tools (run_maxscript and run_python) are cleanly separated by language, and set_property vs. transform have clear boundaries (arbitrary vs. spatial transformation). No two tools appear to do the same thing.
The majority of tools follow a verb_noun pattern (apply_material, set_keyframe, get_scene_info, create_object, set_property, save_scene, add_modifier). However, several tools use bare verbs (select, transform, delete, export, ping) and two use verb_language (run_maxscript, run_python). This mix of patterns is readable but not fully consistent.
With 17 tools, this is slightly above the ideal 3-15 range but still appropriate for a comprehensive 3ds Max bridge that covers modeling, animation, scene management, and export. The tools are not redundant, and the count reflects the breadth of operations required for a professional DCC integration.
The surface covers the core lifecycle: create, inspect, modify, delete, select, save, export, and add modifiers. It also handles materials and keyframes. Minor gaps include lack of a dedicated get_property tool (though run_maxscript can access anything) and no duplicate or group operations. Overall, agents can accomplish most workflows without dead ends.