Systems | Development | Analytics | API | Testing

Designing MCP Servers for Observability

Observability is the key to understanding and improving MCP servers. These servers connect AI agents to tools, but without visibility, issues like slow responses, errors, or security risks can go undetected. Observability helps track how agents interact with tools, pinpoint failures, and optimize performance.

Everything we announced at our Agentic Quality Engineering Platform launch

Over 1,000 people around the world tuned in as Tricentis CEO Kevin Thompson and VP of AI David Colwell unveiled our new integrated platform, followed by a live demo from Enterprise Solution Architect Matt Serpone. From our headquarters in Austin, Texas, we unveiled a unified solution designed to help enterprises treat quality as a coordinated system rather than a collection of disconnected tools.

What Breaking AI Applications Taught Us About Building Reliable Ones

The global industry is currently in a feverish rush to "AI-enhance" every facet of the digital landscape. However, a critical distinction has emerged: while building an AI-integrated application is relatively simple, engineering one that maintains operational integrity in a production environment represents a watershed moment for modern engineering teams. BugRaptors spent the last year inside the intricate internal logic and non-deterministic layers of AI application testin g.

How to Differentiate and Scale Your Agency with AI Analytics

Automated reporting saves your team’s time. AI analytics saves your client relationships — and wins you new ones. Automated reporting for clients means your agency pulls performance data from every agreed source through APIs into one system, applies consistent metric definitions and formatting, and delivers the same client-ready view on a schedule — without anyone copying and pasting.

AI Coding Agents Break What Works

Your AI coding agent just made every test pass. Ship it, right? Not so fast. A growing class of AI-generated bugs doesn’t come from writing bad code. It comes from the AI changing working code to accommodate its own mistakes. This isn’t a theoretical risk. It’s happening now, in production codebases, and it’s harder to catch than any bug the AI might introduce from scratch.

Policy-Driven APIs for AI: Best Practices | DreamFactory

Before rolling out policy-driven APIs, it's crucial to have a governance framework in place. This framework should clearly outline who makes decisions, how approvals work, and how exceptions are handled. Interestingly, while 71% of organizations claim to have data governance programs, only 25% actually put them into practice. Even fewer - just 28% - have enterprise-wide oversight for AI governance roles and responsibilities.

DreamFactory 7.4.5 Release: MCP Aggregate Data Tool, Cursor IDE Support, and Production Stability

DreamFactory 7.4.5 ships the aggregate_data MCP tool — a purpose-built tool that lets AI agents compute SUM, COUNT, AVG , MIN, and MAX directly on the database server in a single call. This release also adds Cursor IDE OAuth compatibility, a desktop OAuth success page for smoother onboarding, server-side aggregate expression support across all SQL connectors, and critical MCP daemon stability improvements including request timeout guards and global error handlers.

How to Teach Your AI Agent to Build Keboola Data Apps

You can build Data Apps inside Keboola with Kai. But what if you prefer working with Keboola via MCP, in Claude Code, Cursor, or another AI-powered editor? Want to build a JavaScript Data App that Kai doesn't support yet? That's what the Keboola AI Kit is for. It's a set of skills you install into your agent so it knows how to work with Keboola - how to query your data, how to structure a Data App, how to deploy it. Here's how to set it up.

Does your AI stack need a session layer? A maturity framework for teams building AI agents

Most teams building AI agents start with HTTP streaming. It's the right starting point. Every major agent framework defaults to it, it gets tokens on screen fast, and for a single-user prompt-response interaction it works well. The question is when it stops being enough - and how to recognise that before it turns into user experience problems, engineering waste, and technical debt that constrains what your product can do.