onedevatlasBeta
Browse the atlas
AllABAPBTPCAPUI5
AppApptypeAn application you deploy and use, installed into a system or loaded into an application as a component, rather than a library whose functions you call.See every one →What this type is →by a partnerby a partneroriginPublished by an SAP partner or vendor.See every one →

Modernization Agents for SAP on AWS

AWS's suite of agents for SAP modernisation work: custom ABAP converted for S/4HANA, PI/PO interfaces moved to Integration Suite, BW objects moved to SAP Datasphere, deployed into a customer's own AWS account and reached only after registration.

A set of AI agents AWS publishes for SAP modernisation work, deployed into a customer's AWS account from CloudFormation templates and prompted from Kiro, AWS's agentic IDE. The README names six use cases: converting custom ABAP from an SAP ECC system into S/4HANA-compliant code in bulk, refactoring custom ABAP towards SAP's Clean Core extensibility model and standard APIs, converting PI/PO interfaces to SAP Integration Suite, moving BW objects to SAP Datasphere in SAP Business Data Cloud, generating functional and technical specifications from existing code and configuration, and generating and running unit tests before and after a conversion. Each agent is described as model choice, a Model Context Protocol server and Kiro Powers, the steering documents and safety hooks that guide a workload from analysis to converted objects; the agents run against non-production development, sandbox or QA systems, and converted code reaches production through transport and change management. This public repository holds the README, an architecture picture and the registration link and nothing else, so the crawled readings on this page, its tests and CI among them, describe that documentation repository and say nothing about the agents. It succeeds ABAP Accelerator MCP Server, whose README now marks that repository deprecated and no longer maintained and names aws-for-sap/Modernization-Agents-for-SAP-ABAP-on-AWS, the gated repository, as where the latest version lives.

GitHub4 ★
Homepage

Facts

Last pushLicenceMIT

Where it sits

Lives in
ABAP
Provides
ABAP Cloud readinessABAPABAP Cloud readinesscapabilityWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.Platform migrationBTPPlatform migrationcapabilityMoving an application, integration or database from one platform to another: assessing what exists, converting what tooling supports, and adapting what cannot carry over. Language-level compatibility is a separate concern from moving the platform around an application.Agent access to your codeABAPBTPAgent access to your codecapabilityLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Unit testingABAPUnit testingcapabilityTesting application logic without a running business process — and the test doubles that make dependencies on the database and on framework services tractable.
Serves
BTP/BAIP
Requires
Amazon Web ServicesAmazon Web Servicesoutside the atlasThe account the agents are deployed into: AWS ships them as CloudFormation templates that provision compute, networking, IAM roles and agent configuration, and local, ECS Fargate, EKS and Bedrock AgentCore are the documented deployment options.
Optional
DockerDockeroutside the atlasBuilding the container image that is deployed in the AWS Cloud; the README names finch and podman as alternatives to it.SAP ERP (ECC)SAP ERP (ECC)outside the atlasThe source system the custom ABAP is read out of for the ABAP agent; the compatibility table names EHP 6, EHP 7 and EHP 8 on SAP NetWeaver 7.4 and above.SAP S/4HANASAP S/4HANAoutside the atlasThe system the converted ABAP is written for, on-premise or RISE with SAP; the compatibility table names 1809 and above.SAP BW/4HANASAP BW/4HANAoutside the atlasThe warehouse whose objects the BW agent moves; the compatibility table names BW/4HANA 1.0 and 2.0, and SAP BW from 7.4 SP9.SAP Integration SuiteSAP Integration SuiteartifactThe target the converted PI/PO interfaces run on; the compatibility table lists it without a version.SAP DatasphereSAP DatasphereartifactThe target the BW data models are moved into, in Business Data Cloud.

Who is behind it

AWS for SAPAWS for SAPOrganisationMaintains this
In the atlas: maintains 1@aws-for-sapmaintainerabhijeetjangamPersonContributes to this
In the atlas: contributes to 1@abhijeetjangam1 contributor

Before choosing this

Conditions

PracticalFunctional boundary

