On-premise ABAP and ABAP Cloud have different permitted syntax, and a general search engine happily hands you the wrong one. This indexes them as separate sources and lets the query say which flavour it wants, then abap_feature_matrix answers the follow-up question — whether the statement exists in the release you are actually on. sap_get_object_details closes the loop for clean core work by naming the successor when an object is not the one you should be using.
A search server over a local index of SAP documentation, with live queries to SAP Help Portal, SAP Community and Software Heroes layered on top. It ships as two variants from one codebase: sap-docs for the broad SAP surface, and abap for ABAP-focused work. A public hosted endpoint exists for both, so trying it costs nothing.
- search — hybrid BM25 and semantic search across the offline index and, optionally, the online sources; you can restrict it by source, ABAP flavour, or whether samples are included
- fetch — the full document behind a search result, by id
- sap_community_search — a dedicated Community search through the Khoros LiQL API, returning whole posts, for the errors and workarounds that only exist in forum threads
- sap_search_objects and sap_get_object_details — SAP released objects by name, component or type, with clean core level and successor objects, from SAP's own release-state repository
- abap_feature_matrix — whether an ABAP feature exists in a given release, from 7.40 upward
- In the sap-docs variant: sap_discovery_center_search and sap_discovery_center_service for BTP service catalogue entries, pricing plans and roadmaps, plus ui5_version_diff for the FEATURE, FIX and DEPRECATED changes between UI5 versions
- In the abap variant: abap_lint, static analysis over ABAP source with line numbers, severity and rule keys
- The offline index covers ABAP keyword documentation for both on-premise and ABAP Cloud, cheat sheets, RAP examples, Clean ABAP style guides, the DSAG Leitfaden, BTP, SAP AI, UI5, CAP, Cloud SDK, the BTP Terraform provider, Architecture Center and wdi5
Nothing, if you point your client at the hosted endpoint — no account and no key. Running it yourself means Node.js and a build: MCP_VARIANT picks sap-docs or abap, then npm run setup fetches the documentation submodules and builds the index before npm run build. A Docker image build takes the variant as a build argument. The online sources are enabled by default and query SAP's public sites directly.
One command — npx -y mcp-remote https://mcp-sap-docs.marianzeis.de/mcp