vn-sketchup-mcp
Related Servers
Alternatives to vn-sketchup-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects MCP-aware AI clients to a live SketchUp session so models can be built and edited through natural-language prompts. Exposes typed tools for geometry creation, materials, booleans, edge chamfers/fillets, joinery, scene export, model introspection, viewport screenshots, and an optional arbitrary-Ruby escape hatch.24MIT
- AlicenseCqualityAmaintenanceEnables MCP clients to inspect and modify SketchUp models through a local authenticated bridge, covering entity creation and editing, geometry, materials, tags, cameras, scenes, transactions, snapshots, and file or view export. It also offers an optional full SketchUp Ruby API execution channel and batch operations for furniture, architectural, and analysis tasks.37MIT
- AlicenseAqualityCmaintenanceConnects MCP-aware AI clients to a live SketchUp session so users can create and modify 3D models, apply materials, perform booleans and joinery, and export scenes through natural-language prompts.22MIT
- AlicenseAqualityCmaintenanceEnables AI clients to drive SketchUp Pro 2026 on a Windows host, including from WSL, by executing arbitrary Ruby in the active model, reading scene and selection details, and capturing viewport screenshots. It talks to a loopback TCP bridge inside SketchUp using a connect-per-command protocol for reliable, desync-free control.4MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and manipulate live SketchUp models through a safe loopback bridge, supporting geometry creation, component/group operations, tags, materials, and transformations with persistent-ID safety.-
- 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.10MIT
TDQS
Scored across 10 tools
Most tools target distinct operations: component creation, deletion, transformation, selection, materials, scene export, and specific joint types. The main ambiguity is eval_ruby, which can theoretically perform any operation, but its purpose as a scripting escape hatch is clear.
Tool names consistently follow a verb_noun pattern, such as create_component, delete_component, transform_component, export_scene, and create_dovetail. There is no mixing of casing styles or vague verbs, making the naming predictable.
Ten tools is a well-scoped number for a Sketchup-focused server. Each tool covers a meaningful aspect of the modeling workflow, and the count is neither too sparse nor bloated.
The tool set covers core component operations and joint creation, but lacks direct component read/list operations and joint removal or editing tools. eval_ruby can fill some gaps, but it is a generic escape hatch rather than a structured part of the domain surface.