New Relic announced the integration of its Model Context Protocol (MCP) Server with Kiro, Amazon Web Services' (AWS) AI-native, agentic development environment.
The one-click integration enriches agentic coding workflows with real-time observability insights, closing the feedback loop between planning, shipping, and validating to boost developer velocity, improve code quality, and reduce mean time to resolution (MTTR) of performance issues.
With the New Relic integration for Kiro, engineers can query live metrics, events, logs, and traces in natural language, bringing New Relic AI directly into Kiro's spec-driven workflow — no context-switching required.
“As organizations navigate this agentic transformation, they face a critical and immediate need to safely unify AI coding agents and live business data,” said New Relic Chief Product Officer Brian Emerson. “By integrating our MCP Server with Kiro, we are combining the rigorous, spec-driven development on AWS with New Relic’s deep operational insights. The result is a seamless, one-click solution that empowers developer teams to confidently ship quality code with minimal operational friction and toil.”
The integration enables Developers, DevOps engineers, and SREs who use Kiro to:
- Surface real-time production context inside Kiro's spec-driven development cycle: Developers can query New Relic's full-stack telemetry directly inside Kiro to validate code performance against technical specs. This unifies planning and execution, ensuring AI-generated code changes are operationally validated before shipping, while keeping developers focused within the integrated development environment (IDE).
- Unify agentic development workflows with observability for AI: By feeding New Relic’s observability insights directly to Kiro’s agents, teams can shift from manual troubleshooting to AI-assisted investigation. As a result, developers can rapidly identify root causes and implement precise code fixes for performance bottlenecks, significantly slashing MTTR.
- Enable instant observability with one-click implementation: Built as a Kiro power, the integration enables one-click deployment that eliminates the need for complex, manual configuration. This allows engineering teams to immediately access rich observability insights, accelerating their transition to spec-driven, AI-native development.
The Latest
For decades, traditional observability tools have forced IT professionals to sift through endless dashboards, turning a flood of alerts into actionable insight and driving widespread burnout. While enterprises adopted AI to eliminate this friction, most still deploy it reactively rather than proactively ... As systems become more complex and IT moves to the center of business strategy, a reactive posture is unsustainable ...
Ask an operations team what they monitor and you will hear a familiar list: latency, errors, throughput, uptime. Those signals still matter for AI, but they no longer answer the most important question. As Krishna Sai, CTO of SolarWinds, puts it: "Traditional observability tells you a system is running. AI observability tells you whether it's still reasoning soundly. Those are completely different questions" ...
AI observability serves several roles across an organization. AI engineers use it to build, evaluate, and improve AI systems. SREs use it to operate those systems reliably and efficiently in production, including managing their cost. Leaders need it to connect AI behavior and operational performance to business outcomes. The common need is a clear understanding of whether AI systems are delivering the intended result ...
Part 4 outlines the challenges enterprise face when adopting AI observability. The main challenge is that AI complexity compounds at every stage of maturity. LLM-based applications introduce new behavior, dependencies, and quality considerations, while Agentic AI adds further failure modes as systems make decisions and take actions ...
Part 3 reports on the current state of AI observability. Most experts agree: enterprises are moving faster with AI than they are with the operational discipline needed to run it safely ...
When discussing AI Observability, one of the first questions that arises: Is this just an extension of traditional observability or is this a whole new type of tool? Part 2 compares traditional observability with AI observability ...
In this extensive 14-part series that will post over the next three weeks, experts across observability and AI will provide insight and opinions on the need for AI Observability, the challenges, the benefits, the current state, and predictions for the future ...
Amid rising complexity, organizations are moving quickly toward agent-driven operations: AgenticOps, according to The Impact of Agentic AI on Network Operations, a new report from Cisco ...
AI, automation, and enterprise software give organizations an extraordinary amount of leverage. Work that once required hours can happen in minutes. Information buried across systems can be analyzed almost instantly. Complex workflows can be coordinated across teams with far less manual intervention. That leverage creates a temptation to start with the technology ...
Everyone wants to talk about models. Compute clusters. Benchmark scores that climb a fraction of a point and make headlines anyway. It's an easy conversation to have because it's measurable. But it's also increasingly beside the point ...