BrowseAll ecosystems
Everything in the atlas
3 of 2341
Domain
Signals
Content: 5
More: 3
Group by: Capability
Offers A referenceOffers Runnable codeOffers A recipeSource capireSource SAP websiteSource SAP CommunityPublished UndatedPublished 2018Clear all
EntryBySignalsLast activity
Model Context Protocol Adapter — CAP guideModel Context Protocol Adapter — CAP guideDocuments @cap-js/mcp and com.sap.cds:cds-adapter-mcp, service annotations, generated describe/query/call tools and local client setup. The guide records Java doc-comment configuration, unbound-action-based data changes, incomplete XSUAA PKCE support and the adapter’s governance boundaries.
Set up VS Code on Chrome OS for local Application Programming Model developmentSet up VS Code on Chrome OS for local Application Programming Model developmentA CAP development environment on a Chromebook, written from preference rather than constraint — the author sets out why Chrome OS is his primary machine before showing the setup. Carries its own updates section noting what has changed since, which for a 2018 post about an operating system is most of it. The interest now is that local CAP development was portable this early.published 2018-10-16
Set up VS Code on Chrome OS for local Application Programming Model development
Local development has changed twice since this was published, most recently in @sap/cds-dk 7.9.1, 2024-05-02. Affects Runnable code.
Under no capability
API Policy - FAQAPI Policy - FAQSAP’s June 2026 FAQ, version 1.3, explains the scope and use conditions of the SAP API Policy, including published and non-published APIs, ADT developer access, AI-driven usage and third-party MCP servers. It also addresses data extraction and the responsibilities of customers and partners. The FAQ is informational: it does not modify contracts, and applicable agreements and product documentation prevail if they conflict with it.