There is nothing to clone here: "Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation", and that repository answers 404 to anyone who has not registered, so neither the agent code nor the deployment guides can be read before the form is filled in. AWS states the agents are published as an unsupported solution, with customers responsible for testing and securing the code before deploying in production, and that they are intended for non-production SAP environments rather than production systems. The documentation link in the README is still a placeholder.

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Agent access to your codeAn MCP server calls ADT or another SAP API of a running system for an agent.
  • § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
  • § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.

An agent that plans and executes ADT calls is the case section 2.2.2 names. Check that the endpoints are published for the intended use, and that the design runs within a pathway SAP identifies for it.

SAP API Policy 4.2026a →

What it declares

Every artifact

Type
App
Origin
By a partner

As an app

Where it runs
does not say
Distributed through
does not say

Tasks this contributes to1Beta

Agent access to your code1
Let an agent change ABAP in an on-premise systemAn agent reads and changes ABAP in a system the customer runs themselves, on the classic development model, and the change is activated there.Standard ABAPCovers, under conditionsbulk conversion against a non-production system, behind a registration gate
What it does

Works on the whole custom code base rather than an object at a time: an agent prompted from Kiro converts ABAP out of an SAP ECC system into S/4HANA-compliant code in bulk, with unit tests generated and run either side of the conversion. The connection is to a development, sandbox or QA system, and converted code reaches production through transport and change management rather than from the agent. Two authentication models are documented, basic auth with one shared SAP service user and principal propagation carrying each caller's own SAP identity into SAP audit records.

Conditions

Registration with AWS: the public repository carries the README and the registration link, and the agents, deployment guides and documentation arrive only once registered.; Kiro or another agentic IDE AWS lists as supported, which is where the agents are prompted, plus an AWS account the agents are deployed into.; A supported SAP NetWeaver version and a network path between the AWS account and the SAP system.

Remaining work

Register first. The public repository names no tools and no object types, so what the agent reads, writes or activates in the system is not established by anything readable here, and each agent's own prerequisites are stated in its own repository.

All options on the Agent access to your code page →

Connections12

Download
Modernization Agents for SAP on AWS connectionsModernization Agents forSAP on AWSPROVIDES→ provides4provides stated Converts custom ABAP out of an SAP ECC system into S/4HANA-compliant code in bulk, and refactors custom ABAP towards SAP's Clean Core extensibility model and standard APIs. The public repository states the two outcomes and not the rules or checks behind them. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSABAP Cloud readinessprovides stated Connects to a non-production SAP development, sandbox or QA system and runs the analysis and conversion against it, through an MCP server the README names as part of each agent without listing its tools. Two authentication models are documented: basic auth with one shared SAP service user, and principal propagation carrying each caller's own SAP identity into SAP audit records. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 6: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, deployment patterns: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSAgent access to your codeprovides stated Carries two migration paths off products approaching the end of standard support: PI/PO interfaces converted to SAP BTP Integration Suite from functional specification documents, and BW objects moved to SAP Datasphere in Business Data Cloud. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 2: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSPlatform migrationprovides stated Generates and runs unit tests either side of a conversion, which AWS states is to validate business logic and reduce AI hallucination. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSUnit testingNEEDS→ connects to1connects to stated If: The ABAP modernization use case, whose source the README names as your SAP ECC system Reading the custom ABAP it analyses and converts, from a development, sandbox or QA system rather than a production one. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 6: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSSAP ERP (ECC)if→ needs1needs stated The account the agents are deployed into: AWS ships them as CloudFormation templates that provision compute, networking, IAM roles and agent configuration, and local, ECS Fargate, EKS and Bedrock AgentCore are the documented deployment options. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 7: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 4: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSAmazon Web Services→ optionally needs6optionally needs stated If: A container image is built for deployment in AWS Cloud, and Docker rather than finch or podman is the engine used Building the container image that is deployed in the AWS Cloud; the README names finch and podman as alternatives to it. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 7: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSDockerifoptionally needs stated If: The BW modernization use case runs against an SAP BW/4HANA system The warehouse whose objects the BW agent moves; the compatibility table names BW/4HANA 1.0 and 2.0, and SAP BW from 7.4 SP9. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 15: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 2: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSSAP BW/4HANAifoptionally needs stated If: The BW modernization use case is run The target the BW data models are moved into, in Business Data Cloud. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSSAP Datasphereifoptionally needs stated If: The ABAP modernization use case runs against an SAP ECC system The source system the custom ABAP is read out of for the ABAP agent; the compatibility table names EHP 6, EHP 7 and EHP 8 on SAP NetWeaver 7.4 and above. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 15: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSSAP ERP (ECC)ifoptionally needs stated If: The PI/PO modernization use case is run The target the converted PI/PO interfaces run on; the compatibility table lists it without a version. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSSAP Integration Suiteifoptionally needs stated If: The ABAP modernization use case targets SAP S/4HANA The system the converted ABAP is written for, on-premise or RISE with SAP; the compatibility table names 1809 and above. aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 15: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWSSAP S/4HANAif

