mcp-abap-adt

Based on the available evidence, this is best understood as a specialized infrastructure connector for SAP ABAP workflows, not a broadly validated AI coding platform. The current evidence is almost entirely the official GitHub repository description, which is enough to support what it is and which SAP environments it targets, but not enough to prove real-world adoption, reliability, performance, or enterprise-scale production use. Popularity proof is also weak so far: there is no visible GitHub growth signal, social repost wave, or ranked-list discussion sample here.

In practice, it is more accurately described as an “MCP adapter for ABAP ADT” or a protocol bridge that lets MCP-compatible AI clients operate on ABAP development objects, rather than a full IDE, low-code suite, or generic SAP automation bot. The repository description explicitly mentions SAP BTP ABAP Cloud and on-prem ECC/S/4HANA support, full CRUD, and authentication methods such as JWT/XSUAA and service-key auth. From that, a conservative conclusion is that it helps existing SAP/ABAP teams connect AI tooling into their development environment for reading, creating, and modifying development artifacts.