From cloud to edge: Expanding agentic development on Arm with new Kiro Powers

Introduction

When we announced the Arm MCP Server last October, the goal was straightforward: Make it easier and faster to develop on Arm-based platforms with your favorite AI coding agent.

Today, we are furthering that vision.

With two new Kiro Powers, the Arm MCP Server supports agentic workflows that span from cloud infrastructure modernization to embedded production hardware transitions. From cloud to edge, the Arm MCP Server now underpins structured agentic development across the entire Arm compute continuum.

What is the Arm MCP Server and Kiro Powers?

The Arm MCP Server exposes Arm-curated tools, technical knowledge, and structured prompts directly to AI coding agents. It runs locally, behind enterprise firewalls, enabling secure development while allowing agents to invoke expert-crafted workflows.

Generic AI assistants generate code, but without structured access to domain-specific tools and knowledge, their output quality depends entirely on how well the developer frames the problem. There is a chicken-and-egg dynamic: To get expert-level output, developers must already know how to encode expert-level architectural intent into the prompt.

The Arm MCP Server resolves this by embedding Arm architectural knowledge directly into the agent’s workflow. This reduces reliance on prompt craftsmanship and places an Arm expert in every team.

To date, the Arm MCP Server’s primary use-case has been around enabling cloud migrations – from x86 to Arm-based clouds like the new AWS Graviton 5. The first agentic integration was the GitHub Cloud Migration Agent.

After close collaboration with AWS teams, the Arm MCP Server’s capabilities will now be supported in Amazon’s agentic Integrated Development Environment (IDE), Kiro. Powers provide developers specialized context and tools to Kiro agents on-demand. Two Kiro Powers are available now:

• For cloud developers: Plan and Migrate to Graviton
• For edge developers: Perform Migration between Arm SoC

Let us dive into each in turn.

Cloud: Plan and Migrate to Graviton

The Graviton Migration Power demonstrates how Arm expertise can be operationalized inside an AI-native IDE. Developed in collaboration with AWS Compute Solution Architects, this Power builds on the GitHub Cloud Migration Agent and is customized specifically for migrations targeting AWS Graviton processors.

It helps developers:

• Assess x86 codebases for Arm readiness
• Identify instruction-set dependencies and performance assumptions
• Refactor containerized workloads
• Align CI/CD pipelines for Arm-native builds

This capability is valuable for any development team considering moving to AWS Graviton to optimize costs. For organizations modernizing cloud infrastructure, Graviton is often the economic inflection point. The Graviton Migration Power takes the guesswork out of migration decisions, replacing uncertainty with a structured, step-by-step workflow guided by an intelligent agent.

Edge: Perform Migration between Arm SoCs

The Arm SoC Migration Power addresses a different but equally complex challenge. Moving embedded codebases between Arm-based platforms.

Modern embedded, automotive, and robotics teams increasingly develop software before production hardware is available. This “shift-left” approach accelerates time-to-market, but it guarantees at least one major platform transition during the project lifecycle.

A typical progression might look like:

1. Cloud development (AWS Graviton)
2. Low-cost Arm development boards (e.g., Raspberry Pi)
3. Production automotive SoCs (e.g., NXP i.MX 952)

And while a core strength in targeting Arm-based devices is code portability across devices, portability does not mean equivalence.

Code that compiles across Arm platforms can behave very differently due to variations in vector handling, memory subsystems, cache topology, power-state transitions, and accelerator availability. These differences are essential in performance-critical systems where every nanosecond from an incoming photon to actuating a motor (or applying a break) matters.

The Arm SoC Migration Power follows a spec-driven approach driven by an expertly crafted prompt in collaboration between AWS and Arm teams. Instead of blindly generating changes, it guides developers through:

• Discovering architectural differences
• Analyzing CPU microarchitecture and SIMD capabilities
• Assessing memory hierarchy and cache behavior
• Evaluating power management and accelerators
• Planning and validating controlled transitions

Developers who want to walk through the full workflow can follow the Arm SoC migration learning path:

Arm SoC migration learning path

Instead of treating migration as a final-stage porting task, teams can approach it as a deliberate engineering transition. The Arm SoC Migration Power makes architectural differences explicit, helps teams define performance and safety targets upfront, and reduces the risk of late-stage regressions when moving to production hardware.

Conclusion

The Arm MCP Server is now tightly integrated into Kiro through the Graviton Migration Power for cloud modernization and the Arm SoC Migration Power for embedded and production transitions. With these new Powers, the Arm MCP Server becomes an active participant in platform transitions, bringing Arm architectural expertise directly into agentic workflows from cloud to edge.

If you are migrating workloads to AWS Graviton, or transitioning embedded software between Arm SoCs, these Powers are available now. Try them today:

Perform Migration between Arm SoC  Plan and Migrate to Graviton