vw_doctor
Diagnoses why Vectorworks MCP is not responding by checking bridge installation, job files, and config without touching Vectorworks; optionally repairs stale files and reinstalls the bridge.
Instructions
Check this Vectorworks MCP setup on this Mac without touching Vectorworks.
Checks: bridge installed in the right Plug-ins folder and up to date (with its check tables), the 'MCP Run Job' command file present, Claude Desktop / Claude Code configured for this Vectorworks version, Vectorworks running, stale job files, recent log errors. Returns {ok, checks: [{name, ok (true / false / null = could not check here), detail, fix}], next_step, installed?}. Use it first when vw_ping fails; vw_ping is the live test that this one deliberately does not do. Not checked here: whether 'MCP Run Job' is in a menu and the macOS Automation permission.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "vw_doctor"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fix | No | False (default): only report. True: also remove stale job and result files and, when the bridge is missing or outdated, install it into the user's Vectorworks Plug-ins folder (the only file written outside this server's own folder); Vectorworks must then be restarted once. |