Everything in the atlas
Type
Domain
Origin
Signals
More: 2
Group by: Domain
MCP adapter turning a CAP Java service into an MCP server
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Generates Open Resource Discovery documents from a CAP Java model
CAP Java plugin for soft delete with a softdelete aspect
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The Maven coordinate its README gives, io.github.miyasuta:cds-feature-softdelete:1.0.0, does not resolve on Maven Central as of 2026-09-07 — you build and install it from source.
CAP Java attachments with database storage and an Object Store module
For deployed environments, the [README](https://raw.githubusercontent.com/cap-java/cds-feature-attachments/302f61c8bb76a0f54f43482ad91d89bf7dc5540f/README.md) excludes the cds-feature-attachments-fs file-system target, which is intended only for local development and testing.
SAP HANA Cloud datasource for CAP Java applications
JDBC runtime for H2 and SQLite in CAP Java
PostgreSQL datasource for CAP Java applications
CAP Java plugin for attachments in SAP Document Management
If document versions are required, the [documented restrictions](https://raw.githubusercontent.com/cap-java/sdm/673769f24ef66fd97daa6a6be41262d45065d3fe/README.md) exclude versioned repositories.
CAP Java plugin for SAP Integration Suite, advanced event mesh
Connects CAP Java messaging to SAP Event Mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Connects CAP Java messaging to Apache Kafka
Business notifications from CAP Java via SAP Alert Notification
Beta connector from CAP Java messaging to Redis Pub/Sub
Remote Services for consuming OData V2 and V4 APIs in CAP Java
SAP Cloud SDK integration for remote REST services in CAP Java
Eclipse plugin bringing Claude into ABAP Development Tools
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
A2A adapter turning a CAP Java service into an LLM-backed agent
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.
CAP Java plugin sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Change log of annotated entity fields for CAP Java
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
Eclipse plug-in turning JSON or XML into ABAP types and DDIC objects
On an [SAP BTP ABAP environment](artifact:btp-abap-environment) system only the generated code is left: DDIC creation is not supported on ABAP Cloud, because classic DDIC object creation over REST is not available there. Create DDIC is also disabled where ADT is not installed in the same Eclipse, and Insert into Editor then works with any editor implementing `ITextEditor` instead of the ABAP one.
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.
Connects a running CAP Java app to CAP console for monitoring
Browser dashboard for a running CAP Java service during development
Maven plugin running CDS build steps in a CAP Java project
Maven archetype generating a new CAP Java project
MCP server for SAP GUI for Windows via the Scripting API
Driving the GUI reaches whatever a user can reach, which is business data and not a development surface. Decide what an agent may do in a session before granting one, not after. Windows only. The HTTP transport is meant for team use but binds to localhost, and unattended multi-user operation is listed as not yet available — a limitation and also the safer default.
MCP server working SAP GUI by screen coordinates
Driving the GUI reaches whatever a user can reach, which is business data and not a development surface. Decide what an agent may do in a session before granting one, not after. It has also not been touched since February 2025, which the maintenance reading states — the three later entries here are where the CI, the Web GUI and the testing framing went.
SAP GUI automation MCP server built on RoboSAPiens
Neither the package manifest nor the repository tree declares a licence.
Declarative status-transition flows on bound actions in CAP Java
Triggers n8n workflows from CAP Java through the outbox