New Relic announced a one-click integration between its MCP Server and Kiro, AWS’s AI-native agentic development environment, so developers can bring New Relic observability context into coding and incident-resolution workflows.
New Relic announced a one-click integration connecting its MCP Server with Kiro, AWS’s AI-native agentic development environment, to bring observability data into agent-assisted software development.
In a June 17 press release, New Relic said the integration links its Model Context Protocol Server with Kiro, which it describes as AWS’s AI-native agentic development environment. New Relic said the goal is to give development teams access to observability insights while they are writing, reviewing, and troubleshooting code.
New Relic’s accompanying blog post says the connection is intended to let agentic coding workflows use real-time telemetry from New Relic inside the development environment. The company frames the feature around two common software workstreams: accelerating development and improving incident response.
The integration is presented as a one-click setup. Kiro’s own documentation for “Powers” lists “New Relic Observability” as an available power. Kiro describes powers as one-click installs that bundle MCP tools, steering files, and hooks for workflows such as development and observability.
The Model Context Protocol, or MCP, is designed to let AI tools connect with external systems in a structured way. In this case, New Relic says its MCP Server can expose observability context from New Relic to Kiro-based workflows.
That matters because coding assistants and agentic development tools can be limited when they lack operational context. A tool may suggest code changes, but it may not understand whether a service is showing elevated error rates, latency regressions, or deployment-related problems unless that telemetry is available to it.
New Relic’s announcement says the Kiro integration is meant to add that missing context. The company specifically cites observability insights and reduced mean time to resolution, or MTTR, as intended outcomes.
According to New Relic, the integration is aimed at developers working in an agentic environment who want observability data available as part of their normal workflow. The company’s blog post says teams can use the connection for development and incident-resolution scenarios.
A practical example would be a developer investigating a production issue while using Kiro. Instead of switching between a development environment and observability dashboards, the connected workflow could make New Relic telemetry available to the AI-assisted environment through MCP tooling. New Relic says this can help teams understand incidents and act on operational data more directly.
Kiro’s documentation supports the integration’s packaging model by listing New Relic Observability among available powers and describing powers as installable bundles for adding capabilities to the environment.
The confirmed facts from the cited sources are narrow: New Relic announced the integration; it connects New Relic’s MCP Server with Kiro; Kiro lists New Relic Observability as an available power; and New Relic says the integration is intended to add observability insights to agentic development workflows and help reduce MTTR.
The sources do not provide independent performance benchmarks, customer case studies, or quantified MTTR improvements for this specific integration. For that reason, claims about productivity gains or incident-resolution speed should be treated as New Relic’s stated objectives rather than verified results.
The announcement reflects a growing pattern in software tooling: AI coding environments are increasingly being connected to operational systems rather than being limited to code generation alone. By linking Kiro with New Relic through MCP, New Relic is positioning observability data as context that agentic development tools can use during both build and response workflows.
For teams already using New Relic and evaluating Kiro, the integration may reduce the friction of bringing production telemetry into AI-assisted development. Its real value will depend on how well the connected workflows surface relevant signals, how teams govern AI-assisted actions, and whether the integration improves everyday debugging and incident practices in production settings.
New Relic announced a one click integration connecting its MCP Server with Kiro, AWS’s AI native agentic development environment, to bring observability data into agent assisted software development.
What New Relic announced In a June 17 press release, New Relic said the integration links its Model Context Protocol Server with Kiro, which it describes as AWS’s AI native agentic development environment.
New Relic said the goal is to give development teams access to observability insights while they are writing, reviewing, and troubleshooting code.
Continue reading
