sapgui.mcp
Drives 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.
The only one of these that reaches both UIs, and the only one whose stated purpose is testing rather than automation. Because it drives the real interface rather than a headless API, it can confirm what a change actually looks like — which is the gap a syntax check and an activation leave open. Its README describes a two-agent arrangement with aibap.mcpaibap.mcpA Go server that closes the loop: after create, write and activate it can run the class it just wrote through ADT's classrun and hand the console output back.independent, abap, the same author's ADT server: one agent writes ABAP through ADT, a second drives this against the running system, captures screenshots and reports failures back. Works against R/3 and S/4, with unit tests, coverage, linting and formatting all enforced in CI.
Facts
Where it sits
Before choosing this
Signals
RepositoryNot reachableNot reachable since 2026-10-20
Since 2026-10-20 the repository this entry names answers that it does not exist.
Conditions
PracticalFunctional boundary
Driving the GUI reaches whatever a user can reach, which is business data and not a development surface. Decide what an agent may do in a session before granting one, not after. And a UI test is slower and more brittle than the layer below it: this is for what only the screen can answer.
PolicySAP API Policy 4.2026a§ 2.2.2, 3from Driving the SAP GUIAn 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 →What it declares
Every artifact
- Type
- MCP server
- Origin
- Independently maintained
Connections
Operating the SAP GUI programmatically
Download
Others providing
Compare all 5 on the Driving the SAP GUI page →- 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, abapChained-call builder for ABAP batch input transactionsfrom ABAP
- 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, abapMCP server for SAP GUI for Windows via the Scripting APIfrom ABAP
- 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, abapMCP server working SAP GUI by screen coordinatesfrom ABAP
- 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, abapSAP GUI automation MCP server built on RoboSAPiensfrom ABAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“The MCP works with both SAP R/3 and S/4.” — Hochfrequenz/sapgui.mcp — README
History in the atlas
- practical boundaries only
- Triaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.
- First seen.
For your agent
- Ref
artifact:hochfrequenz-sapgui-mcp- JSON
- /artifacts/hochfrequenz-sapgui-mcp.json
- MCP
- Connecting an agent