Vectorworks MCP
Related Servers
Alternatives to Vectorworks MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude to control AutoCAD—draw, edit, query, layers, blocks, annotations, screenshots, plot to PDF—using plain language.86MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to work inside Autodesk Civil 3D 2027 through natural language, reading and drawing geometry, modeling roads with alignments, profiles, assemblies, corridors and superelevation, computing earthwork volumes and mass haul, and managing styles, label sets, blocks and hatches.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to analyze, edit, quality-check, and generate Final Cut Pro FCPXML timelines through 30 tools, including marker management, editing, QC grading, and EDL/CSV export. Also provides AppleScript and GUI automation to move timelines in and out of Final Cut Pro without manual menu clicks.MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude to read, edit, and generate real Final Cut Pro timelines from exported project XML, handling cut detection, markers, roles, silence removal, rough cuts, keyframes, speed ramps, and transcript-based editing. Every write is sha256-journaled and reversible, with quote-then-confirm generation and optional pushes straight into a running Final Cut Pro.-
- FlicenseNot gradedqualityAmaintenanceConnects Claude to Cinema 4D so you can create and manipulate scenes through natural-language prompts. It exposes tools for building primitives and abstract shapes, grouping objects, adding cameras, lights, materials and shaders, applying MoGraph cloners, effectors and fields, setting keyframes, driving physics, running Python inside C4D, and rendering previews or frames.-
- AlicenseCqualityCmaintenanceDrive McNeel Rhino 8 and Grasshopper from Claude through the Model Context Protocol.500MIT
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.