SketchUp MCP for SketchUp Make 2017
Related Servers
Alternatives to SketchUp MCP for SketchUp Make 2017
No user-submitted related servers found.
Related Servers
- 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.371MIT
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- AlicenseBqualityAmaintenanceAsk, check and change live Revit models from Claude, Cursor or any MCP client. One undo per change, read-only switch. Revit 2022-2027.795MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI hosts to interact with a browser CAD workbench through model-neutral local stdio or authenticated remote MCP tools, supporting command discovery, design-health analysis, and scoped previews while never reading local files or taking over open sessions.MIT
- 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
- AlicenseBqualityBmaintenanceEnables MCP clients to inspect and edit animation inside a running Cascadeur instance without Computer Use, including scene/object and skeleton rig inspection, bounded joint and Point-target pose edits, snapshots, playback observation, and FBX export.371MIT
TDQS
Scored across 38 tools
Most tools target a clearly distinct operation, and create_* primitives (face, edge, circle, arc, polygon) are distinguishable by shape. The one soft overlap is move_plane vs remap_planes and measure vs audit_geometry, but their descriptions explain the boundaries well enough to avoid misselection.
Names are consistently snake_case and verb-first (list_materials, create_face, cut_opening, move_entity). A few are bare verbs (select, save, measure, push_pull, follow_me), which is a minor deviation but still readable and predictable.
38 tools is heavy and above the comfortable 15-25 band, but the domain is broad (read/model info, creation primitives, transforms, opening cut/fill, geometry cleanup, audit, file ops, Ruby escape hatch), so most tools earn their place. It is on the borderline of over-scoped rather than clearly excessive.
Coverage is strong across read, create, transform, clean-up, audit and save workflows, with an execute_ruby fallback that fills most gaps. Minor holes remain: no explicit delete/erase-entity tool, no material creation/assignment, and no layer creation.