sap-s4-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_USER | No | Username for your own SAP tenant. | |
| SAP_API_KEY | No | Free SAP API key from https://api.sap.com, used to access the public sandbox. | |
| SAP_BASE_URL | No | Base URL of your own SAP tenant, used instead of the public sandbox. | |
| SAP_PASSWORD | No | Password for your own SAP tenant. | |
| SAP_MCP_MAX_ROWS | No | Caps the OData $top value returned to the model, regardless of what the model asks for. | 200 |
| SAP_MCP_ALLOW_WRITES | No | Writes are off unless SAP_MCP_ALLOW_WRITES=true, and they are always refused against the public sandbox. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for reading SAP S/4HANA data: business partners, sales orders and supplier invoices. Every answer should cite the document numbers it used. Write tools never change SAP directly: they create a proposal that a person approves outside this conversation. Tell the user the proposal id and that it is waiting for approval.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_business_partnersB | Find business partners (customers, suppliers) by part of their name. Returns id, full name, category (1 = person, 2 = organization) and creation date. |
| get_business_partnerB | Get one business partner with its addresses. |
| list_sales_ordersB | List sales orders, newest first. Args: sold_to_party: customer (business partner) id to filter on. created_from: only orders on or after this date (YYYY-MM-DD). |
| get_sales_orderB | Get one sales order with its line items. |
| list_supplier_invoicesB | List supplier invoices, newest posting date first. Args: invoicing_party: supplier id to filter on. posted_from: only invoices posted on or after this date (YYYY-MM-DD). |
| propose_delivery_blockA | Propose putting a delivery block on a sales order. Nothing changes in SAP until a person approves the proposal with
|
| list_proposalsB | List write proposals and their status (pending, executed, rejected, failed). |
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
Each tool has a distinct resource and action: business-partner search vs. lookup, sales-order get vs. list, supplier-invoice listing, and proposal workflow tools. There is little risk of an agent confusing the boundaries between these operations.
All tools follow a consistent snake_case verb_noun pattern, e.g. search_business_partners, get_sales_order, list_sales_orders, propose_delivery_block. The naming is predictable and readable throughout.
Seven tools is a well-scoped set for a focused SAP S/4 read-plus-proposal interface, and each tool has a clear role. The count is comfortably within a reasonable range and does not feel padded.
The surface covers business-partner lookup, sales-order retrieval, supplier-invoice listing, and one write proposal workflow, but notable gaps remain. There is no direct supplier-invoice detail getter, no business-partner list beyond search, and no broader sales-order create/update lifecycle coverage.