Hey dev.to 👋
We're Obot — an open-source platform built for teams that want to connect AI agents to real tools without the security and governance headaches that come with it.
We started as an MCP Gateway, and #MCP is still at the core of what we do. But we've grown beyond that. Our latest release (v0.22.0, just shipped May 27) gets at a problem we keep hearing from teams: the "client zoo." A single company has users spread across Cursor, Claude, Copilot, and a half-dozen other AI clients — each with its own config model, its own skills directory, its own way of attaching MCP servers. Nobody has visibility into what's actually running on employee machines, and skills get duplicated and inconsistently authored across every team.
v0.22.0 adds centrally managed skills, fleet scanning across AI clients and coding agents, and stronger enterprise controls for MCP. It's the beginning of a broader vision: a control plane for the whole AI tooling stack, not just MCP.
We'll be posting regularly on:
- MCP fundamentals (great if you're just getting started)
- Building and deploying MCP servers
- Security and access control for agentic AI
- Managing AI tooling at enterprise scale
We're developers first, sharing practical content — tutorials, explainers, and honest takes.
If you're building with MCP or wrangling AI tooling across a team, follow along. And we'd genuinely love to know: what's the messiest part of managing AI tools across your org right now?
— The Obot team
