The Model Context Protocol (MCP) is introducing a structurally different interaction model for Rhino-based workflows. Rather than an AI assistant generating code for manual execution, an MCP-connected AI issues commands directly into a live Rhino session — creating geometry, managing layers and blocks, and executing RhinoScript operations based on natural-language specification.
Beyond Core Rhino: Plugin-Level Data Access
Many Rhino plugins attach data directly to objects via User Text or custom attribute fields — VisualARQ parameters, LandsDesign plant records, and similar plugin metadata are typically stored this way. This makes them comparatively easy to query via MCP: an AI assistant can read object attributes directly through Rhino's standard API without bespoke access to each plugin's internal SDK, provided the data is exposed as User Text rather than locked inside a proprietary object type.
VisualARQ objects carry parametric and schedule data — wall types, door and window parameters, storey assignments. An MCP-connected AI could query this directly, pulling schedules or flagging objects with missing storey assignments, without manually opening schedule tables.
LandsDesign holds plant species, quantities, and landscape schedule data. MCP tooling querying these records directly would allow conversational generation of planting schedules or material take-offs.
The same pattern extends to Bongo (animation parameters), Bella Render (material and render settings), and any plugin exposing data through accessible object attributes.
Collision Detection Across Assembled Workfiles
As separate workfiles — structural, MEP, architectural, or component-level models — are merged into a single assembly, an MCP-connected AI can run geometric intersection checks across defined object sets, flagging overlaps and reporting them by layer, block instance, or source file. This turns a typically manual visual scan, or a separate dedicated clash-detection tool, into a conversational query run directly within Rhino — particularly valuable for teams without access to dedicated BIM coordination software.
2D Dimensioning via MCP
Automated 2D dimensioning is another practical application. Once a model is laid out for documentation — plans, elevations, or fabrication drawings — an MCP-connected AI can be instructed to place linear, angular, and radial dimensions programmatically, based on object geometry or selected reference points, rather than the user placing each dimension manually in layout space. This extends naturally to VisualARQ documentation views, where dimension styles and annotation standards are often firm-specific: the AI can apply consistent dimensioning logic (offset distances, layer assignment, text style) across a full drawing set in one pass. For repetitive fabrication drawings — component families, jewellery settings, panelised assemblies — this can meaningfully reduce the manual annotation burden, provided dimension placement rules are clearly specified upfront.
How Realistic Are These Features?
Plugin attribute querying is genuinely straightforward where data is stored as Rhino User Text — this uses standard RhinoCommon calls with no plugin SDK required. Deeper access into proprietary object types (rather than User Text) needs the plugin's own SDK, which varies in maturity between vendors. Clash detection is arguably not even an AI-dependent feature — Rhino's built-in geometry intersection functions handle this natively; MCP simply adds a conversational front-end. Dimensioning placement is mechanically simple via the API, but getting an AI to choose sensible placement matching a firm's drafting standards, rather than just being technically capable of placing a dimension, requires clear rules to be specified upfront.
Current Reality
Plugin-level querying, clash detection, and automated dimensioning are all considerably less mature in current rhino-mcp implementations than core Rhino geometry operations. Object-attribute querying is readily achievable where plugins store data as User Text; clash detection and dimensioning workflows typically require custom development, and dimension placement logic in particular needs careful specification to match professional drawing standards.
Strategic Opportunity
A firm with deep knowledge of plugin data structures, assembly workflows, and documentation standards is well positioned to build MCP tooling that turns schedule extraction, clash detection, and dimensioning into conversational, on-demand tasks.
New to Rhino MCP? Start with our overview of what it is and how it works. If you're ready to install the platform yourself, see our step-by-step installation guide.