Vextor
中文 Sign in

Remote MCP workflow

Remote Vextor 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 and optional overrides.
  7. Fix the reported errors and repeat until ok is true.
  8. Declare required assets in the document.
  9. Call upload_asset for each STEP or STL input.
  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. 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

  • vextor vxl check maps to check_vxl.
  • vextor vxl build maps to start_build followed by get_build.
  • Local vextor 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.