Rhinomcp MCP Server

Connect Rhinomcp to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Rhino integration through the Model Context Protocol. The rhinomcp mcp server is what makes that connection.

What the server does

RhinoMCP connects Rhino to AI agents through the Model Context Protocol, so assistants like Claude and Cursor can model geometry, read your document, and build Grasshopper definitions for you, just by chatting.

• Describe what you want and the assistant builds it in Rhino
• It reads your document and can capture the viewport, so it works from what is actually on screen
• It scripts Grasshopper for you: finding components, wiring them, setting sliders, and solving
• A single plugin and a single config entry cover both Rhino and Grasshopper
• When you need more control, it can run native Rhino commands, RhinoScript-Python, or RhinoCommon C#

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Rhino — The Rhino tool exposed by this server
• Grasshopper — The Grasshopper tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: RHINO_MCP_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at rhinomcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Rhinomcp's toolset — Rhino, Grasshopper — is a fair guide to whether it matches your workflow.

This entry was verified against Rhinomcp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.