Systems | Development | Analytics | API | Testing

Last updated: May 2026 A PostgreSQL MCP server is a service that exposes PostgreSQL databases as tools an AI agent can call through the Model Context Protocol (MCP). Rather than giving an LLM direct database credentials, you put an MCP server between the agent and the database. The agent discovers what queries it can run, calls them as named tools, and the MCP server translates those calls into safe, governed SQL against PostgreSQL.

These terms show up in every other LinkedIn post about AI. Everyone uses them slightly differently. So here's how we think about them at Keboola, and what they look like in practice.

What marketing mastered years ago, product teams are only now beginning to understand. For decades, marketing has operated on a simple but powerful principle: don't make your customers come to you, go to them. Meet them on the channels they already use, speak in the language they already speak, and show up where they already spend their time. The result was omni-channel marketing, a discipline that transformed how brands engage with the world.

The previous posts in this series built the security model layer by layer: identity, configuration governance, service account automation, compute policies, and production model serving. This final post covers what holds all of it together: the monitoring and audit layer that records every action, every API call, and every resource event and makes the full picture visible to the people responsible for it. It accompanies our Enterprise AI Infrastructure Security YouTube series.

Playwright test agents are LLM-driven execution loops that wrap Playwright's browser automation in a goal-oriented reasoning layer. Instead of executing pre-written scripts, an agent receives high-level intent ("complete checkout and verify the success modal"), inspects the page's accessibility tree, and chooses which Playwright tool to invoke next. The Model Context Protocol (MCP) is the standardized bridge that exposes Playwright capabilities to the LLM and returns structured page context back.

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.

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.

AI chatbots now sit in customer journeys, product workflows, help centers, and decision paths. They represent brands, influence user trust, and increasingly, they make autonomous judgments.

Quick summary: AI is creating anxiety and excitement — teams can get more work done faster, but does all this automation leave the worker behind? Not necessarily, says one performance engineering leader. The AI revolution, he says, is another technological wave. To ride it, performance engineers must embrace the change.