Why is this in future tech? idk. But having an agent talk to an MCP server to provision Venice regions sounds neat and futuristic.

We've got a number of half formed toys of that nature. We've got another repo called the 'crack team (on crack)'. It's a setup where you've got a supervisor agent, and then agents in different roles (coder, qa, ops review, sec review, user). It's the supervisors job to receive assignments, create user stories, and then dispatch them to each agent in it's role in a kind of state machine fashion. They use slack to go back and forthe and give updates/pass context, and I can watch it. For awhile they just used log files, but that had other problems. So for now we're using slack. This works ok. Little ghetto, but at least I can watch it work. We use this for what I call our 'unopinionated work', which is to say "this is a small to medium sized task that I don't think I can bring a ton of nuance to beyond the design stage". So thinks like API integrations or UI stuff.