Everything in the atlas
Type
Domain: Protocols & APIs
Origin: 3
Signals
More
Group by: Capability
CDS plugin adding embedded analytics to CAP for SAP Analytics Cloud
Not in a project on CAP 7 or earlier: the package declares `@sap/cds` >=8 and `@sap/cds-compiler` >=5 as peer dependencies.
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
GraphQL protocol adapter generated from the CDS model
HL7 FHIR implementation for storing and exchanging health data
ABAP classes for calling Azure services from SAP processes
HTTP client for classic on-premise ABAP and ABAP Cloud
No published releases; repository quiet for 32 months.
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Exports AsyncAPI documents for a CAP service's events
Generates Open Resource Discovery documents from a CAP model
CAP Node.js runtime
Generates Open Resource Discovery documents from a CAP Java model
Exposes a CAP service as OData V2
CAP Node.js runtime
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Puts a number from an abap2UI5 app on a Fiori launchpad tile
There is nothing here for ABAP for Cloud: the requirements name Standard ABAP releases only, and a CDS/SADL based OData service for `ABAP for Cloud` compatibility stands under Limitations & Todo.
OData and Gateway shims serving SEGW-style services on Node.js
CAP Node.js server behind the OData Deep Dive tutorials
Generates OpenAPI documents from a CDS service
CodeJam on API management in SAP Integration Suite
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
Open-source Z* version of /UI2/CL_JSON for ABAP to JSON
Exposes CAP services as MCP servers for AI agents
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas applies that prohibition to CAP wrappers around those APIs. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement. In beta, with nine releases in the six weeks after the first, so pin it.
ABAP-native MCP endpoint that drives opted-in abap2UI5 apps
Stateful apps cannot be operated: a stateful session lives in one HTTP request and an MCP call is one request, so `app_start` refuses them. The repository carries no release yet and states the addon has not been run in production use, the 7.02 downport is lint-only with no 7.02 system having run it, and the ABAP Cloud HTTP service setup is written down but still to verify on your own system.
API proxies with security and traffic policies and Developer Hub
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.
CodeJam on LLM-backed integration flows and MCP via API Management
CAP travel-booking app built on xflights master data
WebSocket and Socket.IO adapter for CDS services
Server side of the flight reference scenario for SOAP in ABAP Cloud
Client side of the flight reference scenario for SOAP in ABAP Cloud