io.github.kts982/mcp-sap-gui
PYPI · MCP-SAP-GUI · SCANNED SEP 20
SAP GUI for Windows automation for AI agents - 60 structured tools via SAP GUI Scripting API
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6914 tokens (~113/item across 61 items; 60 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 3% of tool parameters carry a description.Partial
- Structured output schemas are declared (97% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 62 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.kts982/mcp-sap-gui server?
io.github.kts982/mcp-sap-gui runs locally as a PyPI package, launched with uvx mcp-sap-gui. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-sap-gui
claude mcp add kts982-mcp-sap-gui -- uvx mcp-sap-gui
{
"mcpServers": {
"kts982-mcp-sap-gui": {
"command": "uvx",
"args": [
"mcp-sap-gui"
]
}
}
} {
"servers": {
"kts982-mcp-sap-gui": {
"command": "uvx",
"args": [
"mcp-sap-gui"
]
}
}
} codex mcp add kts982-mcp-sap-gui -- uvx mcp-sap-gui
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kts982-mcp-sap-gui": {
"type": "local",
"command": [
"uvx",
"mcp-sap-gui"
],
"enabled": true
}
}
} openclaw mcp add kts982-mcp-sap-gui --command uvx --arg mcp-sap-gui
mcp_servers:
kts982-mcp-sap-gui:
command: "uvx"
args: ["mcp-sap-gui"] {
"McpServers": {
"kts982-mcp-sap-gui": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-sap-gui"
]
}
}
} assistant mcp add kts982-mcp-sap-gui -t stdio -c uvx -a mcp-sap-gui
{
"mcpServers": {
"kts982-mcp-sap-gui": {
"command": "uvx",
"args": [
"mcp-sap-gui"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +15
- Stability: 0.80 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 102 → 113 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.3.0 → 0.4.0 functional
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcp-sap-gui@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sap_select_table_row ~74
Select a row in a table/grid. Works on both ALV grids and table controls. Row index is zero-based. For ALV: uses absolute row index. For TableControl: scrolls to make the row visible first if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| row | integer | yes | – |
| table_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_select_tree_node ~59
Select a node in a tree control. Highlights the node without opening it. For SPRO-style trees, use sap_click_tree_link on the execute icon column instead.
| Name | Type | Req | Description |
|---|---|---|---|
| node_key | string | yes | – |
| tree_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_send_key ~115
Press a keyboard key / function key in the SAP window (sendVKey). Common keys: Enter (confirm), F1 (Help), F3 (Back), F4 (search help / value help), F5 (Refresh), F8 (Execute), F11 (Save), F12 (Cancel/Escape). Also supports Shift+F1..F9 and Ctrl+F, Ctrl+G, Ctrl+P. F11 / Save requires user confirmation via elicitation before proceeding.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_set_batch_fields ~189
Fill in multiple input fields at once (dict of field_id to value). Use this to fill a form or selection screen in one call — more efficient than repeated sap_set_field calls. Table-control cells work too: take the cell_id template of each column from sap_read_table(columns_only=true) and replace {row}. The result gives counts; `results` lists only the fields that did NOT succeed (all of them with verbose=true).
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Dict mapping field_id -> value. |
| skip_readonly | boolean | – | Silently skip fields whose element reports Changeable == False instead of counting them as failures. |
| validate | boolean | – | Press Enter after setting fields and return status-bar feedback. Skipped when no fields were actually set. |
| verbose | boolean | – | List every field in `results`, not only the failures. |
Structured output declared, but exposes no named fields.
No examples provided.
sap_set_confirmation_points ~342
Choose which SAP operations need the user's explicit approval first. Replaces this session's set of confirmation points. When a point is active, every matching tool call pauses and asks the user to approve it (MCP elicitation) before anything reaches SAP; declining returns an error and nothing is executed. Points: - transactions: sap_execute_transaction - batch_fields: sap_set_batch_fields - field_writes: sap_set_field, sap_modify_cell, sap_set_textedit, sap_select_checkbox, sap_select_radio_button, sap_select_combobox_entry - all_writes: every write-tagged tool. Strict and noisy — many write tools only select, scroll or navigate, and they will all prompt. Under all_writes, sap_send_key("F11") asks twice: once for the category and once for the unchanged save gate. 'save' (F11 / Save key, Save toolbar button) is always on and cannot be turned off. Points set by the server's --confirm flag cannot be removed either. Adding a point is silent; *removing* one asks the user first, and a declined removal keeps the point. Confirmation prompts block until the user answers, and on clients without elicitation support the gated call fails instead of running unconfirmed (same fail-closed rule as the save gate). On such a client points also cannot be removed, so activating one there blocks that whole category for the rest of the session. Call sap_preview before a gated action so the user can see the screen and pending values first.
| Name | Type | Req | Description |
|---|---|---|---|
| points | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_set_current_cell ~60
Set the current (focused) cell in an ALV grid or table control. Useful before pressing toolbar buttons that act on the current cell.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | yes | – |
| grid_id | string | yes | – |
| row | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_set_field ~89
Set (type/enter) a value into an input field on the current SAP screen. Works on GuiTextField and GuiCTextField input fields. For filling in multiple fields of a form at once, use sap_set_batch_fields instead. After setting a field, you may need to press Enter to trigger validation.
| Name | Type | Req | Description |
|---|---|---|---|
| field_id | string | yes | – |
| value | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_set_focus ~65
Set focus to any screen element by its ID. Some SAP actions require focus on a specific element before they work (e.g., F4 search help on a field). Use this to set focus before sending keys with sap_send_key.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_set_policy_profile ~114
Switch the active policy profile for this session. Profiles control which tools are visible: - exploration: read-only tools (discover, inspect, screenshot) - operator: read + write tools (normal SAP interaction) - full: all tools including destructive (transaction execution) A session can only restrict, never widen: if the server was started with --profile, a request above that floor is capped to the floor. Default profile is 'full' unless the server was started with --profile.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sap_set_textedit ~49
Write text into a multiline text editor (GuiTextedit) — long texts, notes, comments, document text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
| textedit_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.kts982/mcp-sap-gui server?
io.github.kts982/mcp-sap-gui is listed in the public MCP registry as io.github.kts982/mcp-sap-gui. SAP GUI for Windows automation for AI agents - 60 structured tools via SAP GUI Scripting API. This page covers its PyPI package (mcp-sap-gui).
Is the io.github.kts982/mcp-sap-gui server safe to use?
io.github.kts982/mcp-sap-gui scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.kts982/mcp-sap-gui server expose?
io.github.kts982/mcp-sap-gui exposes 60 tools: sap_connect, sap_connect_existing, sap_list_connections, sap_get_session_info, sap_execute_transaction, and 55 more. Their descriptions and schemas cost roughly 5,676 tokens of context every time the server is loaded.
Is the io.github.kts982/mcp-sap-gui server still maintained?
io.github.kts982/mcp-sap-gui is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.