RhinoAI connects Rhino and Grasshopper to AI assistants such as Claude, GitHub Copilot, Codex and Gemini, so you can describe geometry in plain language and have it built in your modelling window. It's a free, official tool from McNeel — but a live connection between an AI assistant and a CAD application has more moving parts than a typical plugin, and most setup problems trace back to the same handful of causes.

One note on names: RhinoAI previously shipped as the Rhino MCP Platform, and the installer in Rhino's Package Manager still uses that earlier name.

This guide walks through the errors we see asked about most often, with fixes drawn from McNeel's official troubleshooting documentation and the Rhino Discourse AI category.

Before You Start: What You're Actually Installing

Rhino MCP has three parts, and knowing which one has failed is half the diagnosis:

  1. The Rhino plugin — installed from within Rhino via Tools → Package Manager (search for "Rhino-MCP-Platform").
  2. The router — the RhinoAI server does not connect directly to Rhino. It routes commands through a separate process, which is what lets your assistant start Rhino, load plugins and test commands.
  3. The connector in your AI assistant — for example, the Rhino3d extension listed in Claude Desktop's Settings → Extensions.

If your assistant "can't see" Rhino, one of those three isn't talking to the others.

RhinoAI Not Connecting at All

The most common cause is simply that the connection wasn't made on startup, before your conversation began. In order:

  • Quit and reopen your AI assistant — the handshake with the router happens at launch.
  • Confirm the plugin is genuinely installed: in Rhino, open Tools → Package Manager and check that Rhino-MCP-Platform appears in your installed list.
  • In Claude Desktop, open Settings → Extensions and confirm the Rhino3d connector is listed as connected.

"Cannot Find mcpconnect" After Installing

This error means the plugin installed, but the connector on the assistant's side didn't. The RhinoAI package and the connector are installed as separate steps — check the extension list in your assistant for the Rhino entry and complete that side of the setup before retrying.

"Rhinomcp.rhp Initialization Failed"

This is a Rhino-side load failure. It has been reported on specific service releases of Rhino 8 on Windows 11 — the practical fix is to update Rhino to the latest release (Menu → Help → Check for Updates) and restart. Plugin-side load errors that persist across a service release update are worth reporting on the RhinoAI GitHub so the package gets patched.

The Assistant Says It Did Something, But Nothing Appeared

Nothing is broken here — you're just not looking at the result:

  • Multiple Rhino windows open? The assistant may have edited a different document. Check the window titles.
  • Geometry far from the origin? Run View → Zoom → Zoom Extents.
  • Check the Layers panel. The new geometry may have been placed on a layer that's hidden.

Plugin Missing from the Package Manager

Two platform limitations are worth knowing before you troubleshoot further: RhinoAI does not support .NET Framework versions of Rhino, and it does not support Intel Macs. On a supported machine, make sure Rhino is updated to the latest release before searching the Package Manager again.

Grasshopper 2 Tools Not Responding

Grasshopper 2 tooling (the gh2_ tools) requires the Rhino WIP/BETA release, not Rhino 8. The router also defaults to Rhino 8. If you want the assistant to drive a different version, point it there explicitly: in Claude Desktop, open the connector's settings and change the version from 8 to 9; in Claude Code or a custom MCP config, add "args": ["-v", "9"] to the rhino entry in your MCP settings.

Long Conversations and Assistant Credits

RhinoAI conversations can consume your AI assistant's usage allowance faster than a chat-only session, because every step sends file and geometry context. Keeping sessions scoped — one modelling task per conversation — reduces both credit burn and the chance of the assistant losing the thread of a long session.

Where to Get Help

  • McNeel Discourse, AI category — the most active place for RhinoAI questions; McNeel staff participate.
  • GitHub issues — for reproducible bugs in the RhinoAI package itself.
  • CADWAX — we don't build RhinoAI, but if a troubleshooting step reveals a problem with your Rhino licence or activation, contact us and we'll sort that side out.

Related Reading

Get Rhino from CADWAX

Setting up AI workflows in your practice?

CADWAX supplies Rhino 3D licences to professional studios across the UK, with same-day email delivery. Contact us for advice on licence options and AI-assisted workflows.

Browse Rhino Licences Contact Us
Back to blog