Everything in the atlas
Type
Domain: Protocols & APIs
Origin: SAP official
Signals
More: 2
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
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
CAP Node.js runtime
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
CAP Node.js server behind the OData Deep Dive tutorials
Generates OpenAPI documents from a CDS service
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
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.
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.
CAP travel-booking app built on xflights master data
