11
« on: November 04, 2025, 12:13:30 pm »
Hello Viking,
Thank you for your feedback about the MCP add-in.
First, I would like to tell that the issue which BPMN events cannot be created is NOT a bug of my add-in nor an issue of my add-in. This is originally EA's Automation Interface problem.
About the BPMN events, there are two forms. One is the normal (isolated) event, and another is the edge-mounted event. Both has the same BPMN 2.0::StartEvent stereotype.
When we create the BPMN 2.0::StartEvent with Collection.AddNew(name, "BPMN 2.0::StartEvent"), EA always creates the edge-mounted form. But the edge-mounted objects require its parent, so the MCP command always fails. There is no way to specify which form we create for the AddNew method when a stereotype has two or more forms.
Anyway, I have added a workaround for the BPMN events. Please call the tool (MCP method) with BPMN2.0::StartEvent, BPMN2.0::IntermediateEvent and BPMN2.0::EndEvent on the latest MCP server version 2.0.3. You can now create these events.
And during the test of this workaround, I found another issue which we cannot change the type of event (Timer, Message, etc.). This is also an issue of the Automation Interface, so I also added another workaround to update the BPMN properties (tagged values) correctly.
Could you try again with the latest installer?
About your second post, maybe your MCP client sends the string 'CRM' for the type of a new element. In Enterprise Architect, there is no element type 'MCP' so the 'invalid type' is reasonable. About a prompt, the prompts which are offered my MCP add-in are useful to start. In some MCP client such as the Claude for Desktop, we can specify and see the prompts.