CHOOSING A WORKFLOW
FORM and Zoo: two ways to bring AI into CAD.
FORM connects your chosen compatible AI client to a browser CAD workspace through a hosted MCP endpoint. Zoo Design Studio includes Zookeeper, its conversational CAD agent, and uses KCL for native CAD projects. Choose based on the modeling operations, source representation, and exchange formats your workflow requires.
Compare the workflow you need.
This comparison is written by FORM and describes documented capabilities. It is not an independent review or a head-to-head performance test. Competitor documentation was checked on September 20, 2026; confirm changing product details with the linked sources.
Start with three questions: Where should your assistant work? What must remain editable? Which format does the next person or application need? Those answers are more useful than a universal “best AI CAD” label.
How do the approaches differ?
| Decision | FORM | Zoo |
|---|---|---|
| AI workflow | Your compatible external assistant calls FORM’s tools. | Zookeeper is integrated into Zoo Design Studio. |
| Source to keep | FORM JSON with source shapes, parameters, and transforms. | KCL, Zoo’s native CAD project language. |
| MCP access | A hosted endpoint relays operations to your open browser workspace. | Zoo also documents a Zoo-MCP server for external agents. |
| Rhino handoff | 3DM with native supported geometry and explicit mesh fallbacks. | Evaluate the exchange format supported by your Zoo and Rhino workflow. |
| STEP requirement | No direct STEP import or export today. | Zoo documents STEP support. |
| Evidence to inspect | The chair source, export report, and FORM AI benchmark. | Zoo’s documentation, research, and Aquarium model gallery. |
Sources: Zoo’s Zookeeper announcement, MCP announcement, documentation, and Aquarium gallery. FORM’s export details are explained in the 3DM guide.
When is FORM worth trying?
Try FORM when you want to work from a compatible AI assistant you already use, inspect changes in a browser, and retain FORM’s editable source. It is also an option for exploring supported NURBS geometry before a 3DM handoff.
Run a small real task first. Check that the browser workflow, available operations, and export representations meet your needs. FORM’s faceted solid operations and current NURBS scope should not be mistaken for a full mature CAD feature set.
When should Zoo be on your shortlist?
Evaluate Zoo if you want an assistant integrated with its modeling environment, a KCL-based project workflow, or documented STEP support. Use its official documentation and a trial of your own part to check the specific features you need.
MCP alone is not a distinguishing advantage: both products expose tools to agents. Compare how each workflow handles inspection, revisions, errors, and your preferred model’s connection requirements.
How can you compare them fairly?
- Write one brief with explicit units, dimensions, required edits, and an export format.
- Record the assistant, settings, time limit, and allowed human help in each workflow.
- Keep every attempt, including failures. Repeat the task instead of selecting a single attractive result.
- Inspect the exported files in the intended destination, then make the same dimensional revision in both workflows.
- Compare the result against your requirements, along with time and any measured cost.
FORM’s public benchmark measures AI models using FORM’s tools on one defined task. It does not establish that FORM outperforms Zoo. For work that must stay in an existing Rhino document, also consider the Rhino MCP options.
Written by the FORM team. Product details can change; the linked references and current workspace describe the available workflow. Tell us if something needs correcting.