SAP S/4HANA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRY_RUN | No | When 'true', all write operations are blocked | false |
| LOG_LEVEL | No | Log level: debug, info, warn, error | info |
| AUTH_METHOD | Yes | Authentication method: 'basic' or 'token' | |
| S4_ODATA_HOST | Yes | Full SAP S/4HANA URL including scheme and port | |
| S4_ODATA_USER | No | SAP user (required when AUTH_METHOD=basic) | |
| S4_ODATA_TOKEN | No | Bearer token (required when AUTH_METHOD=token) | |
| S4_ODATA_CLIENT | Yes | SAP client number | |
| S4_ODATA_PASSWORD | No | Password (required when AUTH_METHOD=basic) |
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 |
|---|---|
| discover_sap_servicesA | Discovers available OData services from the SAP Gateway Service Catalog. Returns service names, titles, and descriptions. Use this first when you don't know which service name to pass to execute_odata_query or get_entity_metadata. |
| get_entity_metadataA | Fetches and summarizes OData service metadata from SAP S/4HANA. Returns all entity sets with their key fields, properties, and navigation properties. Use this before calling execute_odata_query to understand the available fields and correct entity names. |
| get_field_valuesA | Fetches dropdown and value-list options from a SAP S/4HANA OData entity. Use this to discover valid input values before writing data with execute_odata_query. Provide the entity set that acts as the value-help source and the target field name. |
| execute_odata_queryA | Executes OData CRUD operations against SAP S/4HANA. GET requests return data as CSV for easy reading. POST, PATCH, and DELETE return JSON with the operation result. Use discover_sap_services to find service names, get_entity_metadata for field names, and get_field_values for valid input values before writing. |
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 4 tools
Each tool has a distinct purpose: service discovery, query execution, metadata retrieval, and field values. No overlap, clear differentiation.
All tool names follow a consistent verb_noun pattern in snake_case: discover, execute, get, get. Uniform and predictable.
Four tools cover the essential workflow for interacting with SAP OData services efficiently. Not over- or under-scoped.
The tool set enables a complete cycle: discover services, understand metadata, fetch valid input values, and perform CRUD operations. No critical gaps.