sap-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_HOST | Yes | The hostname of the SAP S/4HANA system. | |
| SAP_PASS | Yes | The password for SAP authentication. | |
| SAP_USER | Yes | The username for SAP authentication. |
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 |
|---|---|
| get-business-partnersA | List Business Partners (customers, suppliers and organizations) from SAP S/4HANA. Returns the first N in ascending Business Partner ID order. By default returns ID, name, category, grouping, customer and supplier numbers, and creation details — pass |
| get-sales-ordersA | List Sales Orders from SAP S/4HANA, including net value, currency and processing status. Returns the first N in ascending Sales Order number order. Pass |
| get-purchase-ordersA | List Purchase Orders from SAP S/4HANA, including supplier and address. Returns the first N in ascending Purchase Order number order. Pass |
| list-entity-fieldsA | List the field names available on a SAP entity. Call this before passing |
| get-sap-dataA | Fetch data from any SAP S/4HANA OData path (read-only, GET only). Prefer get-business-partners / get-sales-orders / get-purchase-orders when they fit — they return far less data. Use this for other entities, entity-key reads like A_BusinessPartner('1'), navigation properties, $expand, $count and $metadata. Returns raw SAP JSON including __metadata, so keep $top small. |
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 5 tools
The three entity-specific getters are clearly distinct, and list-entity-fields serves an obvious separate purpose. get-sap-data overlaps with all getters, but its description clearly positions it as a fallback for other entities and advanced OData queries, so confusion is unlikely.
The first three tools consistently use get-<plural-resource>, and get-sap-data follows the get- prefix. list-entity-fields is the only deviation, using list instead of get, but the pattern is still readable and predictable overall.
Five tools is well-scoped for a read-only SAP S/4HANA connector. Each tool has a clear role, and the generic get-sap-data tool avoids the need to multiply entity-specific tools.
The server covers common entities with dedicated tools and provides a generic OData path for everything else, plus field discovery to support custom field requests. For a read-only data access server, the surface is complete with no obvious dead ends.