Everything in the atlas
Type
Domain
Origin: Not from SAP
Signals
More: 2
Group by: Capability
Shared root exception class and text getter for USI developments
ABAP API for Google Apps, with upload to Google Docs
No published releases; repository quiet for 97 months.
ABAP framework wrapping the Google Sheets API for SAP S/4HANA
No published releases; repository quiet for 81 months.
Generator of ABAP type definitions from JSON structures
ABAP OData service for attachments and comments via GOS
No published releases; repository quiet for 66 months.
Library that reads and generates Excel spreadsheets from ABAP
ABAP template engine for Excel, Word, HTML and PDF
ABAP connector to Kafka through the Confluent Kafka REST Proxy
No published releases; repository quiet for 57 months.
ICF handler receiving Amazon SNS notifications in an ABAP system
No published releases; repository quiet for 64 months.
Fiori launchpad notification for application log errors
RSS feed publisher for content from an SAP NetWeaver ABAP system
No published releases; repository quiet for 93 months.
JSON adapter exposing ABAP function modules over HTTP
Input arrives only as JSON, or as plain XML if the ABAP built-in transformation is switched on, whatever the output format is set to. Cross-site calls are limited to JSONP: the maintainer lists CORS support as planned.
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
C++ binary speaking the ADT REST API as a CLI and MCP server
A compiled binary rather than an npm package, shipped prebuilt per platform and through pip and uvx. It collects anonymous usage telemetry by default, switched off with `--no-telemetry` or `DATAZOO_DISABLE_TELEMETRY=1`. And the BW reach is what distinguishes it — if the work is plain ABAP, that half is weight you are not using.
ABAP MCP server with full CRUD on on-premise and ABAP Cloud
Two licences, by which package you install: the standalone server, `@mcp-abap-adt/core`, is AGPL-3.0-only, a licence to read before shipping anything built around it; the library, `@mcp-abap-adt/lib`, is Apache-2.0. The destination model also expects service keys sitting in a local directory, which is a secrets decision to make deliberately.
arc-1 extension for SAPscript and Smart Forms objects
Smart Form content cannot be read or written, and HR Forms (`PE51`) are not implemented. Installing it needs SAP GUI or WebGUI once, to register the OData services in `/IWFND/MAINT_SERVICE` and to redefine the write service in `SEGW`, and the extension is built against a locally linked ARC-1.
Read-only security analysis MCP server for SAP audits and SoD review
Read-only does not mean low-stakes: a complete picture of who can do what in an SAP system is exactly what an attacker would want, and the ready-made endpoint is the vendor's rather than yours — the README also documents running the server yourself. The authentication is careful; the question of what leaves your landscape is still yours.
Agent skill for off-stack ABAP Unit tests and an abaplint gate
Not a substitute for testing in a system: the README states that any class calling the database, classic BAPIs or HTTP is shimmed out and stays an on-stack ATC and ABAP Unit concern, and that an off-stack green is CI-grade provenance rather than an in-system pass. It also assumes a particular shape of project. The ABAP has to be abapGit-serialised into a Git repository, Node.js 22 or later has to be available locally and in CI, and the CI has to be GitHub Actions.
Claude Code plugins with Clean ABAP rules and templates
Knowledge with no reach: without an MCP server connected it can tell an agent what to write and cannot let it read or run anything. The rules target the ABAP Cloud development model, so a classic on-premise codebase is not what they are written against.
Agent skills for Clean ABAP, ADT in VS Code and guardrails
No published releases; repository quiet for 34 months.
ABAP client library for IBM watsonx.ai APIs
ABAP API for OAuth 2.0 authentication
No published releases; repository quiet for 97 months.
OA2C_SPECIFICS implementation for Microsoft Azure OAuth 2.0 in ABAP
No published releases; repository quiet for 27 months.
Authority check helper class used across SchwarzIT's USI reports
Blowfish cipher in ABAP, ECB and CBC modes
No published releases; repository quiet for 83 months.
Eclipse plugin linking ABAP transports to SAP Cloud ALM features
An Eclipse installation older than the 2026-03 release, or a Java below 21, cannot take it: both are listed prerequisites, and 2026-03 is named as the oldest release the current ADT installs on. The tenant, region, client ID and client secret are entered per installation in Eclipse preferences, so each developer configures the Cloud ALM connection in their own IDE.
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
ABAP application options as a structure with a generated editor
Logger storing RFC function module call parameters as JSON
Object-oriented wrapper around SAP's Application Log (SLG1)
UI5 app for OData test requests and ABAP Push Channels
Software-engineering metrics for an ABAP class or package
No published releases; repository quiet for 43 months.
TypeScript SDK over SAP's headless adt-ls language server
What adt-ls cannot do headless the maintainer puts out of scope, so a consumer that needs an ADT call the language server does not expose is back to speaking ADT itself. The README states the current runtime compatibility as verified on macOS arm64, against adt-ls 1.1.2 as the minimum and `1.1.2.202608131517` as the version tested. An Eclipse installation does not supply that runtime: SAP versions the two separately, so the VS Code extension has to be installed even where nobody opens VS Code.
Eclipse plugin linking ABAP transports to SAP Cloud ALM features
An Eclipse installation older than the 2026-03 release, or a Java below 21, cannot take it: both are listed prerequisites, and 2026-03 is named as the oldest release the current ADT installs on. The tenant, region, client ID and client secret are entered per installation in Eclipse preferences, so each developer configures the Cloud ALM connection in their own IDE.
Browser page searching SAP transaction codes
Windows build packaging Eclipse with ADT as a portable IDE
In-system search tool for CDS views
No published releases; repository quiet for 29 months.
Demonstration of off-stack ABAP development on Node.js
No published releases; repository quiet for 93 months.
No published releases; repository quiet for 59 months.
Demonstration of off-stack ABAP development on Node.js
Report pushing ABAP objects to SAP Translation Hub and back
No published releases; repository quiet for 43 months.
Demonstration of off-stack ABAP development on Node.js