Keyshot MCP
Related Servers
Alternatives to Keyshot MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA local MCP server that enables AI apps to control KeyShot Studio for scene inspection, rendering, model import, material application, camera adjustment, environment setting, and scene saving.19265 npm29MIT
- FlicenseBqualityBmaintenanceEnables safe, observable Blender research by exposing structured tools for viewport capture, object and material edits, semantic scene creation, and managed .blend project lifecycles with transactional rollback and validation.42-
- FlicenseNot gradedqualityBmaintenanceEnables control of a live SOLIDWORKS session through the Windows COM API, providing native sketch, feature, body, reference-geometry, view, probe, and export operations, along with transactional CAD plans, parametric sketches, multibody tools, and deterministic raster-to-sketch vectorization pipelines.1-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run Python inside a live Autodesk 3ds Max session, inspect scene data, capture viewport images, undo operations, and execute headless batch jobs.MIT
- FlicenseBqualityDmaintenanceEnables GUI automation for controlling PIX4Dmatic on Windows through MCP. Supports launching, focusing, capturing screenshots, sending hotkeys, clicking UI elements, opening projects, starting processing, and checking outputs.18-
- AlicenseBqualityCmaintenanceEnables MCP clients to observe and operate the Insta360 Studio desktop app on Windows, including session and window control, input actions, media import and info, and export verification.211MIT
TDQS
Scored across 33 tools
Most tools target a clearly distinct action-resource pair: render_image/render_status/wait_for_render/view_image are cleanly separated phases, and the material-graph tools (add/connect/disconnect/remove node) are unambiguous. Minor overlap exists between list_materials, get_material and list_library_materials, and execute_python vs lux_functions, but the descriptions resolve these.
The bulk of names follow a predictable verb_noun snake_case pattern (list_objects, set_camera, assign_material, connect_material_nodes). A handful start with a noun or bare identifier (screenshot, keyshot_status, lux_functions, reload_bridge), which are minor deviations but still readable.
33 tools is on the heavy side of the 25+ threshold, though the 3D scene domain is genuinely broad (rendering, materials, cameras, environments, scene state). Each tool appears to earn its place, but the surface is large enough to feel weighty for an agent to navigate.
Coverage is thorough across every visible sub-domain: rendering lifecycle (launch/status/wait/view), full material graph editing with undo/commit, library materials, cameras, environments, visibility, and status checks. Few obvious gaps remain for the stated purpose of controlling a KeyShot scene.