StarUML MCP Server Does Not Support Custom Diagram Names

[sjswerdloff]

Problem Description
The StarUML MCP server does not parse or respect custom diagram names from Mermaid code, resulting in all generated diagrams having generic default names.
Expected Behavior

Diagrams should be created with meaningful names based on Mermaid title directive or similar naming mechanism
Diagram names should appear in StarUML's diagram list for easy identification and organization

Actual Behavior

All class diagrams appear as "Class Diagram by Mermaid"
All sequence diagrams appear as "Sequence Diagram by Mermaid"
No way to distinguish between different diagrams in the StarUML interface

Reproduction Steps

Generate a diagram with title directive:
mermaidclassDiagram
title "My Custom Diagram Name"
class TestClass {
+method1()
}

Check diagram name in StarUML diagram list
Observe generic "Class Diagram by Mermaid" name instead of intended title

Impact

Poor user experience when working with multiple diagrams
Difficult to organize and reference specific architectural diagrams
Reduces documentation value of generated diagrams

Suggested Solutions

Parse Mermaid title directive and use as StarUML diagram name
Add optional name parameter to MCP server function calls
Allow post-creation diagram renaming through MCP interface

Workaround
Currently using note annotations within diagrams to display intended titles, but this doesn't solve the organization problem in StarUML's diagram list.
Environment
OS: MacOS Sequoia 15.5
StarUML: 7.0.0 [Latest version as of July 2025]
StarUML MCP Server: 0.1.0 [Latest version]
Mermaid diagram types tested: classDiagram, sequenceDiagram