All servers / Design / Garden Editor MCP server
Garden Editor MCP server
MCP server for Garden Editor — AI-assisted garden design via Claude, Cursor, or any MCP client
Tested by ConnectATDScore 88 out of 100. Tested 2026-11-18 on package version 2.16.2. Package: @zaprojektujogrod/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.9 seconds including download)
- Tools offered: 59
- Last published: 2026-11-18
- Weekly downloads (npm): 1,550
- License: MIT · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
geocode_address1 of 1 parameter describedFind 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. The match is fuzzy: when the result carries `approximate: true` (another place, or the house number not found) it is NOT the address asked for: do not take it for the plot.
get_parcel_by_coordinates2 of 2 parameters describedGet parcel information by WGS84 coordinates (lat/lon). Poland only: refused for a garden placed outside Poland.
get_parcel_by_id1 of 1 parameter describedGet parcel information by parcel ID. Poland only: refused for a garden placed outside Poland.
get_parcel_by_address4 of 4 parameters describedGet parcel information by address (geocodes then looks up parcel). Poland only: refused for a garden placed outside Poland. Give the address as `town`, `street` and `number` (street empty in a village) or as one `address` text; the editor tries the spellings the register understands (ul./ulica, '4 B' = '4B', either order). If the register does not know the address it falls back to the map finder and returns the parcel there with `approximate: true`: then confirm with the owner that it is the plot. A failure says how far it got (town, street or house number); then use get_parcel_by_id with the number from the geoportal, or get_parcel_by_coordinates.
import_parcel3 of 3 parameters describedImport 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 `capture_preview` shows real site context (neighbors, road, vegetation) under the boundary. Default alignment is `north_up` so cardinal reasoning ("south wall", "west fence") works naturally; pass `side_aligned` if you'd rather draw on an axis-aligned canvas. WMS failure is non-fatal — boundary + geo-anchor still land and the response carries `mapBackground: { loaded: false, reason }` so you can decide whether to retry or continue without the background. Pass `loadMapBackground: false` to skip the WMS fetch entirely (faster; useful for headless evals). Poland only: refused for a garden placed outside Poland — draw the boundary with set_boundary instead.
import_buildingsno parametersScan the imported parcel + 10 m margin via ULDK and add discovered building footprints as `building` zones. Requires `import_parcel` first — uses the current parcel and geo-anchor. Blocks until the scan completes; **typically 1–2 minutes for a residential parcel** because ULDK is slow, so do not retry on perceived stalls. Re-runs are safe: buildings already imported are deduped by `parcelBuildingId` and reported under `skipped`. Returns `{ success, count, added, skipped, buildings: [{ zoneId, parcelBuildingId, functionLabel, centerX, centerY, width, height }] }` (meters). The largest building whose center sits inside the parcel is usually the user's house; the rest are neighbors. Poland only: refused for a garden placed outside Poland.
get_site_analysis1 of 1 parameter describedMeasured 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 `gardenDepth` — the free distance from the facade straight out to the boundary; neighbouring buildings with direction and whether attached; total garden area and whether it is a large garden (`largeGarden`, 400 m² or more: zoned in steps); the site's main directions (`axes`, degrees from east: the house walls and the boundary), which zone edges follow. Use it to put door pins ON the right facade and to check whether a terrace or bed fits on a side before drawing zones.
set_geo_anchor5 of 5 parameters describedSet 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_boundary1 of 1 parameter describedSet 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_background2 of 2 parameters describedSwitch 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_image4 of 4 parameters describedLook 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_map2 of 2 parameters describedLay 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 `matches`: two or more points on the map matched to the same points in the garden (garden metres, e.g. boundary corners from get_garden_info) — scale, turn and position are fitted; from three matches you get how far each lands from its garden point. Or `measure` (a plot with no place or boundary): two points on the map and the real distance between them — the map lies to scale, as drawn, `from` at `at`. Pick points far apart, zoom_image to place them exactly, then check with capture_preview. Laying again replaces the map. The next save keeps it with the garden, in the place of a kept cadastral map (which can still be downloaded and shown).
map_to_garden0 of 1 parameter describedWhere 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_anchorno parametersGet the current geo-anchor (if set)
upload_reference_photo2 of 2 parameters describedUpload a reference photo (house exterior, current garden). Stored in-session. The AI agent can analyze photos via its own vision capabilities.
get_reference_photosno parametersGet all uploaded reference photos for this session
add_pins1 of 1 parameter describedAdd context pins (one or more) in one call. Returns `ids` in input order (null where one failed), `issues` for failures and warnings, and `checks`. 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_pin1 of 1 parameter describedDelete a pin by ID
get_pinsno parametersGet all pins in the garden
get_garden_infono parametersGet garden metadata: ID, name, description, rotation, boundary, object counts
set_garden_rotation1 of 1 parameter describedSet the garden's north orientation in degrees
get_journalno parametersRead your design journal: your working memory of this garden across sessions (site, baseline, pins, brief, the decisions of each pass, open questions, status), in Markdown sections. For you only — the owner never sees it. Read it at the start of a session. Answers {text, updatedAt}; empty text while nothing has been written.
write_journal2 of 2 parameters describedWrite your design journal (kept with the garden, for you only). Write the whole journal once; after that update only the section that changed by naming it in `section` — never resend the rest. Answers the journal's length, not its text.
set_garden_description1 of 1 parameter describedWrite the garden's description. It is the owner's: write it only when they ask for it or agree to your offer (offer at most once, when the design is finished). The design as it stands now, in a few lines of Markdown in the owner's language — what the garden has and why. The owner reads it, and it is shown with the garden on the website. Never a log of the work, never ids or pass numbers — those go in the journal.
capture_preview2 of 2 parameters describedCapture 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_zones1 of 1 parameter describedAdd zones (one or more) in one call. Returns `ids` in input order (null where one failed), `issues` for failures and warnings, and `checks` for each zone. 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_zone14 of 14 parameters describedUpdate an existing zone. Reshape it with `polygon` or `path` (absolute, metres) or with x/y/width/height/points; lock or unlock it with `locked`. Returns checks for the updated zone (area, narrowest width, overlaps, parcel overflow).
delete_zone1 of 1 parameter describedDelete a zone by ID
get_zonesno parametersGet all zones in the garden (editor geometry: centre + relative points; `locked` marks zones the design must not change). For absolute polygons and areas use get_site_analysis.
get_objects_in_zone1 of 1 parameter describedReturns 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_analysis1 of 1 parameter describedAnalyzes a zone's contents: object count, planting cover counted once where plants and shapes overlap (`coveragePercent`), the cover of each height layer (`coverByLayer`: ground under 0.5 m, shrub under 3 m, tree), the footprints added up (`footprintSumPercent`), a density rating (dense = one layer crowding itself), and boundary violation warnings.
search_products5 of 5 parameters describedSearch the product catalog. Filter by layer (ground/architecture/plants), text query, or category.
get_categories1 of 1 parameter describedGet 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 top-level groups (Drzewa, Krzewy, Pnącza, Byliny, Trawy Ozdobne); to filter search_products by plant category you must follow up with get_subcategories(<top-level id>) and pass a leaf id.
get_subcategories1 of 1 parameter describedGet 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_details1 of 1 parameter describedGet full details for a specific product by ID
get_plant_info2 of 2 parameters describedA plant's catalog footprint and botanical facts: characteristics (height, spread, form, foliage, flowers), requirements (soil, sunlight, hardiness), maintenance level and spacing. Check finalists only — search_plants already gives every match's mature height and spread.
get_plant_attributesno parametersReturns 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_plants16 of 16 parameters describedFilter the plant catalog by botanical attributes. Returns lean records ({productId, botanicalName, commonName, height, spread, kind} — mature height and spread in metres, the top of each range). Filter by `kind` (grass, perennial, shrub…) instead of guessing names: the catalog is small, and a name you know may not be in it. 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 only to check a finalist's requirements. 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_objects2 of 2 parameters describedGet 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_objects1 of 1 parameter describedAdd garden objects (one or more) in one call. Type determines rendering: 'plant' for plants, 'building' for architecture, 'rectangle'/'ellipse'/'polygon'/'path' for ground shapes, 'shape' for a generic plant shape; a path takes pathWaypoints (centreline) and pathWidth. Each object takes productId OR productQuery (a name search resolved server-side) — a shape takes `shape` instead, sized by width (spread or length), height (depth across) and `tall`; a hedge shape can take `line`. Width/height are optional (catalog defaults; a shape's middle size). Returns `ids` in input order (null where one failed) and `issues` for failures and warnings. Generic plant shapes stand for no species, only a form (SC-191): trees tree_round/oval/conical/columnar/weeping/spreading (2–25 m tall); shrubs shrub_round/conical/columnar/upright/spreading (0.2–6 m); clump = a drift of perennials or grasses (0.15–2.5 m tall, width = the drift's diameter); groundcover = a low mat (≤ 0.5 m, width = its diameter: 1, 2 or 4 m); hedge = a line (0.3–4 m tall, 0.3–2 m thick); climber = a panel on a wall or fence. Sizes are mature, in metres; a size outside the form's range is set to its edge and the reply says so; with no size, the form's middle size.
plant_zones0 of 1 parameter describedPlant zones with the plants you chose — species (productId) or generic plant shapes (shape + size) — the editor places them: in beds, groups of 3–7 of a kind with canopies touching; in hedge and screen zones, one closed row; a hedge shape becomes one line along the zone, as wide as the zone. Species take their catalog size, shapes the size you give. They line up with the zone's longest edge and stay clear of paths, terraces, buildings, entries, parking, lawn and the plants already there of their own height layer — ground cover goes under shrubs and trees. Use it for all planting (trees and specimen shrubs too, with `count`) instead of placing plants with add_objects — and plant every zone of a pass in one call. Replies per zone: how many of each it planted, the `cover` counted once (aim 0.85–1.0) and `coverByLayer` (ground < 0.5 m, shrub < 3 m, tree).
update_objects1 of 1 parameter describedUpdate garden objects (one or more) in one call: position, size, rotation, label, or swap the product with productId or productQuery (plants and buildings adopt the new catalog size; ground shapes keep their shape and swap texture only). A generic plant shape resizes (width, height, tall) within its form's range and keeps its form; it becomes a species with swap_shapes. Returns `ids` and `issues`.
delete_objects1 of 1 parameter describedDelete multiple garden objects by ID in a single call. Returns array of results.
suggest_species5 of 5 parameters describedFor generic plant shapes, the species that fit them — after the designer has signed off the shape layout, instead of searching the catalog shape by shape. Same habit as the shape, mature size within a tolerance of the shape's, suited to the place's light, soil and hardiness; species the shape's label or notes name come first (named). Like shapes (same form, label without its number, size) share one entry with their ids; each candidate is one line. Shapes no species fits come under `noFit`: tell the designer before the swap.
swap_shapes0 of 1 parameter describedSwap generic plant shapes for species once the designer has signed off the layout: each species stands in its shapes' place at its own catalog size — one plant for a tree, shrub or clump; a row half its spread apart along a hedge; plants at their density over a ground-cover mat (which can also take a `mix` of species, neighbours differing) or a drift. The whole call is one undo step. `differs` says where a species' size is outside its shape's. Show the design before and after and ask the designer to approve; if they don't, `undo` brings the shapes back.
set_view_mode1 of 1 parameter describedSwitch between 2D (top-down) and 3D (perspective) view
set_layer_visible2 of 2 parameters describedShow or hide a rendering layer
focus_on4 of 4 parameters describedFocus the camera on a specific area in the garden
saveno parametersSave all changes to the server
get_full_state1 of 1 parameter describedGet 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).
house_build5 of 6 parameters describedBuild the 3D model of a house on its building outline (from import_buildings), at true size and in its place: the main block — walls up to the eaves and a plain gable roof, default colours. Then shape it step by step: house_set_roof, house_set_walls, house_set_openings, and house_set_block for further blocks (a wing, a garage, a porch) assembled from the same simple boxes-with-roofs. A porch, carport or pergola is posts plus an open block: posts are thin blocks (about 0.15 × 0.15 m, no roof), the roof an open block (open: true) at the eave height. Tell it which compass side the front (entrance) facade faces — read it from the photos and get_site_analysis. Calling it again starts that house over. Look at the result after each step with house_preview and compare it with the photos. House frame: stand in front of the house facing its front facade; x runs to your right, z towards you, metres from the main block's centre. Facades: front, back, left, right as seen from the front. An opening's offset is measured on its own facade standing outside facing it: from that facade's LEFT end to the opening's centre.
house_set_block8 of 10 parameters describedAdd, change or remove a block of the house — a box with its own walls, roof and openings: a wing (L or T shape), a garage, a porch, a bay. A new block needs center, width, depth and wallHeight; it takes the main block's walls and roof material, with a gable roof you can change with house_set_roof {block}. Open roofs on posts — a porch on posts, a carport, a pergola: add the posts as thin blocks (width and depth 0.4 m or less: they get no roof and no plinth; give them a wood, render or concrete finish with house_set_walls), then the roof as a block with open: true (no walls; its roof hangs at its wallHeight, a gable's ends stay clad; a plinthHeight gives it a deck underneath) and set its roof (gable, shed or flat — a flat one is a thin sheet). Blocks may overlap the main block (a wing joined to it). The main block's size and place come from the outline: change only its wallHeight here. House frame: stand in front of the house facing its front facade; x runs to your right, z towards you, metres from the main block's centre. Facades: front, back, left, right as seen from the front. An opening's offset is measured on its own facade standing outside facing it: from that facade's LEFT end to the opening's centre.
house_set_roof12 of 13 parameters describedSet a block's roof: gable (two slopes, triangular gable walls), hip (slopes on all four sides), shed (one slope falling towards lowSide), flat. ridge 'parallel' runs the ridge along the front facade (gables on left and right); 'perpendicular' puts a gable on the front. Also the chimneys (whole house) and solar panels (this block's slopes). House frame: stand in front of the house facing its front facade; x runs to your right, z towards you, metres from the main block's centre. Facades: front, back, left, right as seen from the front. An opening's offset is measured on its own facade standing outside facing it: from that facade's LEFT end to the opening's centre.
house_set_walls6 of 7 parameters describedSet the walls' finish and colour: render, brick, cladding-vertical, cladding-horizontal, stone, concrete, glass. lowerBand gives a different finish from the ground up to its height (e.g. grey render on the ground floor, white above; null removes it). block 'all' sets every block.
house_set_openings2 of 4 parameters describedSet the windows, doors and facade panels of ONE facade of a block (replaces that facade's list; [] clears it). Kinds: window, door, patio-door (glazed door), garage-door, panel (a flat panel of another finish, e.g. wooden cladding between windows — give material and color). Measure from the photos in proportion to known sizes (a door is about 2.05 × 0.95 m). Windows in a gable above the eaves go on that gable's facade. House frame: stand in front of the house facing its front facade; x runs to your right, z towards you, metres from the main block's centre. Facades: front, back, left, right as seen from the front. An opening's offset is measured on its own facade standing outside facing it: from that facade's LEFT end to the opening's centre.
house_preview2 of 3 parameters describedPictures of the house as built so far, on its own (no garden around it), from the sides you ask: front-left, front-right, back-left, back-right, front, back, left, right, top. Use it after each step to compare with the photos, and fix what differs. Default: front-left and back-right.
house_get1 of 1 parameter describedThe house as built so far: its position (for focus_on), which compass side each facade faces, every block with its roof, walls and openings, chimneys, solar panels.
get_design_guide1 of 1 parameter describedThe 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 and verification. Call once at the start of a session. Detailing — Step 3: surfaces, objects, the planting as shapes, the species — comes apart: call with `part: "detailing"` before you detail.
attach_image2 of 2 parameters describedHand the editor a picture from a file on the designer's computer — a survey map, a site plan, a dimensioned drawing. Pictures the designer pastes into this chat never reach the editor, so the map tools can't use them: ask where the file is and attach it by its full path. The editor keeps it at full size as the next attached image; the reply shows its copy (view "N"): point at that copy's pixels with zoom_image (a close-up) and set_survey_map (lay it under the garden by matched points). PNG, JPEG or WebP, up to 20 MB; a PDF: a page exported as an image first.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.