Intelligent SAP GUI automation for AI agents — MCP server powered by RoboSAPiens
SAPient MCP has 11 tools with consistent naming (sap_verb_noun pattern) and descriptions present for all tools. However, parameter descriptions are sparse or missing for several tools. Input schemas are visible and properly typed for most tools, but output schemas are undocumented, responses are plain text or JSON strings without formal schema declarations. Error handling exists but lacks recovery guidance. The server follows basic tool patterns but falls short of production-grade quality in schema completeness and LLM-optimized descriptions.
Click on a tab in the current SAP screen by its visible label text.
Close the SAP GUI application. Ends the SAP session.
Attach to an already-running SAP GUI session. Use when SAP is pre-launched (e.g. SSO environments) or when you want to take control of an existing session.
Connect to an SAP server using the description shown in the SAP Logon list. Use the DESCRIPTION (not SID). SAP Logon must already be open (sap_open). After connecting, the SAP login screen appears.
Execute a SAP transaction code. Use /n prefix to navigate to a new transaction from anywhere (e.g. /nME21N). Use /o prefix to open in a new session window.
Fill a text input field in SAP GUI identified by its visible label or field name.
Output schemas undocumented. Tools return plain text or JSON strings without formal schema declarations. LLMs cannot reliably parse responses or plan downstream tool calls.
Descriptions lack LLM-optimized context. Many descriptions (e.g., sap_activate_tab, sap_send_key) are under 100 chars and omit WHEN to use the tool or what it returns. Baseline for A+ tools is 50-200 chars with clear intent.
Error handling returns plain text error messages without recovery guidance. Errors like 'ERROR: ...' do not tell the LLM what to do next or whether to retry. Missing pattern:recovery-guide implementation.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | <=2025-11-25 | v2 |
Return current session state, window title, and connection info. Read-only — safe to call anytime.
Return the title of the current SAP window. Read-only. Use to confirm navigation.
Launch SAP Logon (saplogon.exe). Must be called before sap_connect_to_server. Defaults to the configured saplogon_path if no path provided.
Navigate the SAP menu bar. Provide the full path as separate arguments, e.g. path=['Goto', 'Back'] or path=['Edit', 'Select All'].
Send a SAP GUI keyboard key. Common values: Enter, F1–F12, F3 (Back), F8 (Execute), PageDown, PageUp, Tab, Escape, Save (Ctrl+S equivalent).
Parameter descriptions are minimal or missing context. E.g., sap_send_key lists valid keys in description but does not explain when to use each. sap_select_menu_item lacks guidance on menu path format or common paths.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools are marked with Risk field in metadata but not via MCP tool annotations. LLMs cannot infer safety properties from tool definitions alone.