MCP SAP GUI Server
Related Servers
Alternatives to MCP SAP GUI Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server that connects AI assistants to SAP ABAP systems, enabling table browsing, report execution, and transaction navigation via SOAP/RFC and SAP WebGUI.74 npmISC
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI assistants to SAP systems via the ADT REST API, enabling read, write, syntax-check, and activation of ABAP code directly from the chat.3MIT
- FlicenseBqualityNot gradedmaintenanceAn MCP server that enables AI assistants to interact with SAP systems via the ABAP Development Tools (ADT) REST API. It allows users to read ABAP source code, inspect DDIC objects, and execute SQL queries directly.66-
- AlicenseNot gradedqualityNot gradedmaintenanceAn enterprise-grade MCP server that enables AI agents to execute SAP RFC functions and read business data securely through the Model Context Protocol.MIT
- AlicenseNot gradedqualityFmaintenanceA production-ready MCP server that enables LLMs to automate SAP GUI using RoboSAPiens, supporting both stdio and SSE modes.13Apache 2.0

dassian-adtofficial
AlicenseNot gradedqualityDmaintenanceMCP server for SAP ABAP development via the ADT API. Connect AI assistants to your SAP system — read, write, test, and deploy ABAP code without SAP GUI.18MIT
TDQS
Scored across 60 tools
Most tools target clearly distinct SAP GUI controls or actions (ALV vs TableControl vs tree vs list vs popup), and descriptions explicitly note incompatibilities. However, with 60 tools there remains some overlap, e.g. sap_set_field vs sap_select_combobox_entry for dropdowns, and sap_get_popup_window vs sap_handle_popup, which could cause occasional misselection.
All tools use a consistent sap_ prefix and snake_case verb_noun naming. Minor semantic variation between read_* for content and get_* for metadata is predictable, not chaotic.
60 tools is an extreme mismatch for a single MCP server, far beyond the 3-15 well-scoped range. Even though SAP GUI automation is broad, the surface is too large for an agent to navigate efficiently and risks tool-choice overload.
The set covers connection management, screen and session inspection, fields, tables/ALV grids, tree controls, lists, popups, text editors, toolbars, guided workflows, policy profiles, screenshots, previews, and gated writes. No obvious CRUD or lifecycle operation for the stated SAP GUI automation domain is missing.