Sap Gui MCP server

MCP SAP GUI Server

<!-- mcp-name: io.github.kts982/mcp-sap-gui -->

An MCP (Model Context Protocol) server that enables AI assistants to interact with SAP GUI for Windows through the SAP GUI Scripting API.

It is client-agnostic: if your MCP client can launch a local stdio server, it can use this project. Examples in this README use Claude because the setup is easy to demonstrate, but the same server can be used from Codex, GitHub Copilot, Gemini CLI, and similar MCP-capable tools.

Current release: 0.4.0 for local Windows use over MCP stdio.

Status

• GitHub workflows are included for CI, Docs, Dependency Audit, and tag-based Release.
• Primary repository: GitHub (kts982/mcp-sap-gui).

What's New

0.4.0 — shaped by two days of real agent work on a live system. The lesson was that token cost per call hurts more than missing tools, and that a few screens could not be reached at all:

• Lighter responses. A table control is one discovery element instead of one per cell (an SM30 screen went from 231 elements to 3), element IDs come back in the short wnd[0]/... form, and batch fills and popup actions report what matters instead of echoing everything.
• sapreadlist reads a classic report list (WRITE output, F4 hit lists) as lines of text with list colours and paging — 43 lines instead of 492 label elements, and no screenshot needed.
• View clusters work. Docking containers (wnd[0]/shellcont) are valid IDs and discovery points to them, so the dialog structure of SM34 and most IMG activities can be navigated. A new SM30 transaction guide covers table maintenance and view clusters end to end.
• Your transaction policy. Presets (default, abap-dev, strict) plus a policy file with glob patterns replace the hard-coded blocklist. Details: Security Considerations.
• Popups announce pre-filled values. When an action opens a popup, its response already says what the popup is and which inputs hold values you never chose — such as a customizing request pre-filled with another project's request.
• Screenshots to a file. sapscreenshot(savepath=...) writes a full-resolution PNG for documents and never overwrites a file.

sappreview — see it before it happens. The agent can now show you an approval card at any checkpoint: before a batch write, before saving, or whenever you ask ("before adding country GR, show me the values"*). It carries the current screenshot, session context, and the exact values about to be written — password-shaped values masked. On MCP Apps hosts (VS Code Copilot Chat) it renders as a rich inline card; everywhere else you get the same summary as text plus the screenshot. Saving still goes through the confirmation gate. Details: Rendered Preview Cards.

Confirmation points — nothing is written without you. Tell the agent once ("ask me before every field write") and the server enforces it: sapsetconfirmation_points activates categories of write operations that pause for your explicit approval before anything reaches SAP. Enforced server-side by middleware — declining blocks the call no matter what the agent does, removing a gate asks you first, and admins can pin gates for every session with --confirm. Details: Security Considerations.

What This Does

Shortened. The full README is on GitHub.