Driving the SAP GUI
Operating SAP's own user interface as a program rather than as a person — the desktop GUI or the Web GUI, driven through the Scripting API. Reached for when a transaction has no API at all, and increasingly when a change needs testing against the real screen rather than against the layer beneath it. Distinct from agent access to your codeAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed, which reaches the objects through ADT and never sees a screen.
Overview
No core answer is documented.
Not covered: At the API and the switch that enables it. SAP ships the GUI Scripting interface and the option in SAP Logon that turns it on, and everything above that — sessions, waits, recovery, screenshots — is written by whoever is driving it.
SAP's Scripting API is an interface inside the GUI and not something published as an artifact, so the core side of this concern has no entry of its own. This is also the corner of the corpus where SAP's API policy is most directly in question. Scripting the GUI to move business data is not development tooling, and the distinction belongs in the decision rather than in a footnote — see the SAP API Policy Evidence SkillSAP API Policy Evidence SkillAssesses whether a described SAP API usage aligns with the SAP API Policy, gathering live evidence from SAP's own sources and returning a sourced assessment with a stated confidence — and routing the legal questions away from itself.independent, btp on tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed.
MCP servers that drive the desktop GUI through the Scripting API, such as kts982/mcp-sap-guikts982/mcp-sap-guiSAP GUI for Windows through the Scripting API, deliberately client-agnostic, with CI, docs, a dependency audit and tagged releases wired up around it.independent, abap, through RoboSAPiens, as SAPient MCPSAPient MCPAn MCP server for SAP GUI automation built on RoboSAPiens, the Robot Framework library, rather than on the Scripting API directly, over stdio or SSE depending on the client.independent, abap does, or by screen coordinates with a screenshot after each action, as mcp-sap-guimcp-sap-guiThe earliest of the SAP GUI servers in the atlas. It works the screen by coordinates and hands back a screenshot after each action, with a setup script and a short path from clone to a driven transaction.independent, abap does. sapgui.mcpsapgui.mcpDrives the SAP desktop GUI and the Web GUI, and is built for the jobs a REST client cannot do — end-to-end testing against the real screen, visual validation, and screenshots for documentation.independent, abap also reaches the Web GUI and is built for testing. jrgkraus/tool-bitool-biBuilds an ABAP batch input transaction through chained method calls, one per screen, field and value, then runs it directly or writes it to a batch input session.independent, abap runs a transaction as batch input from ABAP, without a screen, and SAP's own joule-gui-automation-and-integrationSAP-samples/joule-gui-automation-and-integrationSample Joule capabilities that drive an SAP GUI for Windows session through the SAP Business Client's frontend actions, and patterns for feeding a GUI session's own state back into Joule.sap official, abap sample drives a GUI session from Joule.
Policy
PolicySAP API Policy 4.2026a§ 2.2.2, 3AlwaysAn MCP server drives SAP GUI for an agent, through its Scripting API or the screen.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
- § 3 Monitoring and remedies. SAP states that it may monitor API use and take enforcement actions when use does not comply with the documentation and policy.
Driving the user interface for an agent is still an agent executing a sequence of actions against the system. Check whether section 2.2.2 applies to the design, and that the user interface is not used as a way around the controls section 3 names.
SAP API Policy 4.2026a →Artifacts
Seen working
Details
Coverage
For your agent
- Ref
capability:gui-automation- JSON
- /capabilities/gui-automation.json
- MCP
- Connecting an agent