README

quoted from aws-for-sap/Modernization-Agents-for-SAP-on-AWS under MIT, read
aws-for-sap/Modernization-Agents-for-SAP-on-AWS/README.mdOn GitHub

Modernization Agents for SAP on AWS

Overview

Kiro is AWS's AI-powered engineering agent, designed for enterprises to build production-ready software. With Kiro, customers can build across large codebases with parallel agents, which is ideal for complex, resource-intensive projects like SAP modernizations. This repository provides Kiro-based sample agents that customers and partners can use to accelerate the modernization and deployment of custom SAP Advanced Business Application Programming (SAP ABAP) programs, SAP Business Warehouse (SAP BW), and SAP Process Integration and SAP Process Orchestration (SAP PI / PO) on AWS. These agents bring together model choice, a Model Context Protocol (MCP) server, and Kiro Powers. Kiro Powers include steering documents for repeatable workflows, modernization best practices, and safety hooks that guide each workload from analysis to converted, cloud-native target objects.

SAP is where many organizations house their most critical business logic and data. Custom SAP ABAP programs drive core processes like finance, order management, and supply chain operations. SAP BW underpins the reporting and analytics that enterprises rely on for planning and decision-making. SAP PI / PO serve as the middleware connecting SAP to hundreds of external systems, trading partners, and applications. Modernizing these workloads manually is what makes SAP transformations so time and resource intensive. Additionally, with the end of standard support for SAP BW, SAP PI / PO, and on-premises SAP ERP Central Component (SAP ECC) approaching, customers need to modernize to SAP's cloud-native systems.

With these sample agents, customers can accelerate their SAP modernizations, which are historically one of the most resource-intensive undertakings in enterprise IT. With a single prompt, the sample agents can mass-modernize thousands of lines of SAP ABAP code, migrate hundreds of end-of-support SAP PI/PO interfaces to SAP BTP Integration Suite, and move SAP Business Warehouse (BW) data models to SAP Datasphere in Business Data Cloud (BDC) in hours, not months.

Supported use cases:

  • Make ABAP S/4HANA compliant: convert ABAP code from your SAP ECC system into S/4HANA-compliant code in bulk.
  • Refactor ABAP to clean core: automate refactoring of custom ABAP to align with SAP's Clean Core extensibility model and standard APIs.
  • Modernize SAP PI/PO to SAP BTP: convert PI/PO interfaces to BTP Integration Suite ahead of PI/PO end of standard support.
  • Modernize SAP BW to SAP Datasphere / BDC: move from BW to SAP Datasphere in Business Data Cloud in hours, not months.
  • Generate functional and technical specifications: analyze existing code and configuration to produce business requirements and technical specs, and keep them current.
  • Automate unit testing: generate and run unit tests before and after conversion to validate business logic and reduce AI hallucination.

High-level architecture

High-level architecture

Deployment patterns

Pick a deployment option and follow the guide for the authentication model you need:

OptionBasic authPrincipal propagation
Local (Python)SupportedNot supported
Amazon ECS FargateSupportedSupported
Bedrock AgentCore RuntimeSupportedSupported
Amazon EKSSupportedSupported

