SketchupMCP
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
Server capabilities have not been inspected yet.
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 distinct purposes, such as creating specific joint types or managing components. However, create_component and transform_component could be slightly ambiguous if an agent needs to modify a component's geometry versus its transformation, but descriptions clarify their roles.
All tool names follow a consistent verb_noun pattern, using snake_case throughout. Examples include create_component, delete_component, and export_scene, making them predictable and easy to parse.
With 10 tools, this server is well-scoped for Sketchup automation, covering joint creation, component management, scene export, and Ruby evaluation. Each tool serves a clear purpose without redundancy.
The toolset provides good coverage for basic Sketchup operations, including CRUD for components and specific joint types. Minor gaps exist, such as no tool for listing all components or updating joint properties, but core workflows are supported.