sap-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_HOST | Yes | Application server host (required) | |
| SAP_PORT | No | ICM port | 8000 |
| SAP_USER | Yes | Development user (required) | |
| SAP_CLIENT | Yes | Client, e.g. 100 (required) | |
| SAP_LANGUAGE | No | Logon language | EN |
| SAP_PASSWORD | Yes | Development user password (required) | |
| SAP_PROTOCOL | No | https or http | http |
| SAP_TIMEOUT_MS | No | HTTP timeout | 30000 |
| SAP_MCP_AUDIT_FILE | No | Audit log target (/data/audit.jsonl in Docker) | logs/audit.jsonl |
| SAP_MCP_POLICY_FILE | No | Path to your own policy | config/policy.json |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sap_test_connectionA | Checks the connection to the SAP system and reports user, client and number of available ADT resources. |
| sap_search_objectsB | Searches repository objects. Returns name, type and package. |
| sap_read_metadataA | Reads type, package, owner and version of an object. |
| sap_read_sourceB | Reads the source code of a development object. |
| sap_list_transportsA | Lists open transport requests of the logged-on user. |
| sap_write_sourceA | Replaces the source code of an existing object. Only inside the allowed packages. Activation is a separate step that requires approval. |
| sap_activateA | Activates an object. Requires human approval: the call returns an approval request and does not execute. |
| sap_release_transportA | Releases a transport request. Requires human approval and is subject to separation of duties. |
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 8 tools
Each tool targets a distinct resource/action: connection test, search, metadata read, source read, transport list, source write, activation, and transport release. No overlaps or ambiguous boundaries.
All tools follow a consistent snake_case verb_noun pattern with the 'sap_' prefix, making the API predictable and easy to navigate.
8 tools is well-scoped for a SAP development server, covering the essential operations without redundancy or unnecessary bloat.
The set covers the core lifecycle: search, read, edit, activate, and release transports. Missing create/delete operations, but these are often not permitted via API in SAP, so the gap is minor.