<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Obot AI</title>
    <description>The latest articles on DEV Community by Obot AI (@obot_ai).</description>
    <link>https://dev.to/obot_ai</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3954698%2F868082a1-4259-4ada-8e83-e552c0d5d063.png</url>
      <title>DEV Community: Obot AI</title>
      <link>https://dev.to/obot_ai</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/obot_ai"/>
    <language>en</language>
    <item>
      <title>MCP Security Has Gone Mainstream</title>
      <dc:creator>Obot AI</dc:creator>
      <pubDate>Fri, 29 May 2026 15:48:13 +0000</pubDate>
      <link>https://dev.to/obot_ai/mcp-security-has-gone-mainstream-4jn5</link>
      <guid>https://dev.to/obot_ai/mcp-security-has-gone-mainstream-4jn5</guid>
      <description>&lt;p&gt;&lt;em&gt;By Shannon Williams, President &amp;amp; Co-founder of &lt;a href="https://obot.ai" rel="noopener noreferrer"&gt;Obot AI&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A few days ago our outside counsel forwarded me a risk explainer on MCP from a major law firm's technology transactions group. It was the third in a series they've been running on MCP — laying out a NIST-based control framework for deploying MCP connectors in regulated enterprises.&lt;/p&gt;

&lt;p&gt;That's not a developer audience. That's general counsel, CISOs, and procurement teams.&lt;/p&gt;

&lt;p&gt;A year ago, MCP was something you explained to enterprise architects from scratch. Now the questions have shifted from "what is this" to "we already have this in production, our auditors are asking, what's the control framework."&lt;/p&gt;

&lt;p&gt;MCP security has gone mainstream — and in this post I break down what that shift actually means and the four operational controls every organization deploying MCP needs to have in place.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://obot.ai/blog/mcp-security-has-gone-mainstream/" rel="noopener noreferrer"&gt;obot.ai&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>mcp</category>
      <category>ai</category>
    </item>
    <item>
      <title>Hello from us at Obot AI!</title>
      <dc:creator>Obot AI</dc:creator>
      <pubDate>Thu, 28 May 2026 15:26:10 +0000</pubDate>
      <link>https://dev.to/obot_ai/hello-from-us-at-obot-ai-59n0</link>
      <guid>https://dev.to/obot_ai/hello-from-us-at-obot-ai-59n0</guid>
      <description>&lt;p&gt;Hey dev.to 👋&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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 (&lt;a href="https://obot.ai/blog/announcing-obot-platform-v0-22-0-centrally-managed-skills-fleet-scanning-and-enterprise-controls-for-mcp/" rel="noopener noreferrer"&gt;v0.22.0&lt;/a&gt;, 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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;We'll be posting regularly on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;MCP fundamentals (great if you're just getting started)&lt;/li&gt;
&lt;li&gt;Building and deploying MCP servers&lt;/li&gt;
&lt;li&gt;Security and access control for agentic AI&lt;/li&gt;
&lt;li&gt;Managing AI tooling at enterprise scale&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We're developers first, sharing practical content — tutorials, explainers, and honest takes.&lt;/p&gt;

&lt;p&gt;If you're building with MCP or wrangling AI tooling across a team, follow along. And we'd genuinely love to know: &lt;strong&gt;what's the messiest part of managing AI tools across your org right now?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;— The Obot team&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>agentskills</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
