Offline SAP documentation MCP server with unified local + online search
Most knowledge and memory work still happens through a UI a human drives. MCP Sap Docs MCP server moves it into the conversation instead. Offline SAP documentation MCP server with unified local + online search.
An MCP server that gives AI assistants (Claude, Cursor, ChatGPT, etc.) access to SAP documentation through a unified search and fetch interface. It combines a local full-text + semantic index over git-cloned SAP docs with optional live queries to SAP Help, SAP Community, and Software Heroes — all exposed as MCP tools.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 6 tools. What each one is for:
search — Unified hybrid search (BM25 + semantic) across offline docs and optional online sources. Supports query, k, includeOnline, includeSamplesfetch — Retrieve full document content by ID returned from searchabap_feature_matrix — Check ABAP feature availability across SAP releases (7.40–LATEST) using the [Software Heroes featuresap_community_search — Dedicated SAP Community search via the Khoros LiQL API — returns full content of top posts. Use when search results are insufficient for specificsap_search_objects — Search SAP released objects (classes, interfaces, tables, CDS views, …) by name/component/type from the officialsap_get_object_details — Full release state details for a specific SAP object including clean core level (A/B/C/D), successor objects, and optional compliance verdictConfiguration is passed through the environment: ABAP_REPO_SYNC_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Sap Docs's toolset — search, fetch, abap_feature_matrix and 3 more — is a fair guide to whether it matches your workflow. It is maintained by marianfoo; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search | Unified hybrid search (BM25 + semantic) across offline docs and optional online sources. Supports query, k, includeOnline, includeSamples, abapFlavor, sources parameters. |
| fetch | Retrieve full document content by ID returned from search. |
| abap_feature_matrix | Check ABAP feature availability across SAP releases (7.40–LATEST) using the [Software Heroes feature matrix](https://software-heroes.com/en/abap-feature-matrix). |
| sap_community_search | Dedicated SAP Community search via the Khoros LiQL API — returns full content of top posts. Use when search results are insufficient for specific errors or workarounds. |
| sap_search_objects | Search SAP released objects (classes, interfaces, tables, CDS views, …) by name/component/type from the official [SAP/abap-atc-cr-cv-s4hc](https://github.com/SAP/abap-atc-cr-cv-s4hc) release state repo. Useful for clean |
| sap_get_object_details | Full release state details for a specific SAP object including clean core level (A/B/C/D), successor objects, and optional compliance verdict. |
| Variable | Description | Required |
|---|---|---|
| ABAP_REPO_SYNC_TOKEN | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.