← Back to directory
S

SAP Docs MCP Server

Community
A unified hybrid-search MCP server for SAP documentation, with no API key required.
Category
Dev Tools #50 of 438
Stars
★ 249 Very popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Hosted (no local runtime) · Node.js · Docker
Credentials
No credential needed
License
Apache-2.0
Last commit
Tools
9
65FMRS · C

This is a community-maintained SAP documentation retrieval MCP server that fuses BM25 keyword search with semantic embedding search across UI5, CAP, BTP, ABAP, and other SAP docs, plus a public hosted read-only endpoint. It is practical for SAP developers and needs no credentials, but it is not an official SAP product and online queries send keywords to third-party sources. This profile covers only the sap-docs variant, not the abap variant's tools in the same repository.

Strongest · Documentation 15/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
12/20
Maintenance
14/20
Documentation
15/20
Setup experience
14/20
Why each score
Reliability 10/20
The README documents a coherent design: unified search/fetch tools, hybrid BM25 + semantic retrieval with RRF fusion, offline/online modes, health endpoints (/health, /status), and a list of validation commands (test:integration, test:discovery-center, test:sap-objects, etc.), suggesting key paths are intentional. However, this is a purely static review with nothing executed; although CI/sync workflows and test scripts exist in name, coverage of MCP init, tool-list handshake, and error paths cannot be verified from source. The repo also hosts two variants sharing one codebase while server.json maps to only the sap-docs variant, adding behavioral ambiguity. Consistent with the static cap and missing execution evidence, scored 10.
Security and permissions 12/20
The server is a public read-only documentation search endpoint requiring no API key; tools (search/fetch/abap_feature_matrix, etc.) have no destructive side effects, and the Docker docs offer `--network none` plus includeOnline=false for isolated operation, showing reasonable boundary awareness. But online sources (SAP Help/Community/Software Heroes) are enabled by default and the README does not clearly disclose the data flow or privacy implications of sending user queries to third parties; the sync workflow relies on the sensitive ABAP_REPO_SYNC_TOKEN for cross-repo pushes without stating scope or rotation. No red-line issues found (no malware, credential theft, or irreversible defaults), so not 0-4, but deducted to 12 for incomplete data-flow and credential-scope disclosure.
Maintenance 14/20
Apache-2.0 license is clear, version 0.3.15 is published via Release Please, indicating a versioning/release process; the README describes a one-way sync, deployment model, and PM2 runtime with reasonably clear ownership, and open issues stand at 0. However, static materials give no recent commit timeline, dependency-update policy, or security-response channel (CVE/disclosure process), so sustained maintenance cannot be substantiated. Scored 14, deducted for undisclosed security-response and dependency-update mechanisms.
Documentation 15/20
Documentation is well layered: Install, public hosted endpoint, variant comparison tables, offline/online source tables, tool inventory with parameters (search supports query/k/includeOnline/includeSamples/abapFlavor/sources), Docker, BTP CF, PM2, validation commands, and links to docs/ARCHITECTURE.md and HYBRID-SEARCH.md, with disclosed embedding model (~90MB) and port differences. Deductions: full JSON schemas for tool parameters, error-return formats, and rate/cost notes are missing; and the README mixes two variants' tools, risking readers attributing abap_lint etc. to the sap-docs server mapped by server.json. Scored 15.
Setup experience 14/20
Multiple install paths are offered: a one-click Werkbank badge, streamable HTTP client JSON config, local npm ci/setup/build/start flow, Docker build/run examples, and BTP CF deployment guidance, with default ports and health-check commands included, making the main path clear and short. Deductions: local runs require a setup phase pulling git submodules and building the FTS index plus a ~90MB embedding model, a heavier first-time prep with implicit network/disk needs; and the repo spans two variants that users must disambiguate via MCP_VARIANT. Scored 14, within the static (unexecuted) cap of 15.

Static review · not runListed 2026-09-18

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • SAP developers working with SAPUI5, CAP, BTP, or ABAP
  • Teams that want SAP official and community docs searchable directly in their editor or AI assistant
  • Offline or restricted-network scenarios that need a local index
  • Developers tracking clean core compliance and SAP released object state

Not for

  • General documentation search outside the SAP technology stack
  • Scenarios requiring writes, modifications, or deployments to SAP systems (the server is read-only)
  • Enterprise support scenarios needing official SAP support or licensed credentials
  • Users requiring vendor-official maintenance guarantees

Required permissions

  • Local runs need network access to clone documentation submodules and for optional online queries (SAP Help, SAP Community, Software Heroes)
  • Local builds require write access to the project directory (index database docs.sqlite, embedding model cache in dist/models, about 90 MB)
  • Docker offline runs can fully disable networking via --network none
  • The hosted endpoint requires no API key or login and is public read-only

Risks and side effects

  • Online queries send search keywords to external sources (SAP Help, SAP Community, Software Heroes)
  • The local index and embedding model consume disk space (model is about 90 MB, build caches are larger)
  • Setup clones multiple SAP documentation repositories, which takes time and depends on network stability
  • The server is community-maintained and not an official SAP product, so docs and behavior may change with upstream

