SAP MCP Connection Manager 1.0.2

Built in the open, from public sources.

What's new

Microsoft Defender and other antivirus products flagged 1.0.0 and 1.0.1 with generic machine-learning detections such as Trojan:Win32/Sabsik.EN.B!ml. Those were false positives, caused by how the installer and the app were built. This release removes every pattern behind them:

• A standard installer. The installer is now built with Inno Setup instead of a custom program that unpacked itself and ran hidden PowerShell. It shows a normal setup window and lets you choose whether to connect Claude Desktop and Codex. The app now appears in Settings → Apps, so you can uninstall it from there like any other app.
• No hidden PowerShell. The app used to start a hidden PowerShell script every time it saved or read a password. It now calls Windows' own password encryption (DPAPI) directly. Passwords you've already saved keep working: the encryption and file format are unchanged.
• No scripts in the app. The VBScript launcher, the batch file and the PowerShell uninstall and rollback scripts are gone.
• The app's own name and publisher. The app's executable now describes itself as SAP MCP Connection Manager instead of Electron.
• Imports only when you ask. The manager no longer looks for older vaults and abap-adt-mcp settings every time it starts. Use Import existing connections or Choose original vault to import them.

Also:

• Updating while the manager or Claude Desktop or Codex is running now works. The installer closes the Bridge programs that are running (only its own) and opens nothing. Restart Claude Desktop or Codex afterwards.
• If Claude Desktop or Codex can't be connected during setup, the app is still installed and their settings are left exactly as they were. The installer and the manager now say why in plain language and how to fix it, for example a mistake in the client's settings file or a file held open by another program. If neither client is installed yet, the installer tells you how to connect one later.
• A settings file that contains a mistake is now reported as such, with the line where the problem is, instead of a raw parser error.
• The Setup Guide and README have a new section, If Claude Desktop or Codex isn't connected, covering each cause, including a Claude Desktop that is still running in the system tray.
• Unattended installs now use /VERYSILENT /SUPPRESSMSGBOXES /NORESTART instead of /S. Exit code 0 means success; 10 means the app is installed but the clients couldn't be connected (the reason is in %TEMP%\sap-mcp-bridge-install-error.log). Add /MERGETASKS="!clients" to skip connecting them.
• Copies of earlier versions that updates used to keep next to the app are removed.

Your connections, passwords and certificates are kept when you update.

Download

Download SAP-MCP-Desktop-Bridge-1.0.2-Windows-Setup.exe below and run it. You need Windows 10 or 11 and Claude Desktop or Codex. Nothing else to install: the installer includes its own Node.js runtime.

The installer isn't code-signed yet, so Windows shows a SmartScreen notice the first time: choose More info → Run anyway. You can check the download against SHA256SUMS-1.0.2.txt. If your antivirus flags it, please open an issue rather than turning the antivirus off.

If the app helps you, a ⭐ on the repository helps other SAP developers find it.

SAP MCP Connection Manager 1.0.1

Built in the open, from public sources.

What's new

• Silent install. Run the installer with /S for unattended or managed installs: no windows, the app isn't opened, and the exit code reports the result (0 means success). If it fails, the reason is written to %TEMP%\sap-mcp-bridge-install-error.log.
• Built by GitHub Actions from this repository. The Node.js runtime and Electron are downloaded from their official sources and checked against pinned SHA-256 hashes. The MCP server and its dependencies are installed from npm exactly as locked, with integrity hashes. Every build publishes a fingerprint of the app's contents, so anyone can rebuild the same commit and compare.
• Privacy policy added to the repository: https://github.com/Muhammad-Abdullah333/SAP-MCP-Bridge/blob/main/PRIVACY.md

The app itself is unchanged from 1.0.0. Your connections, passwords and certificates are kept when you update.

Download

Download SAP-MCP-Desktop-Bridge-1.0.1-Windows-Setup.exe below and run it. You need Windows 10 or 11 and Claude Desktop or Codex. Nothing else to install: the installer includes its own Node.js runtime.

The installer isn't code-signed yet, so Windows shows a SmartScreen notice the first time: choose More info → Run anyway. You can check the download against SHA256SUMS-1.0.1.txt.

If the app helps you, a ⭐ on the repository helps other SAP developers find it.

SAP MCP Connection Manager 1.0.0

The first release. SAP MCP Connection Manager keeps your SAP connections in one place and makes them available to an AI client, Claude Desktop or Codex, through a local MCP server, with a safety policy that is checked before any request reaches SAP.

Download

Download SAP-MCP-Desktop-Bridge-1.0.0-Windows-Setup.exe below and run it. It installs for your Windows user only, needs no administrator rights, and opens the manager when it finishes. Windows may show a SmartScreen notice the first time: choose More info → Run anyway.

SHA-256: 4df7f78ce79a8d2796ec594f1612088f3694eb9985e8bd04b1641ff9fb9faed6

Nothing else to install. The installer includes its own Node.js runtime. You need Windows 10 or 11, Claude Desktop or Codex, and an SAP account with ADT access.

What it does

• Connections in one place. Add an SAP system once, with its URL, client, user and optional CA certificate. Passwords are encrypted for your Windows account, never kept in a plain file.

• Clients configured for you. Configure MCP clients registers the connection with Claude Desktop and Codex, backing up each client's configuration first.

• A default system. With several connections, the one marked Default system is used whenever a request doesn't name a system.

• A safety policy per connection, answered as two questions:

  • What may it change? Read only; Custom can be changed, standard is read only; or Standard and custom can both be changed. A new connection starts read only.
  • What data may it read? Named tables only, or its own SQL queries as well.

  Lists of packages, transports, tables and tools narrow it further, and the form rates the whole policy Low, Medium or High.

• The middle level also denies the debugger, abapGit and running ABAP snippets or classes, and names anything the namespace limit still doesn't cover.

• Encrypted backups that can be moved to another computer and opened with the passphrase.

• Diagnostics that start the connection exactly as your AI client will and report where it fails.

What it cannot do

• Smartforms, Adobe Forms and SAPscript cannot be edited by the AI. They are built in SAP GUI (SMARTFORMS, SFP, SE71), which the development interface does not offer. Make form changes manually.
• The policy is a safeguard, not a replacement for SAP authorisations. Everything the AI does runs as your SAP user.

Known limitations

• There is no Add/Remove Programs entry. Remove the app with Uninstall.ps1 in its install folder (see the README).
• Renaming a connection leaves its previous saved password in the credential store.