Garden Design MCP Server
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.
Garden Editor MCP. Call get_design_guide once at the start: it holds the core rules, how to talk with the owner, the guided set-up of a new garden and the whole workflow. Check get_full_state first. Metres; x = east, y = south (north-up).
The owner reads your replies in their chat window, the editor open beside it, and sees each change on the plan as you make it. So every reply:
a few short lines: what you did in one sentence, then only what needs the owner — a conflict, a guess to confirm;
at most ONE question, the most important, last, on its own line in bold; the next one after they answer — never a list of questions or a menu of topics;
no tables, headings, ids (pin_15, zone_3), coordinates, pass or step numbers or tool names; say "the gate", "the terrace". Ids, figures and the full record go in the journal (
set_garden_description);act before asking: make your best guess, show it, then ask them to confirm or correct it.
"Stop for the user's sign-off" means: end the reply with the question whether to keep it as it is, and wait for their message.
Write everything the owner reads — replies, the short notes between tool calls, labels, notes, the journal — in the language they write to you in.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocode_addressA | Find an address anywhere in the world (OpenStreetMap Nominatim). Returns {address, lat, lon, countryCode}; countryCode is ISO 3166-1 alpha-2 in lower case. The land-registry tools (get_parcel_by_*, import_parcel) work only for countryCode 'pl'; elsewhere set the garden's place with set_geo_anchor and the plot's boundary with set_boundary. |
| get_parcel_by_coordinatesB | Get parcel information by WGS84 coordinates (lat/lon). Poland only: refused for a garden placed outside Poland. |
| get_parcel_by_idA | Get parcel information by parcel ID. Poland only: refused for a garden placed outside Poland. |
| get_parcel_by_addressB | Get parcel information by address (geocodes then looks up parcel). Poland only: refused for a garden placed outside Poland. |
| import_parcelA | Import a parcel as the garden's site context: sets the scheme outline, geo-anchor, and (by default) auto-loads the KIEG WMS cadastral/satellite map background so |
| import_buildingsA | Scan the imported parcel + 10 m margin via ULDK and add discovered building footprints as |
| get_site_analysisA | Measured site facts for placing pins and zones, computed from the parcel boundary and building zones (call after import_parcel + import_buildings). Returns (metres, garden coordinates): the parcel area and its edges by compass side; the user's house (largest building centred in the parcel) with each facade's compass side, length, from/to endpoints, midpoint, outward normal, whether it is a shared (party) wall, and |
| set_geo_anchorA | Set the garden's place: the real-world point (WGS84) at the editor origin. The plot becomes placed — north, sunlight and the OpenStreetMap background follow it — and the change is unsaved until save. Use it for a plot outside Poland (after geocode_address), then give the boundary with set_boundary; import_parcel sets both for a Polish parcel. |
| set_boundaryA | Set the plot's boundary from a polygon — for a plot outside Poland, one the land registry gets wrong, or the designer's measurements ("18 by 25 m"). Absolute vertices in metres, in the garden coordinates zones use (the garden's place is at 0,0; x east, y south when north is up), e.g. traced from the OpenStreetMap background in capture_preview. Replaces any boundary; the change is unsaved until save. A placed plot becomes located and the map refits around it. Returns {area (m²), plot: 'located' | 'unlocated'}. |
| set_map_backgroundA | Switch a map background under the garden on or off. 'osm' is the live OpenStreetMap map, about 100 m around the plot, turning with the garden; 'satellite' is the aerial photo of the same area (Poland only: the national orthophoto; elsewhere it answers that there is no photo) — fences, hedges, trees and paths show there, not on the street map. Both need the garden's place (set_geo_anchor or import_parcel), are loaded live and start off each time the garden opens. 'survey' is the survey map laid with set_survey_map (false hides it, true shows it again). They show in capture_preview and hide with the 'map' layer. |
| zoom_imageA | Look closer at an image the designer attached in the chat (e.g. a survey map) to place points precisely. Attached images arrive labelled "Image 1", "Image 2"…; each is a view ("1") in the pixels you see. Returns a close-up of the full-size original around a point of a view, as a new view ("1.1", "1.2"…) with its own pixels. Points for set_survey_map and map_to_garden are given on any view. Only in the editor's own chat, where images are attached. |
| set_survey_mapA | Lay a map of the land drawn to scale (survey map, site plan, sketch with its lengths) that the designer attached in the chat under the garden, as a map background. Either |
| map_to_gardenA | Where points on the laid survey map are in the garden, in metres — e.g. the plot's corners read off the map, for set_boundary. Points are given on any view of the laid map's image (see zoom_image). |
| get_geo_anchorB | Get the current geo-anchor (if set) |
| upload_reference_photoB | Upload a reference photo (house exterior, current garden). Stored in-session. The AI agent can analyze photos via its own vision capabilities. |
| get_reference_photosB | Get all uploaded reference photos for this session |
| add_pinA | Add a context pin to the garden. Returns the pin ID. Available pin types: • door — main entrance door (red) • patio_door — patio/garden door (teal) • window — window opening (blue) • gate — garden gate/entrance (green) • view_good — desirable view direction (yellow) • view_bad — undesirable view to screen (grey) |
| add_pinsA | Add multiple context pins in a single call. Returns array of pin IDs. Use this instead of calling add_pin multiple times. Available pin types: • door — main entrance door (red) • patio_door — patio/garden door (teal) • window — window opening (blue) • gate — garden gate/entrance (green) • view_good — desirable view direction (yellow) • view_bad — undesirable view to screen (grey) |
| delete_pinC | Delete a pin by ID |
| get_pinsB | Get all pins in the garden |
| get_garden_infoA | Get garden metadata: ID, name, description, rotation, boundary, object counts |
| set_garden_rotationC | Set the garden's north orientation in degrees |
| set_garden_descriptionA | Set the garden description (Markdown supported). Use as a design journal — write the brief, key decisions, rationale, current phase, and what's next. Persists across sessions. |
| capture_previewA | Capture a screenshot of the garden framed on the parcel (2 m margin), in the current view mode — switch to 2d with set_view_mode for a plan view. Returns an image you can view directly. |
| add_zoneB | Add a new zone to the garden. Returns the zone ID. Available zone types (type → default height → category): • entry — 0.3m — functional (entrance area) • relaxation — 0.5m — functional (seating, lounging) • activity — 0.3m — functional (play, sports) • utility — 0.4m — functional (compost, storage, bins) • wild — 0.6m — functional (naturalistic area) • tall_plants — 2.0m — planting (trees, large shrubs) • privacy_screen — 1.8m — planting (hedges, screening) • low_plants — 0.5m — planting (perennials, groundcover) • herbs — 0.3m — planting (herb garden) • lawn — 0.05m — planting (grass area) • path — 0.05m — infrastructure (walkways) • building — 3.0m — infrastructure (structures) • terrace — 0.2m — infrastructure (paved patio) • parking — 0.05m — infrastructure (driveway, car space) |
| add_zonesA | Add multiple zones in a single call. Returns array of zone IDs. Use this instead of calling add_zone multiple times. Available zone types (type → default height → category): • entry — 0.3m — functional (entrance area) • relaxation — 0.5m — functional (seating, lounging) • activity — 0.3m — functional (play, sports) • utility — 0.4m — functional (compost, storage, bins) • wild — 0.6m — functional (naturalistic area) • tall_plants — 2.0m — planting (trees, large shrubs) • privacy_screen — 1.8m — planting (hedges, screening) • low_plants — 0.5m — planting (perennials, groundcover) • herbs — 0.3m — planting (herb garden) • lawn — 0.05m — planting (grass area) • path — 0.05m — infrastructure (walkways) • building — 3.0m — infrastructure (structures) • terrace — 0.2m — infrastructure (paved patio) • parking — 0.05m — infrastructure (driveway, car space) |
| update_zoneA | Update an existing zone. Reshape it with |
| delete_zoneC | Delete a zone by ID |
| get_zonesA | Get all zones in the garden (editor geometry: centre + relative points; |
| get_zone_typesA | Get all available zone types with their properties (colors, default heights, labels) |
| get_objects_in_zoneA | Returns all garden objects whose center falls within the specified zone. Includes plants, buildings, and ground shapes. Useful for checking plant density, verifying placement, or listing zone contents. |
| get_zone_analysisA | Analyzes a zone's contents: object count, coverage %, planting density rating, and boundary violation warnings. Use after placing objects to validate density and spatial relationships. |
| clear_allA | Clear scene contents. Default scope='all' clears objects, zones, AND pins (matches the tool name's intent). Use scope='zones_pins' to preserve objects, or scope='objects' to preserve zones+pins. NOTE: behaviour change in this MCP version — previously this tool only cleared zones+pins regardless. Returns { success, scope, objectsCleared, zonesCleared, pinsCleared }. |
| export_stateA | Export the current state of all zones and pins as JSON |
| import_stateC | Import zones and pins from a JSON state object |
| search_productsB | Search the product catalog. Filter by layer (ground/architecture/plants), text query, or category. |
| get_categoriesA | Get product categories for a layer. Architecture and ground are flat (1-level): any returned id works directly with search_products.categoryId. Plants use a 2-level tree: this returns only the 6 top-level groups (Drzewa, Krzewy, Pnącza, Byliny, Trawy Ozdobne, Pokroje); to filter search_products by plant category you must follow up with get_subcategories() and pass a leaf id. |
| get_subcategoriesA | Get the leaf subcategories of a top-level plant category. Plants use a two-level tree (6 top-level → leaves); search_products's categoryId filter requires a leaf id. Architecture and ground are flat — calling this on their top-level ids returns []. Locale follows the editor session. |
| get_product_detailsB | Get full details for a specific product by ID |
| get_plant_infoA | Returns detailed botanical information for a plant product: characteristics (height, spread, form, foliage, flowers), requirements (soil, sunlight, hardiness), and maintenance schedule. Use this to make informed plant selection decisions. |
| get_plant_attributesA | Returns the full vocabulary of selectable plant filter values for the current viewer locale: enum lists (flowerColor, bloomPeriod, sunlight, soil, foliageType, foliageColor, maintenanceLevel, form) and observed numeric ranges (height, spread, hardiness). Call this BEFORE search_plants so you pick only valid values; values not in this vocabulary will yield empty results from search_plants. Lazy-loaded once per session and cached. |
| search_plantsA | Filter the plant catalog by botanical attributes. Returns lean records ({productId, code, botanicalName, commonName}). Call get_plant_attributes first to discover valid filter values for the current locale. Multi-value filters use OR semantics (any value matches); different filters are AND-combined. Range filters use overlap semantics (a plant's range must intersect the requested range). Capped at limit (default 25, max 100); response includes total + truncated flag. Use get_plant_info for full per-plant details after picking a candidate. Falls back to a loud error if the index is unavailable on the CDN — agents should retry name-based queries via search_products in that case. |
| get_objectsA | Get garden objects (plants, buildings, ground shapes). Default: full array. Optionally filter by layer. Pass count_only=true on large scenes to get aggregated counts ({total, byLayer, byType, byProductId}) instead of the array — avoids exceeding the tool-result token budget. |
| add_objectA | Add a garden object (plant, building, or ground shape). Type determines rendering: 'plant' for plants, 'building' for architecture, 'rectangle'/'ellipse'/'polygon'/'path' for ground shapes. For type='path', provide pathWaypoints (centerline) and pathWidth; the outline polygon is computed automatically. Supply productId OR productQuery (name search resolved server-side). Width/height are optional — if omitted, defaults from the product catalog are used. |
| add_objectsA | Add multiple garden objects in a single call. Returns array of results. Use this instead of calling add_object multiple times. Each object supports productId OR productQuery, and optional width/height. |
| update_objectA | Update a garden object's position, size, rotation, or swap its product. To swap product: pass productId or productQuery. Plants/buildings get new dimensions from catalog; ground shapes keep their shape and only swap texture. |
| delete_objectC | Delete a garden object by ID |
| update_objectsB | Update multiple garden objects in a single call. Returns array of results. Each item can swap its product with productId or productQuery, as in update_object. |
| delete_objectsB | Delete multiple garden objects by ID in a single call. Returns array of results. |
| set_view_modeA | Switch between 2D (top-down) and 3D (perspective) view |
| get_view_modeA | Get the current view mode (2d or 3d) |
| set_layer_visibleC | Show or hide a rendering layer |
| get_layer_visibilityB | Get visibility state of all layers |
| focus_onC | Focus the camera on a specific area in the garden |
| saveB | Save all changes to the server |
| undoC | Undo the last action |
| redoB | Redo the last undone action |
| get_coordinate_systemB | Get the coordinate system documentation (units, axes, scale factor). Note: 50 editor units = 1 meter, origin top-left, X rightward, Y downward, rotation clockwise degrees. |
| get_full_stateA | Get the garden state. Default: full payload (summary + zones + pins + objects + layer visibility + view mode + geo-anchor + coordinate system) — use at session start. Pass summary_only=true on large scenes to skip the heavy arrays and return just the summary block + coordinateSystem (avoids exceeding the tool-result token budget). |
| set_unitsA | Set the unit system for coordinate inputs/outputs. Default is "m" (meters). When set to "m", all spatial values (x, y, width, height, points) are in meters. When "editor", values use raw editor units (50 units = 1 meter). |
| connection_statusB | Check if the browser is connected |
| get_versionA | Returns version info for the MCP server and the connected browser editor. Use at session start to confirm you are talking to a build that supports the features you depend on (e.g. M25 plant-attribute search). Response: { mcpServer: { name, version }, editor: { version, buildTime, gitHash } | null }. The editor block is null when the browser is not connected. |
| get_design_guideA | The full design guide: step-by-step first-session workflow, how to read photos and floor plans onto facades, pin rules, the three zone passes with minimum sizes, the journal template, plant selection and verification. Call once at the start of a session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| start_design | Begin a new garden design from scratch, as the editor's guided set-up does: the site and what already exists first, then the zones and the detailing, each step signed off. |
| continue_design | Resume working on an existing garden. Reads zone notes and garden description to assess checklist gaps, then suggests next steps. |
| optimize_zones | Review and optimize zone layout. Uses density/coverage analysis, boundary checks, and spacing validation to identify issues. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Garden Info | Garden metadata: ID, name, rotation, boundary, object counts |
| Zones | All zones in the garden as JSON |
| Pins | All context pins in the garden |
| Garden Objects | All garden objects (plants, buildings, ground shapes) |
| Coordinate System | Coordinate system documentation (units, axes, scale) |
TDQS
Scored across 63 tools
Most tools have distinct domain roles, but there are many closely related pairs: add_pin/add_pins, add_zone/add_zones, add_object/add_objects, update_object/update_objects, get_full_state/export_state, and get_garden_info/get_site_analysis. Descriptions usually clarify intended use, but the agent must frequently choose between singular/bulk variants and overlapping state/query tools.
The set overwhelmingly uses snake_case with predictable verb_noun forms such as get_*, set_*, add_*, update_*, and delete_*. A few tools deviate, including connection_status and bare save/undo/redo, but the overall convention remains readable and stable.
63 tools is excessive for an MCP surface, even for a broad garden-design editor. The count is inflated by singleton/bulk CRUD variants plus many specialized state, geospatial, catalog, view, and plant-query tools, making discovery and selection burdensome.
Coverage is strong across zones, objects, pins, garden metadata, geospatial parcel workflows, products/plants, view/layers, persistence, and undo/redo. Minor gaps exist, such as no dedicated update_pin operation, but most core workflows are supported.