Vectorworks MCP Codex Plugin
Allows AI agents to interact with Vectorworks CAD software, enabling operations such as managing documents, running diagnostic and setup tasks, and executing Python scripts within the Vectorworks environment via an MCP bridge.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Vectorworks MCP Codex Pluginlist all layers in the current document"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Vectorworks MCP Codex Plugin
Lean Codex plugin for the latest vectorworks-mcp runtime. The plugin packages skills, a stable control helper, and companion launch scripts; the MCP engine, listener, tests, and native SDK source remain in the companion repository so they cannot drift into a stale embedded copy.
This plugin is strictly Windows 11-only and requires Vectorworks 2024 or 2025 on the same desktop. macOS, Linux, WSL, containers, Wine, and cross-machine bridge layouts are unsupported.
Install
/plugin marketplace add BhaveshY/vectorworks-mcp-codex-plugin
/plugin install vectorworks@vectorworks-mcp-codex-pluginRun vectorworksctl agent-install --json once to resolve or clone the companion
to %USERPROFILE%\repos\vectorworks-mcp, prepare its cached .venv, and return
the exact loader and next steps. Daily MCP startup only resolves an existing
checkout and validates its companion contract; it never clones the repository
or runs the full setup flow. Missing or stale checkouts therefore fail fast
with a repair command instead of delaying MCP connection. The companion runner
still checks its requirements stamp and repairs a missing or outdated virtual
environment; running agent-install first keeps that work off the normal path.
Recommended explicit override:
$env:VW_MCP_REPO = "C:\path\to\vectorworks-mcp"Use vectorworksctl agent-install --json for initial setup and
vectorworksctl doctor --json for troubleshooting. For daily work, Codex
should begin with vw_agent_context(profile="production"), which combines
preflight, capabilities, and compact drawing context in one MCP call.
Related MCP server: revit-mcp
Safety model
Native phase 2 is the preferred non-modal production path.
The Python
dialoglistener is a usable CAD-safe fallback while its dialog remains open.Background/timer listeners are transport-only and must not execute CAD calls.
Destructive, probing, and trusted-code tools require their explicit live confirmation arguments.
Supported application target: Vectorworks 2024/2025 on native Windows 11 only.
This server cannot be deployed
Maintenance
Related MCP Connectors
Convert Revit files to XKT, IFC, or DWG and query BIM data via natural language.
Use AI models for chat, image, and video generation from Claude Code and other MCP hosts.
Gives your AI assistant persistent memory and intelligence about your work patterns.
AI Hub for AEC — 50+ 3D formats, clash detection, ACC integration via Autodesk Platform Services.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Autodesk Civil 3D, allowing them to retrieve project data, create/modify/delete drawing elements, and execute code to automate Civil 3D operations.329MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Autodesk Revit to query project data, manage elements, and execute generated code via the Model Context Protocol. It provides full compatibility with GitHub Copilot and Claude to automate BIM modeling workflows.1360 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Autodesk Civil 3D through natural language, supporting tools for surfaces, alignments, profiles, corridors, pipe networks, COGO points, and AutoCAD geometry.93MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients like Claude Desktop to control AutoCAD through natural language commands using the Model Context Protocol.2MIT