SketchUp MCP Chinese Integration

Problem

When Claude or another MCP assistant needs to operate SketchUp directly, prompts, scene components, materials, exports, and Ruby extensions are often scattered across separate tools. This Skill connects them through the Model Context Protocol, allowing AI to read the current scene, create or modify components, apply Chinese color names, and run modeling tasks such as woodworking joints and boolean operations. For Chinese users, it also uses millimeters by default and supports names like 红色, 绿色, and 青色, reducing parameter conversion during local modeling.

How It Works

• Bidirectional communication: the SketchUp extension starts a local TCP server, default port 9876, and exchanges JSON commands with status / result responses.
• MCP server: the Python server sketchup_mcp/server.py translates AI tool calls into actions SketchUp can execute.
• Core tools: includes get_scene_info, get_selected_components, create_component, transform_component, set_material, export_scene, and eval_ruby.
• Specialized modeling: supports create_mortise_tenon, create_dovetail, create_finger_joint, and boolean_operation, which is useful for generating structural sketches or woodworking layouts from prompts.

Boundaries

It fits local AI-assisted modeling in the SketchUp desktop environment, especially rapid creation of boxes, cylinders, spheres, editing selected components, and exporting skp, obj, dae, stl, or png. The SketchUp extension and MCP server must both be running; complex requests can time out, so splitting work into smaller steps is recommended; eval_ruby provides advanced control but errors may surface in the SketchUp Ruby console.