MCP SAP GUI Server
Related Servers
Alternatives to MCP SAP GUI Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that connects AI assistants to SAP ABAP systems, enabling table browsing, report execution, and transaction navigation via SOAP/RFC and SAP WebGUI.77 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 gradedqualityDmaintenanceA production-ready MCP server that enables LLMs to automate SAP GUI using RoboSAPiens, supporting both stdio and SSE modes.14Apache 2.0

dassian-adtofficial
AlicenseNot gradedqualityCmaintenanceMCP 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.21MIT
TDQS
Scored across 59 tools
Most tools are distinguishable because descriptions explicitly call out element types and restrictions, but there are several overlapping boundaries: sap_get_popup_window vs sap_handle_popup, sap_set_field vs sap_set_batch_fields/sap_select_combobox_entry, and the many ALV/TableControl/tree variants. An agent can usually infer the right tool, but only after reading careful type-specific notes.
Tool names consistently use the sap_ prefix followed by snake_case verb_noun phrasing, such as sap_read_table, sap_press_button, and sap_get_tree_node_children. Variants like ALV and TableControl tools follow predictable naming patterns rather than mixing conventions.
With 59 tools, the surface is far beyond a well-scoped set and includes many micro-variants for tables, trees, popups, and screen discovery. Even for a complex SAP GUI domain, this creates a heavy selection and maintenance burden.
The set covers connection/session management, navigation, field input, tables, trees, popups, lists, screenshots, previews, and confirmation gates, so it is quite complete for SAP GUI automation. Minor gaps remain, and some workflows rely on combinations of many small tools rather than direct lifecycle operations.