Systems | Development | Analytics | API | Testing

Lenses VS Code Plugin - multi-Kafka DevX & governance within the IDE

Engineering is in the middle of an almighty shift. Thanks to AI code-generation solutions, Engineers are being asked to take on a different and wider set of responsibilities in order to be more productive. It’s what’s increasingly being coined as Agentic Engineering - using AI agents to accelerate engineering & operations work while maintaining human oversight, quality and rigour.

Lenses MCP Server with OAuth 2.1

You can now drive Lenses from Cursor, VS Code, IBM Bob or Claude Code without running any extra piece of infrastructure locally. Lenses MCP offers secure tools across topics, schemas, Kafka Connect, SQL processors, consumer groups, datasets and pod logs: everything an engineer would normally click through in the Lenses UI, now reachable from any MCP-compatible client over HTTP.

Introducing Kafka Skills for AI Engineering Agents

If you've written a line of code in the last 18 months, you already know this. Tools like Claude, Codex, Bob, Kiro and Cursor have made agentic software engineering the default. Most developers today are writing prompts as much as they are writing code. That shift changes what ‘developer experience’ means. Clean UIs, useful tools and good docs are still the foundation but the focus has shifted to ensuring a coding agent actually knows what it is doing, in the hands of a developer.

New IDE-Like Studio for Kafka: Lenses 6.2 Features & Demo

Discover the powerful new IDE-like Studio in Lenses 6.2. Learn how to manage your Kafka clusters, discover topics across multiple environments, and perform side-by-side comparisons of dev and staging data. We also dive into the new ways to interact with streaming data, including the CLI, VS Code plugin, and the new MCP server for AI agents and chatbots. Whether you're a developer troubleshooting schema mismatches or a data engineer managing complex Kafka estates, the new Lenses Studio provides the tools you need to stay in context and work efficiently.

Don't trust AI agents on Kafka. Unless you have OAuth 2.1. (Live)

Every engineering team is onboarding AI agents. Most are doing it without a governance model - static API keys, no audit trail, no way to revoke access if something goes wrong. Join us on April 15th as we go live on the topic everyone is talking about but few are solving: how to govern AI agent access to streaming data.

How to give AI Agents secure access to systems (with remote MCP servers)

AI agents need access to your systems. But are you sure they're accessing them securely? In this video, Tun @DataSurfer breaks down the way most teams give AI agents access today: static API keys, shared credentials, no audit trail. It's a disaster waiting to happen, but what exactly can teams do about it?

Your AI agent is one misconfigured MCP server away from leaking production data.

2025 was vibe coding. 2026 is Agentic Engineering - and the security rules haven't caught up. AI agents now have direct access to your databases, your APIs, your Kafka clusters. The protocol giving them that access is MCP. And most teams have no idea how exposed they are. We are fixing this problem with OAuth 2.1.