A free Slack community for engineers, architects, and curious minds who want to explore how AI agents, MCP, and agentic automation are reshaping infrastructure operations.
A free Slack community for engineers, architects, and curious minds who want to explore how AI agents, MCP, and agentic automation are reshaping infrastructure operations.
VibeOps started because every other networking community was aggressively anti-AI. Want to share an agent you built? Dismissed. Discuss MCP for network ops? Dogpiled. VibeOps was built to fix that – a space where real configs, real agents, and real topologies are the currency, and AI-forward thinking is the norm, not the exception.
“I was getting tired of being shut down every time I tried to talk about AI or MCP in network spaces. So I built my own.”
John Capobianco – Head of AI & DevRel, Itential // Founder, VibeOps Forum
VibeOps channels cover the full spectrum of where AI meets network operations.
MCP servers, pyATS, Ansible, NAPALM, and Nornir wired into AI agents — shared, tested, improved.
Claude, GPT, and Gemini running real network ops workflows. What works, what breaks, what’s next.
CML, ContainerLab, and GNS3 VibeOps setups. Share your topology. Get feedback from people who’ve built the same thing.
How to write instructions that network agents actually follow. Practical, tested, production-grade.
AI-gated ServiceNow, GAIT audit trails, digital twins. Governance that keeps humans in the loop.
OSPF, BGP, VXLAN – examined and automated through agent frameworks. The protocols aren’t going anywhere. The way we manage them is.
NetClaw is an open-source, Claude-based network ops agent inside VibeOps the slack space. Mention @netclaw to interact with it directly — ask questions, run tasks, or see agentic ops in action in a live environment.
No gatekeeping. No question too basic. VibeOps was built so that newcomers and seasoned experts sit in the same room and both feel at home.
Replace repetitive CLI work with conversational automation
Build and share MCP-powered toolchains
Event-driven, agentic incident response
Design AI-native operational models
Learn how AI agents actually work in a production network – safely
One of VibeOps’s most significant advantages: the #FlowAI channel gives you a direct line to Itential developers and leaders. Ask questions, share feedback, explore integrations, and follow the roadmap – no support tickets, no marketing filters.
Free. Open to everyone. No question too basic, no background required.
Start with #FlowAI or dive into any channel that matches where you are.
VibeOps is the intersection of “vibe coding” and infrastructure operations — using natural language, AI agents, and MCP to drive network automation instead of writing scripts by hand. It’s a philosophy, a practice, and now a community. The VibeOps Forum is the Slack workspace where practitioners building in this space share their work, ask questions, and push the field forward.
Not at all. VibeOps is explicitly built for enthusiasts, not just experts. If you’re a network engineer curious about what AI agents can actually do in production, you belong here. The culture is generosity over gatekeeping.
MCP (Model Context Protocol) is the standard that lets AI models talk to external tools, data sources, and systems. For network ops, it’s what makes it possible for an AI agent to actually query a device, run a diff, or trigger a change — not just talk about it.
No. VibeOps is practitioner-led, not vendor-driven. Members discuss tools across the ecosystem — Claude, GPT, Gemini, pyATS, Ansible, NAPALM, Nornir, and more. Itential has a dedicated #FlowAI channel where their team is available for direct, unfiltered conversation — but that’s a feature, not the point of the forum.
John Capobianco — Head of AI & Developer Relations at Itential, author of Automate Your Network and the Cisco Press pyATS book — founded and runs the forum. He’s an active member, not just a figurehead.
Yes. VibeOps is free to join and open to everyone. There’s no paywall, no premium tier, no catch.
That’s exactly why now. VibeOps is being built before the textbooks catch up. The people in this community are the ones writing the playbook — joining early means you help define what VibeOps actually means in practice.