Everything in the atlas
Type
Domain: 2
Origin
Signals: No date
More: Java
Group by: Capability
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.
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions