Typical use cases of MCP Server for Enterprise Architect

The following are typical use cases of MCP Server for Enterprise Architect.

Use Case 1: Automated Summarization

Generate "Summary Views" from massive, complex diagrams, focusing only on specific concerns like security, data flow, or hardware interfaces. This helps stakeholders quickly grasp the essential aspects of the model without being overwhelmed by details.

Example prompt to ask AI:

"Analyze the current diagram and generate a summary focused exclusively on Security.

Use Case 2: Natural Language Querying of Models

Allow users to ask questions about the model in natural language, such as "What are the main components involved in user authentication?" or "Show me the data flow between the Order and Payment systems." The MCP Server interprets these queries and retrieves relevant model elements and diagrams.

Example prompt to ask AI:

"Based on the entire project model, identify all classes and interfaces involved in the 'User Authentication' flow. List their dependencies and show which specific component is responsible for hashing passwords."

Use Case 3: Collaborative Model Review & Feedback

Enable stakeholders to review models collaboratively by providing automated annotations, comments, and suggestions based on best practices or organizational standards. The MCP Server can highlight potential issues or improvements directly within the diagrams.

Example prompt to ask AI:

"Review the opened diagram for any potential bottlenecks or violations of our internal communication standards. Find any lifelines that have more than five synchronous calls and suggest where we might use asynchronous messaging instead."

Use Case 4: Legacy Model Analysis & Refactoring

Scan large-scale models that have become cluttered over years of maintenance to identify duplicate definitions or "dead elements" that are no longer referenced. Provide automated refactoring suggestions to streamline the model structure, improve clarity, and enhance maintainability.

Example prompt to ask AI:

"Scan the 'Legacy_v2' package for 'dead elements'. Identify any Classes or Blocks that have no incoming or outgoing relationships and have not been updated in the last 12 months. Propose a plan to consolidate duplicate 'DataEntity' blocks found across different sub-packages."

Use Case 5: Design Consistency & Rule Checking

Monitor diagrams as they are being built to ensure they follow project-specific rules, UML/SysML standards, or design principles like "SOLID." Alert modelers about any violations and suggest corrective actions to maintain design integrity.

Example prompt to ask AI:

"Check the current Class Diagram against SOLID principles. Specifically, look for violations of the Single Responsibility Principle (SRP) where a class has more than 15 methods, and suggest how to split these classes into smaller, more focused entities."

Use Case 6: Design Pattern Recommendations

Analyze the current design context to suggest the application of GoF design patterns or microservice patterns and automatically restructure the diagram. This ensures adherence to best practices and improves the overall architecture quality.

Example prompt to ask AI:

"Look at the current structure of the 'NotificationModule' package. Given that we need to support multiple output types like SMS, Email, and Push, would the Strategy or Observer pattern be more appropriate here? Please tell me how the diagram would look if we implemented the Strategy pattern."

Use Case 7: Automated Test Case Generation

Calculate comprehensive test paths from State Machine or Activity diagrams and automatically output test cases or execution scripts. This accelerates the testing process and ensures thorough coverage of design scenarios.

Example prompt to ask AI:

"Analyze the current State Machine diagram. Generate a set of test scenarios that cover 100% of the transitions, including 'Happy Path' and 'Error' states like 'Payment Timeout' or 'Inventory Unavailable'. Output the steps in a Gherkin (Given/When/Then) format."

Use Case 8: Stub & Mock Generation via Interface Definition

Generate mock programs or API stubs for external systems based on the interface information defined in Component or Class diagrams. This accelerates integration testing and development by providing ready-to-use stubs that simulate the behavior of external dependencies.

Example prompt to ask AI:

"Based on the 'PaymentGateway' Interface in this diagram, generate a C# mock implementation using Moq. Ensure the mock returns a 'Success' status for transaction IDs starting with 'TXN_' and a 'Declined' status for all others."

Use Case 9: Automated Model Generation from Natural Language

Generate initial drafts of Class or Sequence diagrams directly from requirement documents, whiteboard notes, or verbal descriptions. This speeds up the modeling process and provides a foundation for further refinement by modelers.

Example prompt to ask AI:

"Read the attached 'Billing_Requirement.docx' and create a draft Class Diagram in the current package. Include entities for 'Invoice', 'LineItem', and 'TaxCalculator', with appropriate associations and multiplicity based on the document text."

Use Case 10: Automated Traceability Management

Automatically link Requirements (Requirement Diagrams) to the design elements that realize them (Block Definition Diagrams) and the cases that verify them. This ensures that all requirements are properly addressed in the design and verified through testing, enhancing model integrity and compliance.

Example prompt to ask AI:

"Analyze the 'Functional Requirements' package and the 'System Design' package. Automatically create 'Satisfy' relationships between requirements and the Blocks that share similar names or descriptions. Present a list of any requirements that currently have no design elements linked to them."