Rap

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. ...

ARC-1 1.0 is here. When I published the first ARC-1 post, I explained why I built an MCP server for ABAP development and why security has to be part of it from the beginning. This post is not another deep dive into every tool. The release notes already do that. For version 1.0 I want to focus on what really changed: ARC-1 became more stable, it can serve multiple SAP systems from one BTP deployment, the BTP and security setup is much better documented, and the project is no longer only one repository. ...

Series note: This post is part of my AI ABAP development series, where I go from AI development in general, to ABAP-specific problems, and then to ARC-1. In the last posts I introduced ARC-1, explained why I built it, showed the BTP architecture, and then used it from Copilot Studio and Joule Studio. Those posts were mostly about architecture and possible use cases. This one is different. This is the use case ARC-1 was originally built for: making real SAP development easier. ...