Basic auth uses one shared SAP service user, sufficient for most cases since the source side is typically read-only. Principal propagation carries each caller's own SAP identity and is worth the extra setup where SSO is already in place or policy requires per-caller identity in SAP audit records. A local Python run takes minutes once prerequisites are met; the ECS deployment involves VPC networking, a load balancer, and a CloudFormation stack, so plan on an hour or two for a first run.

FAQs

1. What are AWS Modernization Agents for SAP?

AWS Modernization Agents for SAP are a suite of purpose-built AI agents that assist customers throughout the SAP Activate Methodology lifecycle — from discovery and preparation through to deployment and operations, accelerating key SAP transformation workloads such as custom code analysis, interface migration, and BW modernization.

2. What agents are available?

ABAP Modernization Agent— AI-powered custom code analysis, remediation, and S/4HANA upgrade readiness.

PI/PO Modernization Agents— Automated analysis, documentation, and migration of SAP PI/PO interfaces to SAP BTP Integration Suite using functional specification documents.

BW to Datasphere Modernization Agents — Modernization of BW Objects to SAP Datasphere.

3. How do I get access?

Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation. The registration process enables AWS to share updates, new features, and best practices with adopters.

4. How will these agents be delivered to customers and partners?

AWS Modernization Agents for SAP are delivered as AWS CloudFormation templates, enabling automated and repeatable deployment into your AWS environment. This is the same proven delivery mechanism used for other AWS for SAP offerings. The CloudFormation template provisions all required resources — compute, networking, IAM roles, and agent configuration — so you can get started quickly with a consistent, well-architected setup.

5. What are the deployment options?

AWS Modernization Agents for SAP can be deployed on:

Local deployment — For development, testing, and POC scenarios

Central hosted deployment - Deployment options include Amazon ECS, Amazon EKS and Amazon Bedrock Agentcore.

Detailed deployment guides and documentation are provided for each option.

6. Which SAP environments do AWS Modernization Agents for SAP connect to?

AWS Modernization Agents for SAP are intended to connect to non-production SAP environments such as development, sandbox, or QA systems. These agents perform code analysis, conversion, interface conversion, and more - activities that align with the discover, prepare and explore phases of SAP Activate methodology. Converted code and artifacts are then transported to SAP production system through transport and change management processes, ensuring full governance and control.

7. What are the pre-requisites for deploying these agents?

