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
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 1 2026
PR for adding the missing documentation: https://github.com/vyos/vyos-documentation/pull/2124
Hi @mihakralj
Is it worth working on this given the community driven projects you mentioned?
I am learning MCP and deployment framework for them, and I am happy to help - as my learning effort
New repository with PRs is here https://github.com/vyos/rest.vyos
s/set container \$container/set container name \$container/g
Proposed specs for implementation attached for review and discussion.
MCP Architecture proposal:
MCP Tools proposal:
Dynamic Schema proposal:
MCP Security model proposal:
MCP Implementation proposal:
Jun 30 2026
I noticed this independent VyMCP project just dropped a few hours ago. (there is no affiliation between this feature request and their implementation)
1st, July, 2026: Contributor assistance is failing:
Jun 29 2026
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.
Jun 28 2026
Jun 27 2026
Jun 26 2026
I found this as a workaround but again would be handy if things would work out of the box :-)
Another option/workaround would be if something like "config replace" would be supported where the input could be a "config.cmd".
PR that fixes behavior and introduces validation: https://github.com/vyos/vyos-1x/pull/5297
PR submitted for this: https://github.com/vyos/vyos-1x/pull/5296
Jun 25 2026
@o.kuchmystyi I confirm that works, thanks.