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 "Install 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 installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BhaveshY/vectorworks-mcp-codex-plugin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server