
Application to connect any SAP system with the installed MCP client
Application to connect any SAP system with the installed MCP client
·
Connect an AI assistant to your SAP system, with a safety policy you control.
SAP MCP Connection Manager keeps your SAP connections in one place and makes them available to Claude Desktop and Codex (ChatGPT) through a local MCP server. The AI can then read and work with ABAP development objects through the same development interface (ADT) that Eclipse uses. Every request is checked against the safety policy you set for that connection before it reaches SAP.
Windows 10 and 11.
SAP-MCP-Desktop-Bridge-<version>-Windows-Setup.exe from Releases.You don't need to install Node.js or anything else. The installer includes its own Node.js runtime, the desktop shell and the MCP server. The only other things you need are:
To update, run a newer installer. Your connections, passwords and certificates are kept. If the manager or a Bridge MCP server is running, the installer closes it; restart Claude Desktop or Codex afterwards.
For unattended or managed installs, run the installer with /VERYSILENT /SUPPRESSMSGBOXES /NORESTART. It shows no window and doesn't open the app. The exit code reports the result: 0 means success, and 10 means the app is installed but Claude Desktop or Codex couldn't be connected (the reason is in %TEMP%\sap-mcp-bridge-install-error.log and in the manager). Add /MERGETASKS="!clients" to install without touching Claude Desktop or Codex.
Test through MCP and Full diagnostics start the connection exactly as your AI client will, and tell you where it fails.
Bridge never changes a client's settings file it can't read safely, and if one client fails it puts the others back as they were. The manager's Logs show which file, why, and what to do. The usual causes:
config.toml at the path shown in Logs. Correct it, or put back one of the .backup files Bridge keeps next to it, then choose Configure MCP clients.SAP-Bridge already exists that Bridge didn't create. Rename or remove it, then retry.With more than one connection, the one marked Default system is used whenever a request doesn't name a system. Only one connection can be the default.
Each connection answers two questions.
What may it change?
Z*, Y*, $* and /namespace/ packages). Choosing this also denies the debugger, abapGit and running ABAP snippets or classes.What data may it read?
Lists of packages, transports, tables and tools narrow this further. Entries go one per line and accept the wildcards * and ?, and a denial always wins over an allowance. The form shows a Low, Medium or High rating worked out from the whole policy. It also names anything the chosen level does not cover, with the list entry that closes it.
The policy is enforced by the MCP server itself, before a request reaches SAP, so telling the AI to ignore it has no effect. It is a safeguard, not a replacement for SAP authorisations: everything the AI does runs as your SAP user.
%LOCALAPPDATA%\SAP MCP Desktop Bridge. Passwords are encrypted with Windows DPAPI, so only your Windows account can read them.The full privacy policy sets out what is stored, what is sent where, and how to remove it.
Open Settings → Apps → Installed apps, find SAP MCP Desktop Bridge and choose Uninstall.
This removes the app and its Start-menu shortcut. Your connections and saved passwords are kept, in case you reinstall. Delete %LOCALAPPDATA%\SAP MCP Desktop Bridge to remove them as well. Also remove the SAP-Bridge entry from Claude Desktop's and Codex's MCP settings.
The source is in src (manager, desktop shell and MCP host), packaging (installer and build scripts) and test. packaging/vendor-patch holds our patched copy of the MCP server's policy engine. It's kept as the file it replaces, which is why it sits under a node_modules path. No dependencies are committed.
Everything the installer contains comes from this repository or from a public source, pinned by version and hash. It needs Windows, Node.js 24 and Python 3:
python packaging/fetch-base.py downloads the Node.js runtime, Electron and two build tools, rcedit and Inno Setup, and checks them against the SHA-256 hashes in packaging/pins.json. It then installs the MCP server and koffi, which the app uses to call Windows' own password encryption, from npm with npm ci, exactly as locked in packaging/vendor/package-lock.json.npm test runs the test suite, including the end-to-end policy test against the real MCP server.packaging\windows\build.ps1 builds the installer into dist\ with Inno Setup, from packaging/windows/installer.iss. The same inputs always give the same app contents: python packaging/payload-digest.py <payload.zip> prints a fingerprint of them that doesn't depend on which compressor packed them, and every GitHub build publishes its fingerprint for comparison.python packaging/windows/verify-release.py dist checks the build against this source and writes its checksums.The Windows build workflow runs these same steps on GitHub Actions for every change, and runs the installer tests too.
Releases aren't code-signed yet, so Windows shows a SmartScreen notice the first time you run the installer: choose More info → Run anyway. Signing through the SignPath Foundation is planned; see the Code signing policy below.
Microsoft Defender and some other antivirus products flagged the 1.0.0 and 1.0.1 installers with generic machine-learning detections such as Trojan:Win32/Sabsik.EN.B!ml. These were false positives. Those installers unpacked themselves and ran hidden PowerShell, and the app used hidden PowerShell to decrypt saved passwords, which is the pattern such heuristics look for. From 1.0.2 the installer is a standard Inno Setup installer, and the app calls Windows' password encryption directly and contains no scripts. If your antivirus still flags a release, please open an issue and report the file to the vendor as a false positive (for Defender, use Microsoft's file submission). Don't turn off your antivirus to install it.
Until then you can check what you downloaded. Each release lists the SHA-256 of its files in SHA256SUMS-<version>.txt. Every release is built from this repository by the Windows build on GitHub Actions, which publishes a fingerprint of the app's contents that you can reproduce from this source (see Building from source).
Free code signing provided by SignPath.io, certificate by SignPath Foundation. Our application is pending, so current releases are not signed yet.
It's free and open source. If it helps you, a ⭐ on GitHub helps other SAP developers find it, and bug reports and ideas are welcome as issues.
MIT, see LICENSE. Bundled components keep their own licenses, listed in THIRD-PARTY-NOTICES.txt.
This repo does not document an install step we could read. Check the README on GitHub.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/sap-mcp-connection-manager to learn what the "SAP MCP Connection Manager" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
This server doesn't publish a machine-readable tool manifest, and it doesn't expose a public endpoint we could ask. Connect the server locally to see what it exposes.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/sap-mcp-connection-manager)Nothing comparable is listed yet.
v1.0.4SAP MCP Connection Manager 1.0.4Release notesv1.0.3SAP MCP Connection Manager 1.0.3Release notesv1.0.2SAP MCP Connection Manager 1.0.2Release notesv1.0.1SAP MCP Connection Manager 1.0.1Release notesv1.0.0SAP MCP Connection Manager 1.0.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "sap-mcp-connection-manager" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.