MCP (Model Context Protocol) server for Enterprise Architect has been released

[Takeshi K]

But Copilot throws an issue:
' Sorry, your request failed. Please try again.
Copilot Request id: 37d72ba4-1757-43e8-becc-6763ef90ff8d
GH Request Id: 647D:3E781C:528352:5B6037:696F8921
Reason: Request Failed: 400 {"error" : {"message": "missing required Copilot-Vision-Request header for Vision requests","code" :""}} '

This error seems that there was an error between Copilot and GitHub (GH). My add-in never returns an error or requests the Copilot-Vision-Request header. This error maybe relates to Copilot Vision feature, so I cannot help you.

[Paolo F Cantoni]

I think the term "composite diagram" is a bit unfortunate, as it has connotations that it probably shouldn't have.

When explaining the concept to EA users, I often use "linked diagram". I explain to them that this works like a hyperlink. It is the diagram that is opened when double-clicking on the element.
For me, it does not have any other meaning, and it only exists to help us humans navigate the model.

Geert

Wot 'e sed!

Paolo

[Viking]

This error seems that there was an error between Copilot and GitHub (GH). My add-in never returns an error or requests the Copilot-Vision-Request header. This error maybe relates to Copilot Vision feature, so I cannot help you.

Agreed. It seems more a problem with GitHub and the LLM. I tried several LLMs and one did not throw this exception.

[Viking]

Elements are created as intended with Stereotype. But Connectors are not. They are shown correctly, but the attribute Attribute "Stereotype" is empty. Is the issue on my side? I mentioned the profile as required and do not see a chance to do something in addition.

[Takeshi K]

Hello Viking,

I cannot reproduce the issue you mentioned on the latest build. If you use the older builds, please updaate to the latest and try again. If you can still reproduce the issue with the latest build, could you send an email to me for detail with the example mode to reproduce?

p.s.
I will reply the private email from you soon.

[Viking]

Hello Viking,
I cannot reproduce the issue you mentioned on the latest build. If you use the older builds, please updaate to the latest and try again. If you can still reproduce the issue with the latest build, could you send an email to me for detail with the example mode to reproduce?

No, the stereotypes ar not set for connectors. But the connectors are shown correctly as ArchiMate connectors. I said "add an "ArchiMate3::ArchiMate_Composition" connector between REST API and Microservice.

For elements the stereotypes have been set.

[Takeshi K]

Hi Viking,

I am afraid I still do not quite understand the issue; however, this forum is not the appropriate place to solve individual problems related to a specific add-in. Could you please email me the details, along with an example project or the steps to reproduce the error?

[Viking]

Hi Viking,

I am afraid I still do not quite understand the issue; however, this forum is not the appropriate place to solve individual problems related to a specific add-in. Could you please email me the details, along with an example project or the steps to reproduce the error?

As far as I know I cannot insert an image.

I created a ArchiMate3::ArchiMate_Serving realtionship. The mcp server created an association with profile "ArchiMate3". But the checkbox for the stereotype "ArchiMate_Serving" has not been set.

[Viking]

As far as I know I cannot insert an image.
I created a ArchiMate3::ArchiMate_Serving realtionship. The mcp server created an association with profile "ArchiMate3". But the checkbox for the stereotype "ArchiMate_Serving" has not been set.

I tested this behavor now for qeax and MariaDB. Stereotype (checkbox) has been set for Elements, but not for connectors.