A **production-ready Model Context Protocol (MCP) server** that enables LLMs (Claude, Copilot, Cursor, etc.) to automate **SAP GUI** using the
If you already use Sapient MCP, the sapient mcp mcp server is the piece that lets your assistant work with it directly. A production-ready Model Context Protocol (MCP) server that enables LLMs (Claude, Copilot, Cursor, etc.) to automate SAP GUI using the RoboSAPiens library.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Cursor — Go to Cursor Settings → MCP → Add new MCP Server → type command, then enter:Windsurf — The Windsurf tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: SAPIENT_MCP_SAPLOGON_PATH, SAPIENT_MCP_CAPS, SAPIENT_MCP_OUTPUT_DIR, ROBOSAP_MCP_SAPLOGON_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
| Requirement | Details | |---|---| | OS | Windows 10/11 only (SAP GUI is Windows-only) | | Python | 3.10 or newer | | SAP GUI | SAP GUI for Windows installed | | SAP Scripting | Must be enabled on server (RZ11: sapgui/user_scripting=TRUE) AND in SAP Logon client settings |
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sapient MCP's toolset — Cursor, Windsurf — is a fair guide to whether it matches your workflow. It is maintained by toni-ramchandani; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | Go to Cursor Settings → MCP → Add new MCP Server → type command, then enter: |
| Windsurf | The Windsurf tool exposed by this server. |
{
"mcpServers": {
"sapient": {
"command": "python",
"args": ["-m", "sapient_mcp", "--caps", "screenshot,codegen,advanced"],
"env": {
"SAPIENT_MCP_SAPLOGON_PATH": "C:\\Program Files (x86)\\SAP\\FrontEnd\\SAPgui\\saplogon.exe",
"SAPIENT_MCP_OUTPUT_DIR": "C:\\sapient_output"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Requirement | Details | |---|---| | OS | Windows 10/11 only (SAP GUI is Windows-only) | | Python | 3.10 or newer | | SAP GUI | SAP GUI for Windows installed | | SAP Scripting | Must be enabled on server (RZ11: sapgui/user_scripting=TRUE) AND in SAP Logon client settings |
| Variable | Description | Required |
|---|---|---|
| SAPIENT_MCP_SAPLOGON_PATH | Filesystem location the server is allowed to use. | Optional |
| SAPIENT_MCP_CAPS | Configuration value read at startup. | Optional |
| SAPIENT_MCP_OUTPUT_DIR | Filesystem location the server is allowed to use. | Optional |
| ROBOSAP_MCP_SAPLOGON_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.