VextCAD

Remote MCP workflow

Remote VextCAD workflow

  1. Call read_docs without arguments to see the index and engine commit.
  2. Read mcp-workflow, skill, modeling and checking in that order.
  3. Read relevant sections before choosing modeling operations.
  4. Use search_docs to find features or exact diagnostic codes.
  5. Write a complete VXL JSON document and keep your own copy.
  6. Call check_vxl with document, optional overrides and, for a document with assets, the bindings from steps 8 and 9.
  7. Fix the reported errors and repeat until ok is true.
  8. Call upload_asset for each STEP, STL or SVG input, then describe_asset to get the media_type, bytes and digest to declare in the document's assets[].
  9. Bind asset IDs to returned upload_key strings in check_vxl and start_build.
  10. With content_base64, send no more than 4 MiB of decoded bytes.
  11. Without content_base64, PUT the bytes to put_url with put_headers within 15 minutes.
  12. For STEP face selection, call inspect_asset with upload_key and import.source_units (mm or inch, required), plus optional import.heal object, import.at array and import.rotate array matching your VXL import. Then poll get_build with its build_id. No source_units default is assumed. The engine defaults heal to {"mode":"none"}, at to [0,0,0] and rotate to [], and validates their contents. Read the face table (index, surface parameters, area and one-line selector JSON). Paste a non-null selector object into direct_edit / fillet documents; read selector_note for null selectors. The first 200 faces appear in text. structuredContent.inspection contains vextcad.vxl_inspect.v1 JSON up to 64 KiB; otherwise use inspection_url / the inspect.json resource link. The engine lists at most 2000 faces and marks truncated. Inspection uses the 32 MiB STEP cap, 240-second timeout, daily build quota and running-job quota. Bind asset IDs to returned upload_key strings in start_build.assets.
  13. Call start_build with the full document and any overrides.
  14. Retain build_id; an optional idempotency_key makes retries safe.
  15. Call get_build repeatedly until status is completed or failed.
  16. Each get_build waits up to 15 seconds (default 10).
  17. Completed builds include at most two iso preview images by default.
  18. Use get_preview for iso, front, top or right views of a terminal.
  19. Inspect the images as well as the report.
  20. Download individual files from their HTTPS links.
  21. Download archive_url for the complete result bundle.
  22. Refresh expired links by calling get_build again.

CLI commands in the documentation

  • vextcad vxl inspect maps to inspect_asset followed by get_build.
  • vextcad vxl check maps to check_vxl.
  • vextcad vxl build maps to start_build followed by get_build.
  • Local vextcad vxl session commands have no remote equivalent.
  • Keep the document yourself; edit and resubmit a complete document for each revision.
  • To undo, resubmit a previous copy of your document.

Verdicts and next steps

  • RELEASE: the document's measured requirements passed on this cell.
  • HOLD: artifacts exist, but questions, requirements or measurements remain open.
  • FAILED: modeling could not complete; read the revision packet.
  • HOLD/FAILED: read revision_packet, fix, start_build again.
  • status failed indicates a service failure; inspect error before retrying.
  • This cell is development_unqualified.
  • RELEASE is not a print or engineering certification.
  • Slicing, fabrication checks and engineering decisions remain with the user.