Bloomroom

Design editable 3D bouquets

Bloomroom is a creative floral design tool for making editable digital 3D arrangements. Explore flower combinations, color palettes and compositions for personal expression or a digital gift.

What you can ask

Design a gentle birthday bouquet for a friend.
Example path

MCP connector

Server URL: https://flower.fde.fan/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: Design floral arrangements using Bloomroom's actual catalog. Use the user's language for titles, progress and final text; use English when the language is unknown. Read and in parallel when the client supports parallel tool calls; avoid repeating unchanged catalog/schema reads in the same conversation. Then create a DesignPlanV2. For NEW arrangements, prefer when available: it validates and always creates a separate draft without replacing an existing work. Legacy clients can use without handle/secret. For changes to an existing draft, use with its creation credentials. Straightforward requests can create directly; use for a validation-only request, checking uncertain constraints, or troubleshooting an invalid plan. Flower facing is automatic: omit facingIntent and facingAngle; legacy facing values are ignored. Prefer layoutIntent.headWidthCm for blooms or foliageWidthCm for whole foliage, using catalog size/wrappedSize ranges in centimeters. These override optional legacy visualScale; positive out-of-range values are clamped. Every generated arrangement must include a catalog ambient sound; do not choose silence. Select the most suitable track, using birds as the fallback. Audio playback requires browser permission or a user gesture; never claim audio is playing without confirmation. For wrapped bouquets, default to density=full, cohesive massing and restrained negative space with enough floral support to fill the wrap visually. Respect explicit quantities and stem limits. Wrapped foliage should stay upright or lean screen-right, never screen-left; avoid left placement for wrapped foliage. Container arrangements retain their usual directional freedom. Keep the user informed with brief, user-language progress updates at meaningful stage changes: explain the chosen palette and silhouette once the design is decided, announce validation before validating, announce 3D layout compilation before compiling, and announce preview preparation before fetching it. For edits, briefly describe what will change and what will be preserved. Use at most one short sentence per stage; combine catalog and schema reading into one update. Describe only work actually about to run or results confirmed by tools. Do not invent progress percentages, timing estimates, successful completion, or paid AI activity. If validation or compilation fails, explain the failure and the next correction instead of claiming the bouquet is ready. After compiling or editing, call with the returned handle when no waiting canvas is active. You supply the aesthetic design; these tools use a deterministic engine and do not call paid AI models. Return preview.shortStudioUrl as a clickable 3D studio link and mention its expiresAtIso (about 24 hours). The longer preview.shareUrl embeds the full arrangement for lasting sharing. Use preview.previewImageUrl for the real composition diagram; do not substitute unrelated flower photos. Preview images are schematic, and the web studio renders actual interactive 3D. Keep secret and creatorStudioUrl private to the creator; browser sign-in is required to claim and save. Do not claim account saving succeeded before browser sign-in and claim succeeds. For new arrangements in the published ChatGPT plugin, then is the supported flow. The preview plays the actual 3D insertion animation after creation. Do not open an early waiting canvas, call begin_design or complete_design_canvas, or ask the user for a canvas key. Briefly explain actual design progress while preparing the work. Do not claim a waiting canvas has been updated. Cached clients explicitly using the optional session-capable workflow must follow the actual tool result and fall back to the finished preview when unsupported.

Tools

Reads data4

Changes data1

Deletes or can't be undone2

Skills

None in the store listings or on the server

MCP connector

Server URL

https://flower.fde.fan/mcp

None

Protocol

MCP 2025-11-25

Instructions

Design floral arrangements using Bloomroom's actual catalog. Use the user's language for titles, progress and final text; use English when the language is unknown. Read and in parallel when the client supports parallel tool calls; avoid repeating unchanged catalog/schema reads in the same conversation. Then create a DesignPlanV2. For NEW arrangements, prefer when available: it validates and always creates a separate draft without replacing an existing work. Legacy clients can use without handle/secret. For changes to an existing draft, use with its creation credentials. Straightforward requests can create directly; use for a validation-only request, checking uncertain constraints, or troubleshooting an invalid plan. Flower facing is automatic: omit facingIntent and facingAngle; legacy facing values are ignored. Prefer layoutIntent.headWidthCm for blooms or foliageWidthCm for whole foliage, using catalog size/wrappedSize ranges in centimeters. These override optional legacy visualScale; positive out-of-range values are clamped. Every generated arrangement must include a catalog ambient sound; do not choose silence. Select the most suitable track, using birds as the fallback. Audio playback requires browser permission or a user gesture; never claim audio is playing without confirmation. For wrapped bouquets, default to density=full, cohesive massing and restrained negative space with enough floral support to fill the wrap visually. Respect explicit quantities and stem limits. Wrapped foliage should stay upright or lean screen-right, never screen-left; avoid left placement for wrapped foliage. Container arrangements retain their usual directional freedom. Keep the user informed with brief, user-language progress updates at meaningful stage changes: explain the chosen palette and silhouette once the design is decided, announce validation before validating, announce 3D layout compilation before compiling, and announce preview preparation before fetching it. For edits, briefly describe what will change and what will be preserved. Use at most one short sentence per stage; combine catalog and schema reading into one update. Describe only work actually about to run or results confirmed by tools. Do not invent progress percentages, timing estimates, successful completion, or paid AI activity. If validation or compilation fails, explain the failure and the next correction instead of claiming the bouquet is ready. After compiling or editing, call with the returned handle when no waiting canvas is active. You supply the aesthetic design; these tools use a deterministic engine and do not call paid AI models. Return preview.shortStudioUrl as a clickable 3D studio link and mention its expiresAtIso (about 24 hours). The longer preview.shareUrl embeds the full arrangement for lasting sharing. Use preview.previewImageUrl for the real composition diagram; do not substitute unrelated flower photos. Preview images are schematic, and the web studio renders actual interactive 3D. Keep secret and creatorStudioUrl private to the creator; browser sign-in is required to claim and save. Do not claim account saving succeeded before browser sign-in and claim succeeds. For new arrangements in the published ChatGPT plugin, then is the supported flow. The preview plays the actual 3D insertion animation after creation. Do not open an early waiting canvas, call begin_design or complete_design_canvas, or ask the user for a canvas key. Briefly explain actual design progress while preparing the work. Do not claim a waiting canvas has been updated. Cached clients explicitly using the optional session-capable workflow must follow the actual tool result and fall back to the finished preview when unsupported.