More shapes for Lucid MCP server

Hi ​@willnourse, thanks for this idea! 

We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. 

For more information about how we manage feedback in this community, please take a look at this post:

Ideally, I’d like my prompt to be able to say something along the lines of ‘generate a diagram using the DFD shape template for the following details: <specify details>.  Use rounded rectangles for Processes, lines for connectors, shaded rectangles for External Entities’.

I saw that there is another request out there to be able to generate from a Mermaid specification - if that’s how we could specify the diagram content and then have a parameter to pass for the shape library, that would be ideal

The Ask

Extend lucid_create_diagram_from_specification to support shapes from Lucidchart's built-in libraries — starting with Azure 2024, AWS, and GCP — not just standard Lucid primitives.

The Problem

AI-generated diagrams via the MCP server render with generic shapes because the tool doesn't expose Lucidchart's native shape libraries. For cloud architecture diagrams, this makes the output unusable without significant manual rework.

Current workaround: I host a public GitHub copy of Microsoft's official Azure icon SVGs and instruct the AI to import them as external images. This is fragile — no snap-to-grid, no smart connectors, no shape data — and produces inferior results compared to what Lucidchart can do natively in the UI.

Proposed Solution

At minimum, expose three capabilities in the MCP API:

1. List available shape libraries on the account (e.g., azure-2024, aws-2024, gcp, cisco)
2. List shapes within a library so the AI agent can select by name/ID
3. Place library shapes on the canvas with native connector and layout behavior

Why It Matters

• The shapes already exist in Lucidchart — this is purely an API surface gap
• Cloud architecture diagrams are the #1 use case for enterprise teams adopting the MCP server
• A Lucid product team member confirmed this is a known limitation and that support is planned (community thread)

Environment

• MCP Client: Claude (Anthropic)
• Primary shapes needed: Azure Front Door, APIM, App Gateway, WAF, Private Endpoints, Private links, VNets, App Services, Firewalls, 

Thank you ​@brian.pieper for this detailed feedback. I certainly understand why this would be helpful, and this feedback has been shared with our product team. This thread is the best place to stay updated on this topic!