Each agent Github repository outlines detailed pre-requisites. Following are general pre-requisites:

  1. A supported SAP NetWeaver version (refer to each agent's documentation for the exact version required)
  2. AWS account and AWS CLI
  3. Kiro or supported Agentic IDE
  4. Docker,finch or podman to generate container image to be deployed in AWS Cloud
  5. Network path between AWS account and SAP systems

8. How much do these agents cost?

There is no cost for the agents themselves. Customers and partners can register, download, deploy, and use them free of charge. Standard AWS infrastructure costs apply for the underlying compute and AI services.

9. Which IDEs can the AWS Modernization Agents for SAP be used with?

We are distributing the agent sample code designed primarily for Kiro, an AI-powered agentic IDE by AWS. These sample agents are delivered with steering documents to produce deterministic outputs, as part of Kiro Powers that automatically load the right tools and workflows for each SAP workload. These agents are consumed through Kiro using natural-language prompts. Because the agents are built on an open, standards-based integration approach, they aren't locked to a single IDE. Customers can port the steering files and connection setup to work with other agentic IDEs. We will ship new features to Kiro first.

10. What security measures are in place?

AWS Modernization Agents for SAP are provided as open-source code, and it is the customer's responsibility to review, test, and validate the agents within their own environment. AWS performs comprehensive security reviews before publishing, including security scans and threat modeling.

11. Is there a support model?

AWS has officially published the Modernization Agents for SAP as an open-source, unsupported solution. All customers are responsible for testing and securing the code in accordance with their business security standards and policies before deploying in production. Customers are free to customize and extend the agents based on their specific requirements.

If a customer requires a formal support arrangement, we can provide options through AWS Professional Services or several of our AWS partners.

As these agents are strategic to our AWS for SAP business, we do intend to continue investing in improving and maintaining the agents.

12. How do I report bugs or submit requests for new features?

Customers can report bugs through the GitHub repository

13. Will these agents be updated regularly?

AWS will continue to invest in accelerating customer SAP migrations. The Modernization Agents for SAP on AWS provide valuable capabilities to our customers, and we intend to regularly improve and update these agents. As an open-source offering, these agents are provided as-is, without formal commitments around specific updates, bug fixes, or security patches.

Updates will be published via the GitHub repository, and customers can pull the latest versions at their convenience. For customers seeking additional support, options are available through AWS Professional Services or AWS partners.

14. Is there detailed documentation and deployment guide?

Yes. AWS provides comprehensive documentation including:

Architecture overviews

Step-by-step deployment guides for each supported deployment option

CloudFormation template reference and configuration instructions

IAM policy templates and security guidance

Best practices and usage examples

Documentation link: [Link to be included at launch]

15. What SAP systems and versions are compatible?

SAP ProductSupported Versions
SAP S/4HANA (on-premise & RISE with SAP)1809 and above
SAP ECCEHP 6, EHP 7, EHP 8 (SAP NetWeaver 7.4+)
SAP BW/4HANA1.0, 2.0
SAP BW7.4 SP9, check perquisites guide for lower versions
SAP Process Orchestration (PO)7.31, 7.4, 7.5
SAP Process Integration (PI)7.1, 7.31, 7.4, 7.5
SAP BTP Integration Suite
SAP Business Data Cloud (BDC)

16. Are there any restriction on choice for LLM's for using these agents?

AWS Modernization Agents for SAP are optimized for and tested with Anthropic Claude models available through Amazon Bedrock. Claude is the recommended and supported LLM for these agents, and is used for complex SAP code analysis, interface migration, and documentation tasks. While the open-source nature of the agents allows for customization, AWS recommends using the tested Claude model configurations for optimal results.

Partner FAQs

1. How can partners get involved with AWS Modernization Agents for SAP?

Partners follow the same registration-based access model as customers. Register via the AWS registration page to gain access to the GitHub repository containing the agents, deployment guides, and documentation. Partners are encouraged to run POCs on customer environments to build delivery capability and references early.

2. Can partners customize, extend, or build their own solutions on top of AWS Modernization Agents for SAP?

Yes.  The agents are published as open-source, which means partners are free to customize and extend them based on customer-specific requirements. This includes adapting agent logic, adding customer-specific rules, or integrating with additional tools and workflows. Partners can embed these agents into their delivery frameworks, package them as managed services, or list differentiated offerings on AWS Marketplace to reach a broader customer base.

While not a requirement given the open-source nature of these agents, we encourage partners to publicly acknowledge the use of AWS Modernization Agents for SAP in their go-to-market offerings.

3. What skills does a partner team need to deliver with these agents?

Partner delivery teams should be familiar with:

SAP ABAP, PI/PO, BW, or BTP Integration Suite (depending on the agent)

Kiro IDE/CLI — the primary development environment for developing and running agents

Amazon Bedrock and AgentCore — the AWS AI services that power the agents

AWS CloudFormation — for deploying agents into AWS accounts.

For additional questions, please contact your AWS account team or visit aws.amazon.com/sap.

Getting started

To get started, register for access to the sample code and deployment guides through the AWS registration page: Modernization Agents for SAP on AWS, registration

MIT, read

History

Latest

v1.0.0

Notes

Full Changelog: https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS/commits/v1.0.0

Others providing75

ABAP Cloud readiness
  1. abap-cloud-guiReport-style programming model for abap2UI5 on ABAP Cloudfrom ABAP
  2. codepagePolyfill for CL_ABAP_CODEPAGE under Clean Corefrom ABAP
  3. ROSAMCP server answering whether SAP objects are released for ABAP Cloudfrom ABAP
  4. Cloudification RepositorySAP's list of released APIs for SAP Cloud ERP with successorsfrom ABAP
  5. code pal for ABAP — Cloud EditionClean ABAP check set for ABAP Cloudfrom ABAP
  6. Clean-Core.ioHosted workspace redrawing custom ABAP as BPMN and grading itfrom ABAP
  7. Clean Core MeasurementReports Clean Core ATC results per system as Level A to D KPIsfrom ABAP
  8. ABAP Select ConverterConverts classic Open SQL SELECTs to released CDS entitiesfrom ABAP
  9. abap-system-fieldsInjectable wrapper for SY fields and date functions in ABAP Cloudfrom ABAP
  10. Cloudification Repository ViewerBrowser form over SAP's Cloudification Repository for ABAP Cloudfrom ABAP
Agent access to your code
  1. @abap2ui5/mcp-serverMCP server for the abap2UI5 check, deploy and run loopfrom ABAP
  2. arc-1-bopf-enharc-1 extension for reading and maintaining BOPF enhancementsfrom ABAP
  3. HammerNative macOS code editor for ABAP and CDSfrom ABAP
  4. arc-1-lspEdition of ARC-1 that runs ADT calls through adt-lsfrom ABAP
  5. arc-1MCP server over the ADT REST API for ABAP objectsfrom ABAP
  6. arc1-abap-bridgeVS Code bridge between arc-1 and ADT for VS Codefrom ABAP
  7. arc1-adt-abap-mcp-extEclipse add-on enabling the ADT MCP server with read-only toolsfrom ABAP
  8. capforgeMCP server scaffolding CAP and CDS checked by cds compilefrom CAP
  9. ABAP Accelerator MCP ServerAWS's ABAP MCP server for Amazon Q Developer and Kirofrom ABAP
  10. @mcp-abap-adt/coreABAP ADT MCP server published as an npm scope and pluginfrom ABAP
  11. @cap-js/mcp-serverMCP server for CAP development: model and docs searchfrom CAP
  12. chandrashekhar-mahajan/abap-mcp-serverABAP MCP server with ADT tools and five authentication strategiesfrom ABAP
  13. dassian-adtFork of mcp-abap-abap-adt-api with 25 tools and session recoveryfrom ABAP
  14. erpl-adtC++ binary speaking the ADT REST API as a CLI and MCP serverfrom ABAP
  15. bw-modeling-mcpMCP server for BW/4HANA modelling objectsfrom BTP/BAIP
  16. EPOD ADT MCP ServerMCP server for ABAP on the ADT session, in Eclipse or standalonefrom ABAP
  17. ZARC1_EXTENSION_FORMSarc-1 extension for SAPscript and Smart Forms objectsfrom ABAP
  18. fgalastri/MCP_ABAPValidates an ABAP class before it is deployed by converting the global class to a local one and syntax-checking that — plus CDS DDL and table metadata retrieval.from ABAP
  19. fr0ster/mcp-abap-adtABAP MCP server with full CRUD on on-premise and ABAP Cloudfrom ABAP
  20. abapsmithABAP MCP server over ADT with a local journal that can undo writesfrom ABAP
  21. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP systemfrom ABAP
  22. aibap.mcpGo MCP server that writes, activates and runs ABAP classes via ADTfrom ABAP
  23. BellaEclipse plugin bringing Claude into ABAP Development Toolsfrom ABAP
  24. Maherd18/sap-mcp-serverPolicy-checked MCP server for ABAP development over ADTfrom ABAP
  25. sapdumpmcpMCP server reading ABAP short dumps over ADTfrom ABAP
  26. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  27. mcp-abap-abap-adt-apiWrite-oriented MCP server over abap-adt-apifrom ABAP
  28. mcp-abap-adtRead-oriented MCP server fetching ABAP programs, classes, tablesfrom ABAP
  29. SAP MCP Connection ManagerWindows desktop manager handing SAP connections to assistants over MCPfrom ABAP
  30. ABAPilotMCP connector for ECC and on-premise S/4HANA with a licensed SAP sidefrom ABAP
  31. vibing-steampunkADT-to-MCP bridge in Go reaching past what ADT exposesfrom ABAP
  32. ADT MCP ServerLocal HTTP MCP server started from ABAP Development Tools for VS Codefrom ABAP
  33. ABAP Development Tools for VS CodeSAP's ABAP tools in VS Code for editing, debugging, ATC and transportsfrom ABAP
  34. SAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Codefrom ABAP
  35. @sap/mdk-mcp-serverMCP server with five tools for Mobile Development Kit workfrom BTP/BAIP
  36. @sap-ux/fiori-mcp-serverMCP server for creating and editing Fiori applicationsfrom UI5
  37. ABAPDocMCPMCP server turning a transport request into a WRICEF specificationfrom ABAP
  38. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1from ABAP
  39. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP toolsfrom ABAP
  40. @ui5/mcp-serverMCP server for UI5 development with ten toolsfrom UI5
  41. abap-adt-cliCLI that pulls and pushes ABAP packages as local files over ADTfrom ABAP
  42. workskong/mcp-abap-adtLight MCP adapter for ABAP over ADT, documented in Koreanfrom ABAP
  43. KlystronMCP server in ABAP inside the application server, with agent skillsfrom ABAP
  44. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlistfrom ABAP
  45. ABAP-AI-CODE-TOOLSabapGit package adding create, modify and delete tools to ABAP AI Codefrom ABAP
  46. ABAP AI CodeAgentic coding assistant in ABAP that runs as an SAP GUI reportfrom ABAP
  47. VERTEXADT extension for Eclipse and VS Code showing three SAP GUI toolsfrom ABAP
Unit testing
  1. abap2UI5 headless frontendDrives abap2UI5 app classes from ABAP Unit testsfrom ABAP
  2. @abap2ui5/mcp-serverMCP server for the abap2UI5 check, deploy and run loopfrom ABAP
  3. assertFluent assertion helper for ABAP Unit testsfrom ABAP
  4. @abaplint/transpilerTranspiles ABAP to JavaScript to run on Node.jsfrom ABAP
  5. abap_db_preparatorReplays stored database snapshots in ABAP unit testsfrom ABAP
  6. cacamber-BDD-for-ABAPBDD framework turning Given/When/Then into ABAP Unit stepsfrom ABAP
  7. abap-utesthelpHelper classes for ABAP Unit tests and test doublesfrom ABAP
  8. regression_testSnapshot testing library for ABAP, from debugger or unit testfrom ABAP
  9. abapCovUploads ABAP Unit code coverage to codecov.iofrom ABAP
  10. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  11. open-steamgateLocal ABAP server serving /IWBEP/ OData v2 without an SAP systemfrom ABAP
  12. express-icf-shimShim running an ABAP ICF handler behind an Express 4.x serverfrom ABAP
  13. open-abap-coreCore ABAP artifacts for code transpiled by @abaplint/transpilerfrom ABAP
  14. mockup_loaderLoader of Excel-prepared ABAP unit test data, with stub generationfrom ABAP
  15. mockAA free mocking framework for ABAP, published under the Apache License 2.0.from ABAP
  16. Vise_for_ABAPA characterisation-test helper: `ZCL_VISE=>GRIP` records a field's value once and fails a later run if it has changed.from ABAP
  17. abap-senchaBDD/TDD assertion library for ABAP Unit, styled after Chai.jsfrom ABAP
  18. abap-test-containerGitHub-hosted test data container for ABAP Cloudfrom ABAP
  19. abap-unit-runnerApplication job that runs and schedules ABAP Unit tests in the cloudfrom ABAP
  20. adash-servicesBackend exposing ABAP Unit runs and coverage over REST and ODatafrom ABAP

Details

Sources3
GitHub APIdiscovered herechecked
github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWStree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub API
first seen in the atlas
ecosystem and domainabap, ai-and-agents
Contributors1
abhijeetjangam

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:aws-modernization-agents-for-sap
JSON
/artifacts/aws-modernization-agents-for-sap.json
MCP
Connecting an agent