Everything in ABAP
Type
Domain: Operations & Runtime
Origin: Independent
Signals
More: Apache-2.0
Group by: Capability
ABAP application options as a structure with a generated editor
Local MCP server on support status from an SAP PAM export
Browser app checking SAP product support status from a PAM export
Logger storing RFC function module call parameters as JSON
Object-oriented wrapper around SAP's Application Log (SLG1)
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.