ARC-1 and SAP ADT: Growing Together

When I started ARC-1, there were already MCP servers for SAP’s ADT APIs. My main goal was enterprise-ready access: a service hosted on SAP BTP, with central control over who can use it and what they are allowed to do. For a team, that means being able to give some users read access and others permission to make changes, restrict where changes are allowed, and manage the service centrally. ARC-1’s authorization model combines those controls with the SAP user’s backend permissions. That has been the purpose of the project from the beginning. Several bigger changes built on that foundation. ARC-1 1.0 brought multi-system operation from one BTP deployment, alongside reusable skills and extensions for custom tools. I also extracted the authentication code into a reusable XSUAA package for other MCP servers. More recently, ARC-1 1.7.0 added access to saved application logs and SAPscript texts, giving assistants more context beyond source code. SAP’s ADT extension and its MCP server bring AI…