sketchup-mcp2
Related Servers
Alternatives to sketchup-mcp2
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceConnects Sketchup to Claude AI through the Model Context Protocol, allowing Claude to directly interact with and control Sketchup for prompt-assisted 3D modeling and scene manipulation.10503MIT
- AlicenseBqualityCmaintenanceIntegration that connects Sketchup to Claude AI through the Model Context Protocol, allowing Claude to directly interact with and control Sketchup for prompt-assisted 3D modeling, scene creation, and manipulation.1026MIT
- AlicenseBqualityDmaintenanceConnects SketchUp to Claude AI through MCP, enabling natural language controlled 3D modeling, component manipulation, and scene creation.10MIT
- AlicenseAqualityCmaintenanceConnects Claude AI to SketchUp, allowing you to create and modify 3D models via natural language commands.2132 PyPI7MIT
- AlicenseBqualityDmaintenanceEnables direct interaction and control of SketchUp through Claude AI using the Model Context Protocol and a TCP socket connection. It allows for prompt-assisted 3D modeling, component manipulation, and the execution of arbitrary Ruby code within the SketchUp environment.101MIT
- AlicenseNot gradedqualityCmaintenanceConnects Rhino and Grasshopper to Claude AI via the Model Context Protocol, enabling prompt-assisted 3D modeling, scene manipulation, and control through tools like object creation, layer management, and code execution.29MIT
TDQS
Scored across 22 tools
Each tool targets a clear resource+action (create primitive, transform, boolean, joints, chamfer/fillet, query, export, screenshot). The only real overlap is list_components vs find_components, since find_components with no filters reproduces the same traversal as list_components; descriptions distinguish them but an agent could still pick the wrong one.
Strong verb_noun snake_case pattern throughout (create_component, transform_component, get_model_info, list_layers, chamfer_edge, create_dovetail, etc.). Minor deviations: the bare 'undo' and the noun-style 'boolean_operation' break the pattern slightly, but the convention is otherwise predictable.
22 tools is on the heavier side, but the domain is broad (primitive creation, joinery, mesh ops, queries, export, viewport, Ruby escape hatch) and nearly every tool earns a distinct slot. It stays within a reasonable envelope rather than sprawling into redundant duplicates.
Covers the full lifecycle: create (primitive/joint/layer), transform, material, boolean, chamfer/fillet, delete, list/find/info, export, screenshot, undo. Gaps are minor — no layer delete/rename or material removal — and eval_ruby provides an escape hatch for anything missing.