Cordyceps
MCP serverCommunity
A Grasshopper component that serves MCP over local HTTP, so an agent can build canvases, bake geometry and render in Rhino. By Brook Stalley.
107 starsUpdated 2 months agoGitHub data from 5 Nov 2026
At a glance
- Type
- MCP server
- Works with
- Rhino 3D & Grasshopper
- How it connects
- Drives a running copy of the tool
- Access
- Can modify models
- Tool versions
- Rhino 8.21 or later (.NET 8)
- Operating systems
- Windows, macOS
- Needs a Rhino 3D & Grasshopper licence
- Yes
- Transport
- Remote (HTTP)
- AI clients documented
- Claude Desktop, Claude Code, Cursor, VS Code
- Licence
- MIT
- Language
- C#
What it can do
- Adds Grasshopper components, wires them, sets values and manages groups on the open canvas.
- Bakes geometry to Rhino, manages layers, applies PBR materials and renders scenes.
- Runs inside Grasshopper itself, so there is no separate Python process; you drop the component on the canvas to start it.
- Tools can also be called from your own scripts through any MCP client library, without an AI.
Limitations
- Claude Desktop needs the mcp-remote bridge and Node.js, because the server only speaks HTTP.
- The server runs only while the Cordyceps component is on an open canvas.
Install
In Rhino 8 run PackageManager, search for Cordyceps, install it and restart Rhino. Then drop the Cordyceps component (Params > Util > Cordyceps) on the canvas; it listens on port 26929.claude mcp add --transport http cordyceps http://127.0.0.1:26929/mcp{
"mcpServers": {
"cordyceps": {
"command": "npx",
"args": ["-y", "mcp-remote", "http://127.0.0.1:26929/mcp"]
}
}
}MCP servers and skills run code on your computer. Review the source before installing.
AI-generated models, drawings and results must be checked by a qualified engineer before use.