Skip to main content

Idea pipeline

1718 Ideas

API/UI versioning inadequate for exportsIdea

Hi there,I’m currently working on a process to automatically export diagrams from lucid, to store the artifacts for regulatory purposes. However, I’m not able to marry the versioning observed in the UI and API.High level overview is quite straight forward:User edits a document, (multiple diagrams in different pages) User using the ui, names the version User triggers tool to export the document Tool hits /documents/{id} to obtain: Number of pages Version Tool exports each individual page using same endpoint (since only one page can be exported per API call) My plan was to be able to confirm that the version of the document I’m fetching is the intended on (i.e. the named revision).However, named versions are not shown in the API. And numeric versions are not shown in the UI This means I can’t prove that the document I’m exporting is actually the indented one - there is no way to marry them. Imagining Alice and Bob: Alice updates the diagrams and named the latest document version 1.0 (as you can do in the revision history). Bob makes an accidental change, does not name the revision.  Alice initiates export which includes Bob’s accidental change as the API only regards the latest version. Since there is no way to observe the numeric version in the UI, nor is it possible to observe the named version in the API, Alice can’t confirm the export was what she wanted.  The page export via /documents/{id} doesn’t embed any versioning in the metadata Similar issue to the above, but on a more narrow time window, from the moment one obtains the version from /document/{id} endpoint, to running all API calls to export each page, a change could be made before each API call has run. There is no way to verify this. Is there any way around this?The only way I see is the following:Expose named versions in API or provide a way to show numeric versions in the UI Export of pages with image/png or any other format, should embed versions in the produced artifact.With the current limitations, the API isn’t useful for us. Thanks

Add Update/Modify capabilities to Lucid MCP ServerIdea

I'm currently using the Lucid MCP (Model Context Protocol) server to integrate Lucidchart with AI tools and I'm finding it incredibly useful for creating diagrams programmatically.However, I've encountered a limitation that would significantly improve the workflow: the current MCP server only supports creating new documents but doesn't provide functionality to update or modify existing documents.Specific use case: I have a multi-page Lucidchart document and want to add additional pages to it programmatically through the MCP server. Currently, I have to either:Manually open the document and add pages, or Recreate the entire document from scratch with all pages includedFeature request: Could you add MCP tools that support:Adding pages to existing documents Updating/modifying existing pages Deleting pages from documents General document update capabilities (similar to how lucid_create_diagram_from_specification works, but for existing documents)This would enable true iterative diagram development through AI tools and make the MCP integration much more powerful for ongoing documentation workflows.Example tool signature:lucid_update_diagram- documentId: string (the existing document to modify)- operation: "add_page" | "update_page" | "delete_page"- pageData: standard_import_json (for the page content)Thank you for considering this enhancement. The Lucid MCP server is already a great tool, and this addition would make it even more valuable for teams using AI-assisted diagramming workflows.

Hide settings when multiple styles are selectedIdea

Lucidchart: The state indication when multiple items with different properties are selected is inaccurate/confusing and has led to many mistakes on my docs over the years. Standard UI app guidelines are that when multiple selected items have different properties – the shown definitions should blank-out, or are replaced by a horizontal line, so that you can visually tell that there are different settings applied to the multiple items. Samples:Three fonts of different sizes/colors – but the settings (if I were to follow the typical way that apps work) indicate that they are all Inter, 10pt, and black (and in fact none of these three have that setting): And then here are two selected lines – with the displayed settings indicating that they are black 6pt bent lines with a single arrow – and again, neither of these lines have that setting, let alone both:When the multiple items selected that are closer in style than my above more extreme samples – it is very confusing, because users are used to UI standards showing accurate setting information when multiple items are selected – so wrong assumptions can be made that the multiple selected items do in fact have the same settings.This is a huge problem in my opinion, and I’ve been mentioning it for years to various folks on the Lucidchart teams. Is there any chance of getting values to blank-out or have a horiz line (or even the word “mixed”) indicating differing settings, the way pretty much all other apps do? Thanks for considering!