Skip to main content
Glama
nguyenduyhust

sketchup-mcp

by nguyenduyhust
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to sketchup-mcp

No user-submitted related servers found.

    Related Servers

    • Hueflow SketchUp MCP

      hueflowstudio
      A
      license
      A
      quality
      C
      maintenance
      Connects Claude AI to SketchUp, allowing you to create and modify 3D models via natural language commands.
      21
      7
      MIT

    • sketchup-mcp2

      zinin
      A
      license
      A
      quality
      A
      maintenance
      Connects SketchUp to Claude AI through the Model Context Protocol, enabling prompt-assisted 3D modeling, scene manipulation, and woodworking joinery operations.
      22
      18
      MIT

    • SketchupMCP

      mhyrr
      A
      license
      B
      quality
      F
      maintenance
      Connects Sketchup to Claude AI through the Model Context Protocol, allowing Claude to directly interact with and control Sketchup for prompt-assisted 3D modeling and scene manipulation.
      10
      409
      MIT

    • SketchupMCP

      piexl
      A
      license
      B
      quality
      D
      maintenance
      Enables direct interaction and control of SketchUp through Claude AI using the Model Context Protocol and a TCP socket connection. It allows for prompt-assisted 3D modeling, component manipulation, and the execution of arbitrary Ruby code within the SketchUp environment.
      10
      MIT

    • BlenderMCP

      mikeysrecipes
      A
      license
      B
      quality
      D
      maintenance
      Connects Blender to Claude AI through the Model Context Protocol (MCP), enabling prompt-assisted 3D modeling, scene creation, and manipulation.
      17
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (selection, CRUD, materials, export). The three joint creation tools are similar in structure and verb, differing only by joint type, which could be ambiguous for agents unfamiliar with woodworking terminology.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, such as create_component, delete_component, export_scene. Even eval_ruby is verb_noun, and joint tools consistently use create_<joint_type>, making the naming highly predictable.

    Tool Count5/5

    10 tools is within the ideal 3-15 range. Each tool serves a distinct purpose, and the three joint tools represent specific sub-types rather than redundant operations. eval_ruby provides a general escape hatch, so no tool feels unnecessary.

    Completeness4/5

    The set covers core component lifecycle (create, delete, transform, set material), selection, scene export, and specialized joints. Missing a direct get_component or list_components operation is a minor gap, but get_selection and eval_ruby can bridge it, so most workflows are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources