sap-abap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_CLIENT | Yes | SAP client number | |
| SAP_LANGUAGE | No | Logon language (default: EN) | EN |
| SAP_PASSWORD | Yes | Your SAP password | |
| SAP_USERNAME | Yes | Your SAP username | |
| SAP_WEBGUI_URL | Yes | Full WebGUI URL of your SAP system |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sap_loginA | Log in to the SAP system via WebGUI. Must be called before using any other SAP tool. Returns the welcome screen text on success. |
| sap_navigateB | Navigate to an SAP transaction code (e.g. SE11, SE16, SM30, SU01). Returns the HTML page text of the resulting screen. |
| sap_se16_browseA | Browse a database table via SE16 (Data Browser). Returns the first page of table contents as text. |
| sap_rfc_read_tableA | Read data from any SAP transparent database table using RFC_READ_TABLE over SOAP. Supports field selection, WHERE filters, row limits and offsets. No session required — uses Basic Auth directly. |
| sap_run_reportC | Run an ABAP report or program via the SA38 / SE38 transaction. |
| sap_execute_commandA | Submit an arbitrary command string (OK code / transaction) to the current SAP WebGUI session, as if typed in the command field. |
| sap_get_pageC | Fetch any SAP WebGUI URL and return the rendered page text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Several tools have fuzzy boundaries: sap_se16_browse and sap_rfc_read_table both read table data, while sap_navigate, sap_execute_command, and sap_get_page all retrieve rendered SAP pages and can be used to reach transactions. An agent would need to read descriptions very carefully to reliably pick the right tool.
All tools share a sap_ prefix and snake_case style, which helps, but the internal pattern is inconsistent: sap_navigate is a bare verb, sap_se16_browse leads with a transaction code, and sap_rfc_read_table mixes technical context with the action. It is readable but not a uniform verb_noun convention.
Seven tools is a reasonable size for an SAP interaction server and not bloated overall. However, the set could be tightened because some tools are near-duplicates in functionality, such as the two table-reading paths and the multiple page-fetching mechanisms.
Core workflows like login, navigation, table reads, and running reports are covered, but there is no logout or explicit session-management tool, and report output is only exposed as raw page text. Agents can work around some gaps via execute_command or get_page, but the surface is not fully lifecycle-complete.