Repository navigation
Upcoming Split of COM API MCP and Web GUI MCP #1116
hf-kklein
announced in
Announcements
Replies: 1 comment
|
@Tianbe als fleißigster Web GUI Bug-Reporter: willst du maintainer des neuen MCP sein? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Right now this project allows you to choose your
BACKEND_TYPE: your AI agent drives either the SAP GUI through the COM scripting API (Windows only), SAP GUI for HTML (aka Web GUI). The web GUI backend is far less mature than the COM backend, as many open Web GUI issues show.Supporting both SAP Desktop GUI (via sapsucker + pywin32) and the Web GUI (via Chromium + Playwright) is a burden. Each build carries the dependencies and code of the backend it doesn't use. That makes the builds larger and the setup more complicated, both for developers and users.
So I think it's the right step to split the code bases:
This repo will support SAP GUI for Windows (COM) only. It will ship as Windows binary, without Docker, macOS or PyPI variants, so there is exactly one simple setup. The first COM-only release will be
v1.0.0.A new repo, sapwebgui.mcp, supports Web GUI only. Both repos start from the same release, v0.20.0. Open Web GUI issues will move there. The Web GUI repo is looking for a maintainer; without one, it may not receive updates.
If you use
BACKEND_TYPE=webgui, you can keep using v0.20.0 and switch to the new repo once it is published. If you use the COM backend, nothing changes for you except a simpler setup. Nothing changes about the features that are already shipped.Any opinions on this?
All reactions