sketchup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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 |
|---|---|
| create_componentC | Create a new component in Sketchup |
| delete_componentB | Delete a component by ID |
| transform_componentC | Transform a component's position, rotation, or scale |
| get_selectionB | Get currently selected components |
| set_materialC | Set material for a component |
| export_sceneC | Export the current scene |
| create_mortise_tenonC | Create a mortise and tenon joint between two components |
| create_dovetailC | Create a dovetail joint between two components |
| create_finger_jointB | Create a finger joint (box joint) between two components |
| eval_rubyB | Evaluate arbitrary Ruby code in Sketchup |
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 10 tools
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.
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.
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.
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.