RHINO WORKFLOWS
Rhino MCP: choose where your AI should model.
Rhino MCP connects an AI assistant to tools that operate inside Rhino. McNeel’s Rhino MCP Platform and the community RhinoMCP project are two options. FORM is a separate browser CAD workspace with its own hosted MCP connection; it can export 3DM files for Rhino, but it does not control Rhino or Grasshopper.
Which Rhino MCP project do you mean?
The search phrase “Rhino MCP” can refer to different projects. Check the publisher and setup instructions before installing one.
- McNeel’s Rhino MCP Platform: the RhinoAI site describes McNeel’s connection between AI assistants and Rhino or Grasshopper. Start with its official getting-started guide, which assumes an installed and licensed copy of Rhino.
- Community RhinoMCP: Jingcheng Chen’s project connects an MCP server to a plugin running in Rhino. Its repository documents Rhino 8 support, installation, document inspection, modeling, and Grasshopper workflows.
- FORM: a separate CAD workspace that runs in the browser. Use its hosted MCP endpoint when the work should happen in FORM.
These projects have different installation requirements and geometry engines. Sharing the MCP protocol does not make their commands or documents interchangeable.
Should I use Rhino MCP or FORM?
| Your task | Starting point | Why |
|---|---|---|
| Edit an existing Rhino document | A Rhino MCP integration | The assistant works in the application that owns your document. |
| Build a Grasshopper definition | A Rhino integration with Grasshopper tools | FORM does not execute Grasshopper definitions. |
| Explore geometry in a browser | FORM | The modeling workspace runs without a Rhino installation. |
| Start in FORM, continue in Rhino | FORM → 3DM → Rhino | Supported curves, surfaces, and primitive solids have native representations. |
If you need Rhino’s broader surfacing, trimming, finishing, or plugin workflows, evaluate an integration that operates in Rhino. FORM is useful when you want an agent-driven browser workspace and can work within its current modeling scope.
Can I open a FORM model in Rhino?
Yes. Export a 3DM file from FORM and open it in Rhino. NURBS curves stay curves, and NURBS patches and lofts become editable NURBS surfaces. Boxes, spheres, and cylinders can become BRep solids. Other current shape types, including boolean results, export as meshes.
The export retains names, layers, colors, and millimeter units. Review the representation report to distinguish native geometry from mesh fallbacks. A surface without thickness remains an open surface after export.
FORM cannot currently import an edited 3DM file. Keep your FORM JSON source and treat this as a handoff to Rhino. The step-by-step export guide explains what transfers and what to inspect.
Is FORM a Rhino plugin or a full Rhino replacement?
No. FORM has its own TypeScript geometry kernel and uses an optional browser-local 3DM writer for export. Supporting the 3DM file format does not provide Rhino’s entire modeling engine.
FORM supports editable NURBS definitions and a bounded set of solid operations. It does not currently implement Grasshopper, SubD, arbitrary NURBS trimming, general fillets, or STEP interchange. For the established Rhino feature set, consult McNeel’s feature overview.
FORM is independent of McNeel, RhinoAI, and the community RhinoMCP project. The names here identify compatible workflows and comparison options, not a partnership.
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.