Documentation
The ABAP keyword documentation, the cheat sheets and the RAP tutorials are public repositories, and mcp-sap-docsmcp-sap-docsAn MCP server over seventeen cloned SAP documentation repositories — ABAP keyword docs, capire, OpenUI5, Cloud SDK, BTP — searched with BM25 and prebuilt embeddings fused by reciprocal rank fusion.independent, cap indexes all three alongside a cloud and standard flavour switch — so an agent asked about a statement answers from the reference rather than from memory of an older release. Custom code is the other half: a package nobody documented, handed to a team that did not write it, where the document has to be produced from the objects in the system.
Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP
Overview
SAP publishes ABAP Cloud as a restricted, cloud-safe ABAP language version built on released APIs, and lists which repository objects carry that release: found in ADT's Project Explorer under Released Objects, or on the SAP Business Accelerator Hub and the Cloudification Repository Viewer.
Not covered: It documents which objects and statements the release contract covers, not whether a given piece of code still compiles against it — that check is ADT's syntax check and the ABAP_CLOUD_READINESS ATC variant, run against the code rather than read from a page.
The ABAP Cloud contract is documented by SAP in the developer guide and in ADT. abap-cheat-sheetsSAP-samples/abap-cheat-sheetsA collection of ABAP syntax cheat sheets, from internal tables to RAP's Entity Manipulation Language, each backed by an executable demo class you import into an ABAP system with abapGit.sap official, abap demonstrates this capability rather than providing it, and mcp-sap-docsmcp-sap-docsAn MCP server over seventeen cloned SAP documentation repositories — ABAP keyword docs, capire, OpenUI5, Cloud SDK, BTP — searched with BM25 and prebuilt embeddings fused by reciprocal rank fusion.independent, cap answers it from the CAP door, abap only among the ecosystems it serves.
No community artifact is documented here.
Artifacts
Seen working
The Markdown is a snapshot of whatever help.sap.com served when the pipeline last ran, and the Standard library is scraped from the `latest` index, so which release a page describes follows from the scrape date rather than from anything the corpus states. `package.json` states ISC and the repository carries no LICENSE file, so what the copied SAP documentation may be used for is not stated in it.
Details
Coverage
For your agent
- Ref
capability:documentation- JSON
- /capabilities/documentation.json
- MCP
- Connecting an agent