if you are asking about VyManager and VyMCP - I don't know them; it looks only two contributors at the moment...
My proposal here is structurally very different from their MCP implementation - I am proposing to add MCP capability into core VyOS, alongside with rest and GraphQL APIs we already have. They are essentially extending VyManager, that runs in 3 containers separate from VyOS

Proposed specs for implementation attached for review and discussion.
MCP Architecture proposal:

I noticed this independent VyMCP project just dropped a few hours ago. (there is no affiliation between this feature request and their implementation)

1. Exposed MCP Resources
Resources expose read-only context to the language model via specific URIs. Instead of forcing the AI to read a massive monolithic configuration file, the system provides targeted data slices.

Required changes:

I created a PR 5114 for this - learning the ropes to contribute to VyOS.