The Quiet Headline From DevDay: MCP Events
OpenAI adopting the MCP Events spec means an integration you build once can now serve three ecosystems.
Lost under the Dots and Sol announcements, OpenAI added support for the MCP Events specification at DevDay. Anthropic and Google already spoke Model Context Protocol. Now all three do. That means if you build a connector for your internal systems using MCP, it increasingly works across ChatGPT, Claude, and Gemini without a rewrite.
This is the boring infrastructure win that pays off for years. The alternative, which we lived through, is building a separate integration per vendor, each with its own auth and quirks. MCP doesn't erase that entirely, but the Events spec gives agents a common way to react to things happening in your systems.
For the Croatian software houses and internal-tool builders the spec targets, it's a clear bet: invest in MCP servers for your local systems once, and the model layer becomes interchangeable. That's the opposite of vendor lock-in, and it's the part of DevDay that will age best.
If you're wiring AI into your stack, build to the protocol, not the product. The model you use today might not be the one you use next quarter. The standard underneath them is the thing worth depending on.