SAP GUI MCP Server
Related Servers
Alternatives to SAP GUI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to drive SAP GUI for Windows through the SAP GUI Scripting API — connecting to systems, running transactions, reading and writing screen fields, extracting ALV grid, table, tree, and report-list data, and capturing screenshots. Includes server-enforced confirmation points and previews so nothing is written to SAP without explicit user approval.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to execute SAP tasks through a cost-routing MCP server that tries API, recorded scripts, WebGUI, and computer-use vision in cheapest-first order, falling back only when needed. It can also promote an interactive GUI routine into a reusable recorded script to make repeat runs nearly free.1MIT
- AlicenseBqualityCmaintenanceAutomates interactions with SAP GUI using the Model Context Protocol, allowing precise control of SAP transactions through tools like clicking, typing, scrolling, and transaction management.12147MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to observe and control real Windows desktop applications — locating windows and controls via UI Automation, reading on-screen text with OCR and screenshots, then clicking, typing, filling forms, launching apps, and verifying results. Mouse and keyboard actions are visible on screen and can be halted instantly with Esc.1,600 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI platforms to see the screen and operate any desktop software through real mouse clicks, text input, key presses, and scripted scenario execution.MIT
- AlicenseAqualityBmaintenanceEnables AI tools to operate IBM i 5250 green screens, driving and testing interactive RPG programs by seeing screens, typing into fields, and pressing keys.626 npm1Apache 2.0
TDQS
Scored across 71 tools
Many tools are transaction- or object-specific, but the set contains clear overlaps: sap_get_form_fields vs sap_discover_fields, sap_set_field vs sap_select_dropdown/sap_fill_form, sap_screenshot vs browser_screenshot, and browser_* UI controls vs the SAP-native click/fill/keyboard tools. Descriptions give preferred-order hints, but boundaries remain fuzzy enough that an agent can easily choose the wrong discovery or interaction tool.
All names use lower_snake_case, but there is no uniform verb_noun pattern: sap_get_screen_text and sap_set_field coexist with sap_transaction, sap_session_list, sap_keepalive_start, and sap_abapgit_list_repos. The sap_*, browser_*, search_*, log_*, and bare choose prefixes namespace some tools, but verb order and prefix conventions are mixed.
At 71 tools this surface is extremely oversized for a single MCP server, even for the broad SAP GUI automation domain. It includes overlapping UI layers, auxiliary logging/choice tools, and multiple session-management utilities that would be better consolidated or split into focused servers.
Coverage is unusually broad: login/session management, screen/form interaction, transactions, table/query lookups, ABAP metadata and editing, transports, logs, jobs, dumps, IMG search, and abapGit. Gaps remain around ABAP debugger control and creating new ABAP objects, but those are explicitly scoped limitations rather than fatal omissions.