SketchUp MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKETCHUP_MCP_HOST | No | Host used for the server connection. For the included bridge, keep the local address (127.0.0.1). | |
| SKETCHUP_MCP_PORT | No | Port used for the server connection. The included bridge listens on 127.0.0.1:9876 by default. | |
| SKETCHUP_MCP_CACHE | No | Directory where the simulated scene data is stored. Defaults to ~/.cache/sketchup-mcp. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
SketchUp integration — conecta IA a SketchUp vía TCP 9876 o modo mock Linux. Herramientas para crear, transformar, materializar y evaluar Ruby.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sketchup_statusA | Estado de conexión a SketchUp + info mock. Usa esto primero. |
| get_scene_infoB | Info de la escena actual — intenta SketchUp, fallback a mock. |
| get_selectionC | Entidades seleccionadas (mock o SketchUp). |
| get_selected_componentsB | Alias de get_selection para compatibilidad con mhyrr. |
| create_componentC | Crea un componente en la escena. Tipos: cube, sphere, cylinder, face, custom. Position/size como 'x,y,z'. |
| delete_componentC | Borra componente por id o nombre. |
| transform_componentC | Mueve/rota/escala componente. Formato: 'x,y,z' para cada uno. |
| set_materialC | Aplica material/color a componente. Colores: Red, Blue, #ff0000, etc. |
| eval_rubyB | Ejecuta Ruby arbitrario en SketchUp. Si no hay SketchUp, mockea con info. |
| export_sceneC | Exporta escena mock o pide a SketchUp que exporte. Formatos: json, obj, skp, glb. |
| screenshotB | Captura de SketchUp. Requiere SketchUp vivo y SCREENSHOT_DIR configurado, si no mock. |
| clear_sceneA | Limpia la escena mock (borra todos los componentes). No afecta SketchUp vivo. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools are clearly separated by resource and action (create_component, transform_component, set_material, export_scene), so the core set is easy to navigate. However, get_selected_components is explicitly an alias of get_selection, meaning two tools have an identical purpose and an agent must guess or arbitrarily choose between them. The status/info/selection trio is also somewhat close in scope (all read-only introspection).
The dominant pattern is a clean verb_noun snake_case convention (create_component, delete_component, transform_component, set_material, export_scene, clear_scene, get_scene_info, get_selection). The deviations are the bare nouns sketchup_status and screenshot, which break the verb-first pattern but remain unambiguous and readable. No camelCase/snake_case mixing, so the set is easy to predict.
Twelve tools is comfortably in the well-scoped range for a 3D scene manipulation server, covering connection, inspection, creation, mutation, and export. Apart from the redundant alias, each tool maps to a distinct operation that earns its place. No sign of tool bloat or a thin surface.
The lifecycle is broadly covered: connect/status, inspect scene and selection, create/delete/transform components, apply materials, evaluate Ruby as an escape hatch, export, screenshot, and clear. Minor gaps remain — there is no explicit list_components or get_component-by-id tool (agents must rely on get_scene_info), and no copy/duplicate or undo operation. These are workaroundable, especially via eval_ruby.