https://github.com/vyos/vyos-1x/pull/5307

Fix PR: https://github.com/accel-ppp/accel-ppp-ng/pull/31/
(PR #30 was closed)

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

PR https://github.com/vyos/vyos-build/pull/1233

PR: https://github.com/vyos/vyos-build/pull/1232

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

https://github.com/vyos/vyos-1x/pull/5305

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:

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

apologies, yes its a feature request. i must have fat fingered the category. can someone change it?

This reads a a core feature request, not exactly to do with Ansible Galaxy collection.
We can look into this from automation perspective once this feature is supported by the product

AI review revealed a bug when with ACTION state, the module also removes L2 configuration.
A module fix is required as such

1st, July, 2026: Contributor assistance is failing:

PR https://github.com/vyos/vyos-build/pull/1231

https://github.com/vyos/vyos-1x/pull/5304

PR: https://github.com/accel-ppp/accel-ppp-ng/pull/30/files

Fix: https://github.com/vyos/vyos-1x/pull/5303

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.

Typos-check pilot COMPLETE — 2026-06-29.

https://github.com/vyos/vyos-1x/pull/5300

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".

https://github.com/vyos/vyos-build/pull/1228