Skip to content

MCP

RhinoArtisan MCP

Connect RhinoArtisan to your favorite AI assistant. RhinoArtisan exposes a local MCP server that lets compatible AI assistants work with RhinoArtisan directly inside Rhino — and not just for design. The same connection covers the whole RhinoArtisan workflow: designing, manufacturing checks, weights, pricing and reporting.

The Model Context Protocol (MCP) is the open standard the whole AI industry is converging on — Anthropic, OpenAI, Google and Microsoft all speak it, and McNeel is building RhinoMCP on the same standard for Rhino itself. RhinoArtisan MCP brings Artisan’s jewelry tools into that world, and the two servers work side by side: connect both and your assistant gets Artisan’s jewelry tools next to McNeel’s Grasshopper and scripting tools. See Grasshopper + MCP for building ArtisanGrasshopper graphs by conversation.

Works with

Connect from the AI assistants you already use:

  • Claude Desktop — Anthropic’s Claude app, on every plan; a downloadable connector (or one command in Rhino) connects it
  • ChatGPT — through OpenAI’s Secure MCP Tunnel
  • Google Gemini — through Antigravity, Google’s agentic IDE

And from the tools developers live in:

Prefer to run a model on your own machine? LM Studio works too — with weaker results than a frontier model, serious hardware needs, and no support from us. Read the caveats before you try.

What this looks like

With Rhino and RhinoArtisan running, you ask your AI assistant:

“Add an oval 2-carat ruby at the origin and a half-carat round diamond on each side.”

The assistant discovers Artisan’s tools and the gems appear in your viewport — created by the exact same pipeline as the QuickGems tool, on the right layers, with the right materials, sized correctly for their carat weight.

And design is only the beginning. RhinoArtisan MCP is built on the same automation surface that powers every Artisan module, so the same conversation extends across your whole workflow:

“How much does this ring weigh in 18k gold — and what would it cost?”

“Is this model ready to print? Export the STL and prepare the production report.”

The whole workflow is there today — gems and every setting, shanks, pavé, booleans, relief, weight and price, printability, sprues, reports, exports, renders. The assistant can also look at your viewport, work with whatever you have selected, and script anything the typed tools don’t cover through the same Scripting API that powers Flow Studio. See Tools for the full list.

What’s new in 7.0.0.10

  • Presets. Build from a saved element with element on about 25 create tools, apply one to an existing object with edit_object {"element": …}, store an object as a new preset with save_element, and organize the library with manage_elements (rename, duplicate, favorite, delete, export and import bundles).
  • Profile library. export_asset_curve draws a profile so the assistant can look at it before choosing it. manage_assets renames, duplicates, sets the default and deletes. Every *profile argument also accepts "id:<n>".
  • Smart Profiles. create_smart_profile sweeps profile sections along a curve, and edit_object edits them section by section.
  • Editable components. Bails, named pendants, bangles, beads, charms, links, milgrain, ropes, 3D textures and ring engravings can be edited after creation with edit_object, by path ({"top_profile.width": 4.5}).
  • Richer edit_object. It now calls a handle’s edit methods too (set_section, add_section, fit_to_gem…). describe_object_parameters lists them as calls.
  • Cutters that fit the stone. create_cutters takes fit_to_gem for fancy cuts. A redesigned create_bail exposes every option of the Bail panel.
  • Panels. close_panel closes a command panel that run_command left open.

The Tools page lists everything.

How it works

AI assistant (Claude, ChatGPT, Gemini, …)
    │  Model Context Protocol (localhost only)
    ▼
RhinoArtisan MCP bridge  ──►  RhinoArtisan  ──►  your document
  • Included with RhinoArtisan 7 — nothing extra to install.
  • The bridge runs entirely on your machine: it listens on localhost only and is never exposed to the network.
  • Tools execute through RhinoArtisan itself — same pipelines as the UI tools, same licensing, same friendly error messages.
  • Read-only tools (listing gems, discovering valid shapes and materials) are separated from tools that modify the document, so assistants can explore safely before they act.

Why it matters

A jeweler’s AI assistant is only as good as the tools it can use. MCP turns RhinoArtisan into a first-class tool for any capable agent — today for early experiments, tomorrow as the standard way AI works alongside professional software.

Ready to try it? Head to Getting Started, then see Tools for what the toolset covers today. Have a workflow in mind? Talk to us.