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.
Overview
For custom code, ADT exports the ABAP Doc comments of classes and interfaces, chosen singly or by package, as HTML files, for example as a record for audits.
Not covered: For SAP's own documentation, at the corpus indexed: an index cannot tell you which of two statements your release supports. For custom code, at what developers wrote as ABAP Doc comments on classes and interfaces; an element with no comment gets at most its short text.
Two halves on this door. SAP publishes its ABAP documentation in the open, and publishing a corpus is not answering this capability. For custom code the core export is the ABAP Doc one, a function of ADT, the platform; community tools add to it by reading ABAP Doc, such as abapdocs-code-scannerabapdocs-code-scannerReads the abapDoc comments of a class or interface's public methods and type definitions and returns their text at runtime.independent, abap, or generate a document of a package, such as abap-docabap-docA Node.js command that reads an ABAP package and its sub-packages over ADT and writes one PDF documenting every object in it, with an LLM writing the prose.independent, abap. How they relate to the export has not been assessed.
Artifacts
Content
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