Everything in the atlas
Type
Domain
Origin: SAP official
Signals
More
Group by: Kind
CAP integration with SAP Integration Suite advanced event mesh
CDS plugin for building agents inside a CAP service
Not as a gateway or proxy for SAP Application APIs: capire's guide states that CAP-level agents are intended only for exposing custom CAP application services and are not an SAP-endorsed architecture or pathway for agentic access to those APIs, and sends the reader to the SAP Architecture Center for the endorsed routes. Not as the screen a user of the application talks to, either — the chat preview in the generic index.html page is marked experimental and for local development.
Value-help recommendations and SAP AI Core as a CAP service
Exports AsyncAPI documents for a CAP service's events
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP integration with the SAP Audit Log service
Generates Helm charts for the CAP Operator on Kubernetes
Monorepo of CAP's SQL database services
Test support for CAP Node.js: server start, HTTP client, assertions
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
Change history for annotated CAP entities
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
CAP integration with SAP Data Privacy Integration
Base service shared by CAP's SQLite, PostgreSQL and HANA services
Consumes events from SAP Cloud Application Event Hub in CAP
GraphQL protocol adapter generated from the CDS model
SAP HANA database service for CAP
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 server for CAP development: model and docs search
The tools are documented as meant for AI models and not a stable API, so anything built to parse `cds-mcp` output rather than to feed a model can break between releases. Its corpus is the CAP documentation, so Fiori elements, BTP service or ABAP questions are not in what `search_docs` indexes.
Triggers n8n workflows from a CAP application
Business notifications from CAP to SAP Build WorkZone
Generates OpenAPI documents from a CDS service
Generates Open Resource Discovery documents from a CAP model
PostgreSQL database service for CAP
Prints documents held in CAP entities through SAP Print service
Starts and manages SAP Build Process Automation processes from CAP
CAP attachments stored in an SAP Document Management repository
If document versions are required, [@cap-js/sdm](artifact:cap-js-sdm) excludes versioned repositories in its [documented restrictions](https://raw.githubusercontent.com/cap-js/sdm/ad13b61f21816ebead2d08264a74521cfb75846c/README.md).
SQLite database service for CAP, in memory during development
OpenTelemetry instrumentation for CAP services
Framework core: module loader, MVC runtime, binding, routing, theming
VS Code Multi-Target Application tools
AI Core control plane API surface of SAP's AI SDK
Shared internals of SAP's AI SDK
Client for foundation models via SAP AI Core and Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
Colour, font and metric definitions of the SAP themes
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Command line for changing features of an existing Fiori project
ESLint rules for projects the Fiori tools generators produce
Writer of flexible programming model elements into Fiori elements apps
Fiori Elements mock server plugin taking a CDS file as metadata
Programmatic API for reading and writing project annotations
Fiori documentation indexed as embeddings
Shared functions and types of the Fiori generators
MCP server for creating and editing Fiori applications
Reader and writer for i18n bundles of UI5 or CAP projects
Writer that adds an OData service to an existing UI5 project
OASIS and SAP OData vocabularies with a VocabularyService
Library for sending usage telemetry data
Writer of the base structure of a UI5 project from Node code
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
CLI for the SAP BTP Application Frontend service
SAP's Node.js application router in front of business applications
MTA generation and Cloud Foundry deploy for VS Code workspaces
A library a VS Code extension calls, not something installed and run on its own; there is no documented standalone CLI. No public repository either, so what it does is read from its own README rather than checked against source.
CAP Node.js runtime
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.
ISO content for CAP's countries, languages, currencies and timezones
Compiler from CDS models to CSN, EDMX and database schemas
Command line client and development toolkit for CAP
Fiori draft handling and UI-facing behaviour for CAP services
Database adapter for SAP HANA in CAP
Language server for CDS
Multitenancy, tenant provisioning and extensibility for CAP
WebAssembly sandbox for tenant-specific extension code in CAP
Calls to ABAP function modules over RFC from a CAP service
SAP Passport handling for Node.js components
SAP's ESLint plugin for CDS
CAP project generator behind SAP Business Application Studio's wizard
CDS project generator, deprecated in favour of @sap/cds-dk
Entry point for generating a Fiori application from a template
SAP's Node.js driver for SAP HANA
Node.js deployer for SAP HANA Deployment Infrastructure containers
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
MCP server with five tools for Mobile Development Kit work
It expects a real landscape, not just a project: a `.service.metadata` file naming the Mobile Services app, endpoint and destination, the Cloud Foundry CLI, and access to a BTP Cloud Foundry environment. From 0.4.0 macOS support is ARM64 only — Intel Macs are not supported — alongside Linux and Windows on x64 and ARM64.
CLI to build, deploy, migrate and validate MDK projects
Specific to MDK metadata projects — nothing here builds or deploys a CAP service or a plain Fiori app. Closed-source, under SAP's own developer licence rather than a public repository.
Wrapper around the CDS compiler for annotation handling
OData annotation features for the @sap/vscode-cds extension
CDS language support for VS Code and Business Application Studio
Token validation and security context for XSUAA and IAS
UI5 Tooling command line for project setup, dev server and build
Static analysis tool for UI5 projects
Internal logger of the UI5 CLI
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
UI5 CLI middleware for Istanbul code coverage
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
The declared repository is archived.
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
MCP server answering questions on UI5 Web Components
It answers from documentation and never opens your project, so it cannot tell you whether the component you are asking about is the one your application already uses. Node.js v20.17 or v22.9 and above; on Windows the command needs a `cmd /c` prefix.
SAP reuse library for calling large language models from ABAP
Modelling layer of ABAP Cloud above database tables
Nothing to choose here and nothing to install: it is what an ABAP Cloud system gives you. It shares a name and a lineage with CAP's CDS but is a different language in a different runtime, and a model does not move between them.
SAP's Eclipse plugins for ABAP development over ADT
It is an Eclipse install. A development object that is not native-integrated in Eclipse opens in the SAP GUI that is installed locally with the client.
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
Open-source Z* version of /UI2/CL_JSON for ABAP to JSON
SAP's specification for serialising ABAP objects to files
Local HTTP MCP server started from ABAP Development Tools for VS Code
There is nothing to install and nothing to deploy, and equally nothing to run headless: in VS Code it exists only while ADT for VS Code is running with a logged-on ABAP project, so it is a developer's local surface rather than anything a pipeline or a hosted agent can reach. No public repository, so what it exposes is what the documentation says it exposes.
HTTP endpoint under /sap/bc/adt exposing ABAP development objects
A client that cannot reach the adt ICF service over HTTP has nothing to call.
Injects the Dynatrace agent into Java applications on SAP BTP
BTP service for building and running Agentry mobile apps
Four agent skills for SAP AI Core in SAP's AI Skills Library
Business data graph queried with OData V4 or GraphQL
API proxies with security and traffic policies and Developer Hub
Scales Cloud Foundry app instances by policy rules and schedules
Tracks vulnerabilities in open-source components of BTP apps
Yeoman generator for Cloud Connector mappings and BTP destinations
Containerised script setting up an SAP BTP account from JSON config
The declared repository is archived.
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
Prebuilt SAP S/4HANA integration package for CAP projects
Agent skills for CAP development, each a SKILL.md with references
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
SAP CDS language support for IntelliJ IDEA
TextMate grammar for the CDS language
Not an editor integration. If you want completion, navigation and diagnostics, that is the CDS language server, not this.
GitHub Action setting up the Cloud Foundry CLI
Open, versioned style guide for ABAP
SAP's on-premises agent linking SAP BTP to customer-network systems
Identity Authentication and Identity Provisioning as one tenant
Builds and runs integration flows between cloud and on premise
Guided workflow for configuring SAP cloud solution integration
SAP's list of released APIs for SAP Cloud ERP with successors
It is a catalogue of SAP's objects and not a reading of your code: it states that an object is not released, never that you used it, and the finding is the ATC check's. For SAP Cloud ERP Private the files exist for feature pack stack releases only, with no update per support package, so a system between two stacks is checked against its stack's file.
ATC and Code Inspector checks for Clean ABAP
This is the legacy edition, for on-premise systems from SAP_BASIS 7.40. On ABAP Cloud, [the Cloud Edition](artifact:sap-code-pal-for-abap-cloud) is the one that runs.
Clean ABAP check set for ABAP Cloud
A2A adapter turning a CAP Java service into an LLM-backed agent
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
CAP Java plugin for SAP Integration Suite, advanced event mesh
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.
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
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Connects a running CAP Java app to CAP console for monitoring
Browser dashboard for a running CAP Java service during development
Connects CAP Java messaging to SAP Event Mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Declarative status-transition flows on bound actions in CAP Java
SAP HANA Cloud datasource for CAP Java applications
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
JDBC runtime for H2 and SQLite in CAP Java