Everything in the atlas
Type
Domain
Origin
Signals: Last 3 months
More: 2
Group by: None
Compares a CAP project's CSV data with its database rows
XSUAA authentication stack for an MCP server on SAP BTP
It stops at the `AuthInfo` and the raw bearer token, and the README lists what stays with the consuming server: rate limiting, the scope and tool policy, the MCP transport, the SAP HTTP client's headers, and helmet-style hardening. The one piece of hardening it constrains rather than defers is the cross-origin opener policy, which it deliberately leaves unset because popup-based OAuth breaks under it. It is ESM-only on Node 22 or later and shares the host's Express and MCP SDK instances as peer dependencies, so a server on Express 4 cannot take it.
Interactive generator for CAP event handler files
Business-level metrics from CDS annotations via @cap-js/telemetry
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.
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
Live-updatable feature toggles for CAP, backed by Redis
CLI for operating tenants of multitenant CAP applications
Exposes a CAP service as OData V2
SDK for SAP Advanced Financial Closing scheduling providers on CDS
WebSocket and Socket.IO adapter for CDS services
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
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
Shared ESLint configuration for SAPUI5 and CAP projects
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Annotation-driven mail on CAP entity lifecycle events
Node below 22, or [@sap/cds](artifact:sap-cds) below 9: the package declares the first in engines and the second as a peer dependency. Any mail path other than Microsoft Graph, until a provider is written for it: graph is the only kind that sends, and basic, the kind configured by default, is the base class such a provider extends.
Vercel AI SDK provider for SAP AI Core
Interactive project installer for CAP Node.js
Browser login and session module for SAP MCP servers
The maintainer states it is unofficial, not endorsed by SAP, and that it automates authenticated SAP web endpoints and browser session cookies in ways SAP's terms of service or an organisation's own policies may restrict. Password login is confined to `accounts.sap.com` and the standard SAP Cloud Identity Services tenant domains: a custom IAS domain, or a login that conditional authentication delegates to a corporate identity provider, fails closed before the password is filled and has to be completed through an interactive login instead.
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
LangGraph Store keeping agent memory as CDS entities
Deep Agents filesystem over an SAP Document Management repository
Not a way to edit Office formats: the author states that access to a file does not automatically provide native editing of Word documents, spreadsheets or PDFs, and suggests starting with text-based content such as instructions, templates and reports. Not a control point either: a prompt telling the agent to ask for confirmation or to leave a template alone needs enforceable application controls where that is a business requirement, and the host application stays responsible for the authenticated request context and tenant isolation.
LangGraph checkpointer backed by CDS for CAP agents
MCP server inside a CAP application with model and query tools
Copy of @cap-js/notifications published under another scope
Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.
CAP plugin casting read values back to CDS model types
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
CAP plugin serving the Cardano blockchain as OData V4
MCP server exposing the ODATANO Cardano-to-OData bridge as tools
The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
CAP plugin indexing the Midnight blockchain, exposed as OData V4
MCP server exposing the NIGHTGATE Midnight attestation layer
SAP's capire/skills packaged for the pi coding agent
If your tool reads the open skill standard directly, install [capire/skills](artifact:capire-skills) and skip the wrapper.
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
CLI of CAP development tools for Cloud Foundry workflows
There is no repository and no README: what the eight commands do is only readable from the compiled dist that ships in the package. Three of them — npmrc, install, project — are written for "SimpleMDG" projects rather than for CAP generally, so the reusable part is bind-local, run-local and debug. Seven releases up to July 2026. Its binding step writes the resolved VCAP_SERVICES into default-env.json in the project, where [@sap/cds-dk](artifact:sap-cds-dk) keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.
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
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
ESLint rules for projects the Fiori tools generators produce
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
Library for sending usage telemetry data
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
CLI for the SAP BTP Application Frontend service
SAP's Node.js application router in front of business applications
CAP Node.js runtime
Compiler from CDS models to CSN, EDMX and database schemas
Command line client and development toolkit for CAP
Language server for CDS
Multitenancy, tenant provisioning and extensibility for CAP
WebAssembly sandbox for tenant-specific extension code in CAP
SAP Passport handling for Node.js components
CAP project generator behind SAP Business Application Studio's wizard
Entry point for generating a Fiori application from a template
SAP's Node.js driver for SAP HANA
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
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
Runner for Bruno collections against XSUAA-protected CF apps
Node.js inspector tunnel over cf ssh to Cloud Foundry apps
File search in apps deployed to SAP BTP Cloud Foundry over cf ssh
Step-by-step state recorder for one JavaScript function in Node.js
SQL runner against the SAP HANA Cloud database bound to a CF app
Shell debugger for remote Node.js over the Chrome DevTools Protocol
HTTP trace hook streaming a running CF Node.js app's traffic
Log fetcher and parser for one Cloud Foundry app
Read-only query tool for metrics in SAP Cloud Logging
Read-only query tool for OpenTelemetry spans in SAP Cloud Logging
Endpoint discovery for CAP services deployed to Cloud Foundry
Cloud Foundry topology cache for the other @saptools packages
Merged log tail of every started app in a Cloud Foundry space
OAuth2 token fetcher for a Cloud Foundry app's XSUAA binding
Workspace-wide CSN cache for querying CAP entities and columns
Static end-to-end tracer of one CAP operation across repositories
SQLTools connection from a Cloud Foundry app's HANA binding
MCP server answering plain-English questions against a CDS schema
Four agent skills for SAP AI Core in SAP's AI Skills Library
MCP server drawing BTP solution diagrams on a draw.io canvas
Any run nobody is watching: the drawing tools work only while the draw.io canvas at `http://localhost:3000/` is open and connected, so there is no diagram to produce on a build agent or a server. Nothing checks the result either, because the maintainer keeps a diagram linter on the [roadmap](https://github.com/etosin/arc-draw#-roadmap) rather than in the release. The maintainer marks the status early at v0.x, installs it from source, and records testing with Claude Code alone.
Hub on SAP BTP putting several arc-1 instances behind one login
Archived The declared repository is archived.
Functional boundary With one SAP system the README says to point the client at that arc-1 directly. Version 1 exchanges tokens within a single subaccount, so backends spread across subaccounts are out; it keeps its session map in memory, so more than one instance needs sticky sessions or a shared store. It routes deterministically and runs no model, which is a different thing from an assistant that reasons across systems. The `/all` endpoint drops the per-connection isolation, and the maintainer's answer to that is a PROD backend set read-only at the SAP end rather than a tool surface that hides the writes.
BTP Core Services as MCP tools with in-chat dashboards
It administers a real account through Core Services, so what it can change is what the caller can change. And the UI half depends on hosts that render mcp-ui or MCP Apps resources; elsewhere those five tools return markup nobody displays.
MCP server for SAP BTP and Cloud Foundry acting as the logged-in user
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
MCP server with read tools over the SAP Cloud ALM APIs
CAP review skill for coding agents with gates and prohibitions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary There is no licence, so there is no grant to use or redistribute it. Everything else is secondary to that. Note too that its 'verified' claim means the skill text was checked against itself by an evaluation suite — not that the advice was run against a CAP version.
UI5 web interface for an agent built in a CAP service
Not where the agent is reached over anything other than A2A: the README states the plugin does not speak anything other than A2A as @cap-js/agents serves it. Not where an upgrade has to be uneventful either — it pins @cap-js/agents to exactly 0.9.1, calls that package pre-1.0 and days old at the time of writing, and says this plugin inherits that instability and to expect breakage on upgrade.
CodeJam on LLM-backed integration flows and MCP via API Management
Sample apps for SAP AI Core's Generative AI Hub capabilities
FastAPI backend for SAP-RPT-1.5 predictions from SAP Analytics Cloud
Showcase for dev-approuter in front of two UI5 apps
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Java implementation of the capire/bookshop getting-started sample
Java implementation of the capire/bookstore composite app
Terraform samples for the SAP BTP Administrator's Guide account model
Guide and samples for moving Java apps from Neo to Cloud Foundry
Machine-readable catalogue of SAP BTP pay-as-you-go services
Code samples for the Getting Started with Terraform on SAP BTP course
Samples for the Terraform Provider for SAP BTP
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
Neither the package manifest nor the repository tree declares a licence.