While work on the varlink-http-bridge for systemd I had this idea that a lot of the tech could be used to build an #MCP for systemd via #varlink. So here it it is: https://github.com/mvo5/systemd-mcp - it auto-discovers systemd's varlink sockets, introspects the IDL, and exposes every method as a typed tool. On a typical system that's 50-80+ tools: units, journals, credentials, factory reset, you name it. What could possibly go wrong :) ? (requires systemd v260+)
Remote
Michael Vogt
@michaelvogt@mastodon.social
mastodon 4.8.0-nightly.2026-10-06I like tea and free software
0 Followers
0 Following
9 Posts
Joined January 27, 2026
github:
Super excited to join Amutable and work on the next level of secure Linux: https://amutable.com/blog/introducing-amutable 🚀
#amutable #linux #systemd #⊼mutable #integrity
Replying to
@rfc1036 @pid_eins @arianvp Thanks again @arianvp for the very nice gist - I created https://github.com/systemd/varlink-http-bridge/pull/13 that should implement this "--more" streaming via json-seq and connection pipelining in the bridge now without websockets- really cool to get these kind of improvement suggestion so quickly/nicely.
Some cool news about the rust based varlink-http-bridge - its now under the systemd org and @zeenix ported it to zlink in https://github.com/systemd/varlink-http-bridge/pull/7 - many thanks!
I'm exicted to see more rust usage in the systemd org and hope it will keep growing. Help (especially from experienced rust developers) with the varlink-http-bridge is of course always welcome!
Replying to
Replying to
Replying to
@arianvp @pid_eins Thanks Arian for the gist! The main reason for the websocket stuff is/was the protocol switching that Lennarts mentioned. But of course your right that just for the --more we won't need it and can use http streaming or SSE. I expect that we will add either http stream or sse (or both) pretty soon to make it easier for traditional curl usage to call e.g. io.systemd.JournalAccess.GetEntries. But I also want to make sure we DTRT so this kind of feedback is much appreciated!
Replying to
@diegovsky @pid_eins Varlink streaming is supported when using the websocket, its pretty nice with the new varlink-protocol feature of systemd v260+: varlinkctl call --more http://localhost:1031/ws/sockets/io.systemd.JournalAccess io.systemd.JournalAccess.GetEntries {}. The regular API does not currently support streaming, I was thinking we could add it via SSE but not fully sure yet