Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

Related Servers

Alternatives to Garden Design MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Autodesk Civil 3D through natural language, supporting tools for surfaces, alignments, profiles, corridors, pipe networks, COGO points, and AutoCAD geometry.
      9
      4
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to assess any parcel for micro-farm viability (climate, water, farmland context, access, flood risk) and dwelling feasibility, and to find real land for sale from free, keyless public data sources.
      5
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to design 3D-printable, multi-colour OpenStreetMap models in chat by finding places, creating and editing designs, rendering images or rotatable 3D views, and sharing links that open the design in a configurator.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to control supported CAD applications through natural-language or direct tool calls for drawing, layer, block, entity, file, and data-export operations.
      -

    TDQS

    B3.3/5.0

    Scored across 63 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.