sweethome3d-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_projectA | Create a .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not create multi-level homes or add furniture beyond the optional 4-wall rectangle footprint. Example: create_project(project_path='house.sh3d', name='House', width=800, height=600) |
| add_wallA | Add a wall to a .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not create rooms or resolve unsupported multi-wall junctions beyond the documented pairwise join model. Example: add_wall(project_path='house.sh3d', x1=0, y1=0, x2=500, y2=0) |
| add_roomA | Add a room polygon to a .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not infer walls, repeat the closing point, or auto-split overlapping rooms. Example: add_room(project_path='house.sh3d', points=[(0,0),(500,0),(500,400),(0,400)], name='Kitchen') |
| add_furnitureA | Add furniture to a .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not bind doors or windows to walls and cannot invent a missing 3D model or unsupported catalogue entry. Example: add_furniture(project_path='house.sh3d', catalog_id='eTeks#chair', x=120, y=240, rotation=90) |
| add_dimensionA | Add a dimension line to a .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not snap to existing geometry or infer offsets from nearby walls. Example: add_dimension(project_path='house.sh3d', x1=0, y1=0, x2=500, y2=0, offset=20) |
| list_elementsA | List editable elements in a .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not modify the archive or canonicalize element order. Example: list_elements(project_path='house.sh3d', kinds=['walls','rooms']) |
| export_projectA | Finalize and rewrite a .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not export OBJ, PNG, SVG, or any format other than .sh3d. Example: export_project(project_path='house.sh3d', destination_path='house-final.sh3d') |
| open_referenceA | Inspect a reference .sh3d file and populate the in-process furniture catalogue cache. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not modify the sample archive or copy any content into another project. Example: open_reference(sample_sh3d_path='sample.sh3d') |
| validate_projectA | Validate an existing .sh3d project. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not modify the archive or rewrite canonical order. Example: validate_project(project_path='house.sh3d') |
| delete_elementA | Delete an editable element from a .sh3d project by id. Lengths are in centimetres and rotations in degrees. The plan coordinate system uses y increasing downward. This tool does not delete unsupported tags or repair geometry beyond clearing inbound wall join references to a deleted wall. Example: delete_element(project_path='house.sh3d', element_id='wall2') |
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
Each tool targets a distinct action/resource: validate, reference loading, project creation, four add operations for different element types, listing, export, and deletion. The only possible overlap between validate_project and open_reference is clarified by their stated purposes, so an agent can reliably select the correct tool.
All tools follow a consistent verb_noun pattern in snake_case: validate_project, create_project, add_wall, add_room, add_furniture, add_dimension, list_elements, export_roject, delete_element. The naming makes both the action and the target clear with no style mixing.
Ten tools is a well-scoped size for a .sh3d authoring server. Each tool covers a distinct operation without redundant helpers or unnecessary bloat.
The set covers project creation, element addition, listing, deletion, validation, and export, but it lacks any update or modify operation for existing elements such as moving a wall, resizing furniture, or editing a room. Agents can only work around this by deleting and recreating elements, which is a notable lifecycle gap.