Setup

Before you start

Runtime:Hosted (no local runtime) · Node.js · Docker

Other optional settings (3)
MCP_VARIANT optional Selects the server variant (sap-docs or abap); falls back to sap-docs when unset.
MCP_PORT optional Sets the HTTP listen port; the Docker examples use 3122.
MCP_HOST optional Sets the bind address; set to 0.0.0.0 in Docker for host access.

Option 1 (hosted endpoint, no install): add the config {"mcpServers":{"sap-docs":{"type":"http","url":"https://mcp-sap-docs.marianzeis.de/mcp"}}} to any MCP client that supports streamable HTTP. Option 2 (local stdio): clone the repository, run npm ci, npm run setup, and npm run build, then run npm start for stdio mode; run npm run start:streamable for streamable HTTP (sap-docs default port 3122). The npm package mcp-sap-docs is also available over stdio transport.

.cursor/mcp.json
{"mcpServers":{"sap-docs":{"type":"http","url":"https://mcp-sap-docs.marianzeis.de/mcp"}}}

Shown for Cursor. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "sap-docs": {
      "type": "http",
      "url": "https://mcp-sap-docs.marianzeis.de/mcp"
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add --transport http sap-docs https://mcp-sap-docs.marianzeis.de/mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

Add the hosted endpoint https://mcp-sap-docs.marianzeis.de/mcp to your MCP client; the tool list should include search and fetch. For a local install, verify with curl -sS http://127.0.0.1:3122/health.

Troubleshooting

  1. If online sources are unavailable, set includeOnline=false in the search request to use only the offline index
  2. If health checks fail, verify ports: the sap-docs variant uses HTTP 3001 and streamable 3122
  3. Confirm the variant config: MCP_VARIANT environment variable or the .mcp-variant file at the repo root; the fallback is sap-docs
  4. If local results are empty, run npm run setup and npm run build first to build the index and embeddings
  5. With --network none, startup logs may show online prefetch warnings; this does not prevent offline search usage

Things to try

Once connected, you can ask your AI assistant things like:

  • Search SAP docs for how RAP draft handling works.
  • Check the ABAP feature matrix for features available since release 7.50.
  • Show all FEATURE and DEPRECATED changes between SAPUI5 versions 1.120 and 1.124.
  • Search SAP Community for workarounds for this OData V4 error.

Tools 9

search read-only
Unified hybrid search (BM25 + semantic) across offline docs and optional online sources, supporting query, k, includeOnline, includeSamples, abapFlavor, and sources parameters.
fetch read-only
Retrieve full document content by ID returned from search.
abap_feature_matrix read-only
Check ABAP feature availability across SAP releases (7.40–LATEST) using the Software Heroes feature matrix.
sap_community_search read-only
Dedicated SAP Community search via the Khoros LiQL API, returning full content of top posts.
sap_search_objects read-only
Search SAP released objects (classes, interfaces, tables, CDS views, etc.) by name, component, or type from the official SAP/abap-atc-cr-cv-s4hc release state repo.
sap_get_object_details read-only
Full release state details for a specific SAP object, including clean core level (A/B/C/D), successor objects, and an optional compliance verdict.
sap_discovery_center_search read-only
Search the SAP Discovery Center service catalog for BTP services by keyword, category, or license model.
sap_discovery_center_service read-only
Get comprehensive BTP service details: pricing plans, product roadmap, documentation links, and key features. Accepts a service UUID or name.
Show 1 more tools
ui5_version_diff read-only
List all matching FEATURE / FIX / DEPRECATED changes and SAPUI5 What's New entries for a version or range from a local all-changes bundle.

Use cases

Looking up SAP docs for SAPUI5, OpenUI5, CAP, Cloud SDK, BTP, ABAP, and Terraform Provider for BTP
Letting AI assistants find SAP documentation content with natural-language queries (for example, permission-check docs)
Retrieving SAP Community blogs, Q&A, and troubleshooting posts
Checking ABAP feature availability in a specific SAP release
Discovering SAP released objects and their clean core release state
Querying BTP services and pricing plans in the SAP Discovery Center
Reviewing SAPUI5 feature, fix, and deprecation changes for version upgrades

Supported clients

Claude
Cursor
ChatGPT

Listed from the project's documentation, not tested by this site.

Overview

SAP Docs MCP Server gives AI assistants (Claude, Cursor, ChatGPT, etc.) access to SAP documentation through a unified search and fetch interface. It combines a local offline full-text and semantic index over git-cloned SAP docs with optional live queries to SAP Help, SAP Community, and Software Heroes, all exposed as MCP tools. Search uses hybrid BM25 keyword matching plus semantic embeddings (Xenova/all-MiniLM-L6-v2) fused via Reciprocal Rank Fusion. The server is public and read-only, requires no API key or login, and offers a hosted streamable HTTP endpoint. The repository also contains a second abap-variant MCP server; this profile covers only the sap-docs variant.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 64.1k · Tools 2 Compare with this →

Source revision 6e672417fde2 Data synced 2026-11-02 Read the FMRS scoring method