3dsmax-mcp
Related Servers
Alternatives to 3dsmax-mcp
No user-submitted related servers found.
Related Servers
- 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
- FlicenseBqualityBmaintenanceEnables AI agents to control a live 3ds Max session directly, including creating and editing objects, materials, animation, and scene inspection, with undo support.17-
- 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.223 PyPI248MIT
- 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.42417MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Autodesk Maya through natural language for scene creation, modeling, material assignment, and object manipulation.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically control Autodesk Maya via natural language using over 30 tools for 3D modeling, lighting, and animation. It connects through Maya's command port to facilitate procedural scene generation and complex production-ready workflows.1-
TDQS
Scored across 375 tools
With 375 tools there is substantial overlap. Examples: create_primitive vs the many create_box/sphere/cylinder/cone/torus/teapot/plane/tube/pyramid/hedra/geosphere/capsule tools; set_property_value/ctrl_set_property/get_property_value all do arbitrary property access; poly_set_vertex and poly_move_vertices overlap; render_preview and anim_play_preview both generate preview animations; export_engine_preset/export_selection overlap with format-specific exporters. The generic escape hatches (execute_maxscript, execute_python) also blur boundaries with every other tool, making selection harder.
There is a strong prefix-group convention: create_*, poly_*, mod_*, mat_*, map_*, anim_*, rig_*, render_*, viewport_*, export_*, import_*, cam_*, light_*, env_*, bridge_*, scene_*, uvw_*. However, there are notable deviations: generic create_primitive alongside 20 specific create_* tools, model_* vs mod_* subdivisions, convert_to_editable_* using a different verb style than the poly_* tools, and ctrl_*/constraint_* overlapping with anim_*. The pattern is readable but not consistently applied.
375 tools is an extreme count for a single MCP server. While 3ds Max is a large domain, the server exposes nearly every operation plus generic escape hatches, which overwhelms an agent's ability to navigate. Many tools could be consolidated (e.g., a single create_primitive with parameters vs dozens of create_* wrappers, or generic property/modifier tools instead of dozens of specialized variants). This is far beyond a well-scoped tool surface.
The tool surface is exceptionally complete, covering scene management, modeling, polygon editing, modifiers, materials, maps, UVs, lights, cameras, environment, animation, rigging, skinning, rendering, baking, viewports, import/export, and file operations. Generic escape hatches (execute_maxscript, execute_python, create_primitive, mod_add, mat_create_generic, get/set_property_value) fill any remaining gaps. Common workflows from asset creation to engine export are fully supported with no obvious dead ends.