su-unity-walkthrough
Related Servers
Alternatives to su-unity-walkthrough
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
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query SketchUp models, extrude massing volumes, configure solar shadows, and capture viewport renderings through MCP tools.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
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to execute editable-3D design programs, inspect their geometry, and replay or revise native project files through MCP tools.1Apache 2.0
- AlicenseAqualityDmaintenanceControls SketchUp via AI assistants, enabling 3D model creation programmatically through the Model Context Protocol.2115MIT
- AlicenseNot 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.MIT
TDQS
Scored across 14 tools
Most tools target clearly distinct pipeline stages (config lifecycle, inventory, staging, review, preview, launch, reports). A few boundaries are fuzzy: job_get vs job_reconcile vs workflow_status all report on job state, and environment_inspect vs inventory_query both surface local state, though descriptions do differentiate them.
Nearly all names follow a noun_verb pattern (config_read, job_get, review_record, preview_control). The lone irregularity is workflow_status, which uses a noun instead of a verb, but overall the convention is predictable.
Fourteen tools map cleanly onto the pipeline's phases—discovery, config, inventory, staging, reconciliation, review, verification, and reporting—with no obvious padding. Each tool earns its place.
Coverage is strong across the walkthrough lifecycle: config create/read/save/validate, inventory, multi-stage jobs, review recording, status, launch, preview, and report reading. Minor gaps exist—no explicit job cancel/abort, no report listing, and no cleanup/teardown for created artifacts—but agents can likely work around them.