sap-s4hana-odata-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| S4HANA_SYSNR | Yes | SAP system number (00-99) | |
| S4HANA_CLIENT | No | SAP client number | |
| S4HANA_HOSTNAME | Yes | S/4HANA application server hostname | |
| S4HANA_PASSWORD | Yes | Password | |
| S4HANA_USERNAME | Yes | SAP technical user | |
| S4HANA_USE_HTTPS | No | Use HTTPS (default: true) | true |
| S4HANA_ODATA_PATH | No | OData service path (default: /sap/opu/odata/sap/API_BUSINESS_PARTNER) | /sap/opu/odata/sap/API_BUSINESS_PARTNER |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_business_partnersB | List business partners from SAP S/4HANA. Supports OData filtering, sorting, pagination, and field selection. Category '1' = Person, '2' = Organization. Use $filter for search, e.g. substringof('keyword',BusinessPartnerFullName). |
| get_business_partnerA | Get a specific business partner by ID from SAP S/4HANA. Returns full details. Use $expand to include related data like addresses or roles. |
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 2 tools
list_business_partners and get_business_partner are clearly distinct: one handles collection-level querying with filters/pagination, the other handles single-record retrieval by ID. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun convention: list/get + business_partner, with plural for the collection and singular for the individual resource. The naming is clean, predictable, and consistent.
Two tools is borderline for the server's stated scope. It is sufficient for a minimal business partner lookup server, but the generic 'sap-s4hana-odata-mcp' name suggests a broader OData surface, so the tool count feels thin at the low end.
The tool set covers basic read/query needs for business partners via list and get, but it lacks create/update/delete operations and exposes no other S/4HANA entities. Agents needing write capabilities or non-business-partner data will hit dead ends.