Hosted Vextor · public preview
Your agent describes the part in VXL, a compact JSON language that holds both the geometry and the requirements. Vextor builds it on the server as exact CAD (STEP) or a printable mesh (3MF, STL), then measures the result against every requirement in the document.
"requirements": [
{ "id": "large_teeth",
"kind": "gear_teeth",
"subject": "large",
"module": "1.5",
"pressure_angle": "20",
"teeth": "2 * pinion_teeth",
"thinning": "backlash / 2", … },
{ "id": "large_bore",
"kind": "hole",
"subject": "large",
"diameter": "6.3",
"through": ["0", "8"], … },
…
]
RELEASE
29 of 29 requirements pass
Large gear, as built · Build 8caa9029
The agent reads the VXL docs through MCP and writes one document: parameters, sketches, solid and mesh operations, and the requirements the part must meet.
A static check answers in about a second. The build runs the Vextor engine on the server: exact parts come out as STEP, meshes as 3MF and STL, each with rendered views.
RELEASE when every requirement was measured on the built geometry and passed. HOLD or FAILED comes with a revision packet that tells the agent what to change before it builds again.
RELEASE means the part matches its own measured requirements. It is not a print or engineering certification.
Four documents from the Vextor examples, built here without edits. Every number comes from the build's own report.
Seven parts as exact B-Rep: base, two gears, two caps, an M3 screw and nut. The checks cover tooth geometry, bores, mounting holes, journal diameters and the base envelope.
VXL sourceBuild 8caa9029
The C-frame of the screw clamp example: an extruded profile with rounded edges and a threaded bore for the screw. The screw, knob and pads are separate documents.
VXL sourceBuild 44c09b9e
The organic body of the owl example, before its sculpting pass. The sculpted finish starts from an uploaded input, so it is not shown here.
VXL sourceBuild cac20e9f
A shallow organic tray with leaf-vein relief, checked for printability.
VXL sourceBuild 35e7c5ff
Vextor runs as a remote MCP server. Your agent signs you in through the browser, then reads the docs, checks and builds parts, and downloads the files. Nothing to install.
MCP server
https://mcp.vx.fibonax.org/mcp
Other clients: add the URL above as a remote MCP server (Streamable HTTP). Sign-in uses OAuth.
Create an API key in the portal and call the HTTP API, or use the Python client. HTTP API guide
claude mcp add --transport http vextor https://mcp.vx.fibonax.org/mcpThen run /mcp in Claude Code and authenticate vextor.
codex mcp add vextor --url https://mcp.vx.fibonax.org/mcp
codex mcp login vextorCapacity is small during the preview, so builds queue when the service is busy.
We are looking for a few design partners who need functional parts generated at scale: product configurators, jigs and fixtures, enclosures, replacement parts. Tell us what you build.