Documentation
Finding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.
Overview
capire, at cap.cloud.sap, is the CAP documentation: its core pages are built from the public capire/docscapire/docsThe sources of capire itself, in the repository it is built from: the documentation every core_coverage claim in this graph is checked against, so a claim can be dated against a commit.sap official, cap repository, open to issues and pull requests, with SAP-specific pages added on publication. Around it, @cap-js/mcp-server@cap-js/mcp-serverSAP's MCP server for CAP development, run as cds-mcp: search_model searches the project's compiled CDS model, search_docs searches the CAP documentation indexed as embeddings on the developer's own machine.sap official, cap searches a preprocessed copy of it from a coding agent, and @sap-ux/fiori-docs-embeddings@sap-ux/fiori-docs-embeddingsFiori documentation indexed as embeddings, which is what makes it searchable by something other than a person scrolling it.sap official, cap does the same for the Fiori documentation.
Not covered: capire is the documentation and it is SAP's; what the corpus holds beside it is machine-readable packaging of the same material rather than a second source. Nothing here documents your application — that is metadata publishing.
SAP-official packages and independent servers both package first-party prose for machines, and how they relate has not been assessed.
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 clones SAP's documentation repositories and serves them over MCP with hybrid keyword and embedding retrieval, reaching ABAP, UI5 and BTP material the SAP-official embeddings package does not carry. Clean-Core.ioClean-Core.ioA free hosted workspace that reads one piece of custom ABAP, redraws its business process as BPMN with a line anchor on every element, grades the SAP objects it uses Level A–D and ends in a keep, rebuild, move-to-standard or retire decision.independent, abap is the other kind: it writes a document of a custom program from the program itself.
The framework's own reference, served as tools rather than scrolled. @ui5/webcomponents-mcp-server@ui5/webcomponents-mcp-serverFour tools that answer an agent's questions about UI5 Web Components from the framework's own documentation — component API, integration guides, and the docs themselves.sap official, ui5 answers what properties, slots, events and methods a named component actually has — the part a model is most likely to invent — and returns the integration guide for the framework you are wiring it into.
@ui5/webcomponents-mcp-server Four tools that answer an agent's questions about UI5 Web Components from the framework's own documentation — component API, integration guides, and the docs themselves.
Not covered: At the documentation. Nothing here opens your project, so it cannot say whether the component it just described is the one your application already uses.
SAP's own answer is @ui5/webcomponents-mcp-server@ui5/webcomponents-mcp-serverFour tools that answer an agent's questions about UI5 Web Components from the framework's own documentation — component API, integration guides, and the docs themselves.sap official, ui5. Independent tools add the API reference inside the editor, as vscode-ui5-api-referencevscode-ui5-api-referenceVS Code extension that shows the SAPUI5 and OpenUI5 API reference in a side bar view, with inherited members, member filters and a favourites list, for one framework version at a time.independent, ui5 does, and the change log answered by release range, as ui5-lib-diffui5-lib-diffA hosted app that lists what changed between two SAPUI5 or OpenUI5 versions from the UI5 API's change records, and publishes the same data as static JSON files at fixed paths for tools and agents.independent, ui5 does. what_core_does is left empty: no page has been checked that states an intent here.
SAP publishes its platform documentation as public repositories, which makes indexing it something anybody can do. Independent servers do so over single corpora, such as BTP documentationsap-btp-docs-mcpAn MCP server for semantic search over the SAP BTP documentation repository, filtered by area such as development, administration, integration or security, with full document retrieval.independent, btp and AI Core documentationsap-ai-docs-mcpAn MCP server with semantic search, category filtering and whole-page retrieval over SAP AI Core's documentation, from the SAP-docs/sap-artificial-intelligence repository.independent, btp, with semantic search and category filtering, and over catalogues such as SAP's API Business Accelerator Hubsap-api-hub-mcpA read-only MCP server over the SAP Business Accelerator Hub catalogue: categories, search, metadata, resources, specs and packages, reached as the caller's own SAP user.independent, btp.
No core answer is documented.
Not covered: At the corpus or catalogue each server reads. What is answerable is exactly what that repository, catalogue or feed holds and nothing beside it.
The providers are independent and read SAP's published material: documentation repositories, the Business Accelerator Hub catalogue, SAP Notes and the roadmap. SAP publishes the documentation itself, in the open, which is what makes indexing it possible — publishing a corpus is not the same as answering this capability.
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.
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
Show 3 more
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