Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to rhino-mcp

No user-submitted related servers found.

    Related Servers

    • RhinoMCP

      reer-ide
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Rhino and Grasshopper to Claude AI via the Model Context Protocol, enabling prompt-assisted 3D modeling, scene manipulation, and control through tools like object creation, layer management, and code execution.
      27
      MIT

    • GOLEM-3DMCP-Rhino-

      TheKingHippopotamus
      A
      license
      Not graded
      quality
      B
      maintenance
      GOLEM-3DMCP implements the Model Context Protocol to give AI agents direct, programmatic control of Rhino 8 — create geometry, run booleans, drive Grasshopper, capture viewports, and execute arbitrary Python scripts, all through natural language. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible host.
      14
      MIT

    • HMK Pilot — MCP for Revit,

      hmertkaramann
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Revit, AutoCAD, Civil 3D and Navisworks (2023–2027): 340+ read/write actions, one-click setup for Claude, ChatGPT/Codex and Cursor, runs locally. Commercial, free 14-day trial.
      2
      -

    • AutoCAD MCP

      codesknight
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients like Claude Desktop to control AutoCAD through natural language commands using the Model Context Protocol.
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.5/5.0

    Scored across 542 tools

    Disambiguation1/5

    Dozens of tools appear to do the same thing: rhino_box and rhino_cmd_box, rhino_sphere and rhino_cmd_sphere, rhino_boolean_union and rhino_cmd_boolean_union, rhino_execute_python and rhino_run_python, plus many overlapping render/capture tools. An agent cannot reliably tell which variant to call without extensive inferencing.

    Naming Consistency2/5

    The rhino_ prefix and mostly snake_case naming provide some consistency, but conventions are mixed across what look like multiple API generations: rhino_cmd_* coexists with direct rhino_* calls, run_* coexists with execute_*, sel_* coexists with object_select, and some pairs reverse verb order (rhino_set_view vs rhino_view_set, rhino_set_display_mode vs rhino_display_mode_set). The gh_* tools add a second naming world.

    Tool Count1/5

    542 tools is an extreme mismatch for a coherent MCP surface, even for a broad CAD application. The count is inflated by large numbers of duplicate and near-duplicate operations rather than by genuinely distinct capabilities.

    Completeness4/5

    The set covers an unusually broad range of Rhino domains: primitives, curves, surfaces, meshes, SubD, booleans, transforms, layers, materials, rendering, annotations, blocks, BIM, analysis, import/export, and Grasshopper. There are minor gaps such as curve-level fillet/chamfer and some bridge-only limitations, but the generic rhino_run_command and rhino_execute_python tools let agents work around most omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources