Skip to main content

Idea pipeline

Filter by idea status

Filter by product

1796 Ideas

Lucid MCP fully customizable: tool reference, roadmap, bulk ops, shape library accessIdea

What I want, simply: describe a diagram to my AI agent, give feedback on it, then easily iterate either in the Lucid UI or back through the MCP, while using the proper native AWS resources throughout.The biggest ask: a fully transparent MCP. I want a published tool-by-tool reference + parameters + a roadmap so users know what's available, what's coming, and what's not planned. Today everything is discovered through runtime trial-and-error. Here are my problems and proposed solutions / requests:Problem: No public tool / parameter docs or roadmap. Agents discover capabilities by trial-and-error. Users can't tell what's planned vs deprioritized. Publish a tool-by-tool reference (each name + purpose + parameter signature) plus a quarterly status board (planned / in progress / shipped / not planned). Problem: No bulk update / move. Every position change, resize, or text edit is a separate `lucid_edit_item` call. Updating 20 icons = 20 round-trips. "Shift these 8 boxes down 50px" = 8 round-trips today. Solution: Add a bulk-edit and bulk-delete primitive that accepts an array of item ops (id + position / size / text) in one call. Problem: `lucid_add_block` rejects AWS / Azure / GCP shape libraries. Only Standard Library block types (RectangleBlock, TextBlock, etc.) are accepted. AWS 2024 / Azure 2024 / GCP 2021 shapes are reachable ONLY via `lucid_create_diagram_from_specification` (`namedShape` + `className`). Passing `ResAmazonVPCEndpointsAWS2024` to `lucid_add_block` returns HTTP 500 "An unknown error occurred". Mid-iteration additions force either full doc recreation (loses the reviewer's stickies and repositioning) or fallback to plain rectangles (loses the AWS visual). Solution: Extend `lucid_add_block` to accept the classNames listed in `lucid://shape-libraries/aws-2024/*`, `lucid://shape-libraries/azure-2024/*`, `lucid://shape-libraries/gcp-2021/*`, including containers (VPC, AWS Cloud, Region, Subnet)., etc.. Problem: no delete. I would love to be able to have access to delete lucid charts that I own. Because of restrictions on lucid edit block actions, I have had to use create new from spec and iterate, so now I have a lot of diagrams that I would like to delete haha.  This is mostly a side effect of the mcp function limitations Solution: add bulk / expand update capabilities or allow for delete of document to enable iteration  If I'm missing something / if any of this is already doable via a path I haven't found, please point me at it! Thanks!

plaird
Lucid Legend Level 1
plairdLucid Legend Level 1

Lucid AI changing advanced properties on SFACardsIdea

First time bug reporter. I think I am following the correct process as described in the community bug report explainer apologies if not! I asked Lucid AI to write up its own bug report on the issue it faced. Problem: Lucidchart AI Cannot Change Advanced Properties on SFACards Use CaseSetupCreate a new Lucidchart diagram In the Shape Gallery, select all 4 Salesforce architectural libraries (header, card, icons) Drag a Collapsed Card shape onto the canvas Give the card name in the text headerActionAsk Lucid AI to enable the Header icon advanced property for the card. “for the salesforce card shape, set the ‘Header icon’ property to true” It will fail. “I can’t directly toggle the ‘Header icon’ property on the Salesforce card shape via automation. You can do it manually using Shape Options” We are hoping to generate diagrams using Lucid AI. But for complex diagrams with many shapes, there will be a lot of manual fixups (header icons, footer icons, etc) which makes Lucid AI difficult to use. Lucid AI’s Self DiagnosisI asked Lucid AI why it couldn’t complete the task. After some back and forth diagnosis chatting, this is what Lucid AI reports about its failure to toggle the Header Icon toggle: Subject: SFACard advanced toggles (Header icon / Footer icons) not settable via EditBlockAdvancedProperty Summary: When working with Salesforce Architecture “SFACard” shapes, several Advanced Options toggles (notably “Header icon” and related icon/footer toggles) appear to be stored as block properties (e.g., ShowEntityIcon), but they cannot be programmatically set via the EditBlockAdvancedProperty automation API. This prevents automation from enabling header/footer icons on SFACards even though the UI supports it. EnvironmentShape: SFACard from Salesforce Architecture Diagrams library (salesforcearchitecture.js)Automation tools used: EditBlockAdvancedProperty, CanvasQuery, ShapeDetails, DocumentHistory Repro stepsCreate an SFACard and confirm Advanced Options toggles exist in UI: Advanced options: Allow nesting, Header icon, Header line, Condensed, Footer, Footer icons, etc. In the Lucid UI, toggle “Header icon” ON for a card. Observe the underlying property change captured in document history: SetProperty on the card: Property = ShowEntityIcon, Value = true (OldValue = false) Attempt to set the same property on another SFACard via automation: Call: EditBlockAdvancedProperty(ItemId=, PropertyName="ShowEntityIcon", Value="true", ValueType="boolean") Observed behaviorThe automation call fails with:“Advanced property 'ShowEntityIcon' is not registered for SFACard.” CanvasQuery (IncludeAllProperties=true) does not reliably surface these advanced-toggle properties for the SFACard instance, even after toggling them in the UI. ShapeDetails does not expose a usable, instance-specific list of registered advanced properties for SFACard (i.e., we can’t discover the correct property key(s) that are accepted by EditBlockAdvancedProperty).Expected behaviorAdvanced options toggles that are user-editable in the UI (e.g., “Header icon”, “Footer icons”) should be settable via EditBlockAdvancedProperty.At minimum, the property keys that correspond to those toggles (e.g., ShowEntityIcon) should be registered/whitelisted as advanced properties for SFACard so automation can set them. ImpactPrevents programmatic configuration of SFACard features that are important for standardized architecture-diagram generation (header icons, footer icons, potentially header line / condensed / footer toggles).Forces manual per-card UI changes, which defeats automation workflows.Evidence / notes Document history shows SFACard instances created with (non-exhaustive) SFACard-specific fields such as:ShowEntityIcon, IncludeHeaderLine, CondensedPadding, CondensedPaddingAmount, ShowFooter, FooterIconIds, SecondaryColor, AttrColumnsCount, etc.Of these, at least ShowEntityIcon clearly maps to the UI “Header icon” toggle, but it is rejected by EditBlockAdvancedProperty as “not registered.” RequestPlease confirm intended API support for SFACard advanced toggles.If supported, register/enable the relevant properties (e.g., ShowEntityIcon, FooterIconIds / Footer icons toggle, ShowFooter, IncludeHeaderLine, CondensedPadding, etc.) so they can be updated through EditBlockAdvancedProperty, and/or expose them through ShapeDetails (BlockId mode) so automation can discover valid PropertyName values.