Vectorworks MCP
Related Servers
Alternatives to Vectorworks MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude to draw, verify, correct, and organize precise 2D architectural geometry directly in an open Vectorworks file, including exact arcs, measurements, classes, layers, and self-checking fixes.28MIT
- AlicenseNot gradedqualityBmaintenanceConnects Claude Desktop to a running AutoCAD instance over local Windows COM, letting users query, draw, edit, organize layers, measure areas, take off quantities, and export sheets to PDF using plain language. Every action is undoable, logged, and optionally restricted to read-only mode with no network exposure.MIT
- AlicenseNot gradedqualityBmaintenanceLets Claude draw in and inspect the AutoCAD session already running on a Windows PC by attaching over COM, so no add-in or restart is needed. Provides 32 tools for drawings, layers, geometry, dimensions, blocks, queries, view capture and PDF plotting, with an edit guard, busy guard and one undo step per tool.MIT
- AlicenseAqualityCmaintenanceEnables Claude to control AutoCAD—draw, edit, query, layers, blocks, annotations, screenshots, plot to PDF—using plain language.812MIT
- AlicenseBqualityCmaintenanceEnables Claude or any MCP client to build, validate, import, and read Final Cut Pro XML timelines, and to control the macOS app through menus, shortcuts, dialogs, exports, and screenshots, all locally.19MIT
- FlicenseNot gradedqualityAmaintenanceConnects Claude to a running Cinema 4D instance so users can build and edit 3D scenes through natural-language prompts, including primitives, cameras, lights, materials, MoGraph cloners, dynamics, keyframes, and rendered previews. It also exposes scene inspection, file save/load, Redshift material inspection, and arbitrary Python execution inside Cinema 4D.-
TDQS
Scored across 17 tools
Most tools target clearly distinct resource/action pairs, but there is some overlap between vw_set_record (single object or plug-in parameters) and vw_set_lighting_device_fields (bulk lighting device edits), and between vw_list_lighting_devices and vw_lighting_device_report, which both surface device data. The detailed descriptions clarify when each should be used, so ambiguity is limited.
All tool names share a consistent vw_ prefix and snake_case formatting, with predictable patterns such as vw_list_*, vw_get_*, and vw_set_*. A few names are noun-based (vw_document_info, vw_lighting_device_report) rather than strict verb_noun, but the set remains readable and mostly consistent.
17 tools is slightly above the typical 3-15 range, but each covers a distinct capability in a complex CAD/lighting bridge: bridge check, Python execution, API lookup, document/layer/class inspection, records, symbols, undo, and lighting workflows. The set does not feel padded with redundant tools.
The surface covers introspection, generic execution, document/layer/class queries, object finding, record read/write, symbol insertion, undo, and lighting-specific workflows including reports. Dedicated create/delete/modify-object tools are absent, but vw_exec_python provides a workaround, leaving only minor gaps.