Skip to main content
Glama
kbangaru-cyber

RhinoMCP

by kbangaru-cyber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to RhinoMCP

No user-submitted related servers found.

    Related Servers

    • Rhino MCP

      quocvibui
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered 3D modeling in Rhino 8 through 135+ tools for geometry, transformations, booleans, layers, materials, and more, using natural language.
      6
      MIT

    • 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

    • revit-mcp

      Mohamed-Elnahla
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Autodesk Revit to query project data, manage elements, and execute generated code via the Model Context Protocol. It provides full compatibility with GitHub Copilot and Claude to automate BIM modeling workflows.
      13
      65 npm
      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.
      13
      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.7/5.0

    Scored across 105 tools

    Disambiguation2/5

    Most geometry creation/editing tools are distinguishable by their object type and operation, but the set contains direct duplicates (set_material/assign_material, duplicate_border/get_naked_edges) and overlapping checks (check_objects/check_mesh). With 105 tools, an agent must navigate many near-synonyms and the line between trim/split and copy/array is not always obvious.

    Naming Consistency4/5

    Tools consistently use the rhino_ prefix with snake_case verb_noun operations, making groups like create_* and get_* easy to scan. Minor inconsistencies exist (scene_info is noun-only, distance/intersect have no target, set_material vs assign_material) but they do not undermine the overall pattern.

    Tool Count1/5

    At 105 tools, this is an extreme mismatch for an MCP tool surface, far beyond the 25+ threshold where selection overhead becomes severe. Many narrow variants (e.g., point vs points, multiple sweep/loft surface creators) could be consolidated without losing capability.

    Completeness4/5

    The server covers the full Rhino modeling lifecycle: primitive creation, editing, transformations, booleans, analysis, layers, materials, blocks, Grasshopper, and file I/O. Minor gaps like layer rename/lock or block definition removal exist, but the universal run_python and run_command escape hatches prevent dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources