# GuniWeb SAP MCP [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/guniweb/guniweb-sap-mcp  
**GitHub Stars:** 3  
**npm Downloads (last month):** 1697  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/guniweb-sap-mcp

## Description
SAP S/4HANA and ECC: OData V2/V4, IDoc and RFC/BAPI for n8n and other MCP clients

## Tools
Capabilities this server exposes over MCP:

- **test-connection** — Stage-by-stage connection diagnosis (DNS → TLS → auth → client → catalog); names the first failing stage
- **sap_list_services** — List entity sets in an OData service (paged, default 50)
- **sap_discover_services** — Discover all services with category filtering and search
- **sap_get_metadata** — Inspect entity types, properties, keys, and what SAP allows per entity set (creatable/updatable/deletable)
- **sap_read** — Read a single entity or collection
- **sap_query** — Query with OData $filter, $select, $expand, paging (default `top` 50)
- **sap_nl_query** — Natural language query with structured filters
- **sap_create** — Create entities (supports deep insert + draft services)
- **sap_update** — Update entities (automatic ETag handling)
- **sap_delete** — Delete entities (automatic ETag handling)
- **sap_function** — Call V2 function imports or V4 actions/functions
- **sap_batch** — Execute multiple operations in a single batch
- **sap_idoc_send** — Send IDoc to SAP via HTTP/XML
- **sap_idoc_list_received** — List received IDocs from webhook
- **sap_idoc_status** — Check IDoc processing status
- **sap_idoc_discover** — Discover available IDoc types
- **sap_rfc_call** — Call any RFC-enabled function module with zod-validated parameters
- **sap_rfc_metadata** — Fetch function-module signature (imports/exports/tables/exceptions)
- **sap_bapi_call** — Invoke a BAPI, parse BAPIRET2 return tables, pin connection for follow-up commit
- **sap_bapi_commit** — Invoke `BAPI_TRANSACTION_COMMIT` on the pinned session
- **sap_rfc_search_functions** — Find function modules by name pattern via `RFC_FUNCTION_SEARCH
- **sap_enable_tools** — Activate/deactivate tool tiers at runtime

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "guniweb-sap-mcp": {
    "command": "npx",
    "args": ["-y","guniweb-sap-mcp"],
    "env": {
      "SAP_BASE_URL": "",
      "SAP_AUTH_TYPE": "",
      "SAP_USERNAME": "",
      "SAP_PASSWORD": "",
      "SAP_CLIENT": "",
      "SAP_MCP_TRANSPORT": "",
      "SAP_MCP_PORT": "",
      "SAP_MCP_DEMO": ""
    }
  }
}
```

**Requires environment variables:** `SAP_BASE_URL`, `SAP_AUTH_TYPE`, `SAP_USERNAME`, `SAP_PASSWORD`, `SAP_CLIENT`, `SAP_MCP_TRANSPORT`, `SAP_MCP_PORT`, `SAP_MCP_DEMO` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What GuniWeb SAP MCP does

GuniWeb SAP MCP MCP server exposes SAP S/4HANA and ECC capabilities to n8n and other MCP hosts. It covers OData V2 and V4 services, HTTP/XML IDocs, and RFC/BAPI calls. The available operations include service discovery, metadata inspection, entity reads and queries, creates, updates, deletes, function imports, actions, and batch requests.

IDoc tools can send documents to SAP, inspect received documents, check processing status, and discover available IDoc types. RFC and BAPI tools support function lookup, signature retrieval, validated calls, BAPI return-table parsing, and a pinned follow-up commit through `BAPI_TRANSACTION_COMMIT`.

The project fits the 🛠️ Other Tools and Integrations category and is aimed at AI-assisted workflows where a human or workflow author determines which SAP operations are allowed and in what sequence.

## How it works

The MCP layer sits between an MCP client and the configured SAP system. OData requests use the selected SAP endpoint and can work with service catalogs, entity metadata, filters, selections, expansions, paging, ETags, deep inserts, and draft services. Natural-language queries are converted into structured OData filters by `sap_nl_query`.

Authentication supports eight documented modes: basic, user-basic, OAuth2, API key, SAP IAS, SAP XSUAA, BTP principal propagation, and SAML bearer. Named destinations can select among multiple SAP systems based on the inbound Bearer token. IDoc HTTP/XML support does not require RFC connectivity.

The server offers stdio, Streamable HTTP, and SSE transports. It can run locally from npm, in Docker, or beside n8n. A demo mode supplies an in-memory mock OData gateway for testing without an SAP system; its data is local and disappears when the process stops.

## Setup and configuration

Install the package globally with npm or run the published container image. A typical direct configuration sets `SAP_BASE_URL`, `SAP_AUTH_TYPE`, `SAP_USERNAME`, `SAP_PASSWORD`, and `SAP_CLIENT`. The client value matters for client-dependent SAP Gateway systems. The default transport is stdio; HTTP mode can be enabled with the transport and port options.

Use `--allow-write` to enable create, update, delete, and other write-capable operations. Tool tiers can be restricted at startup, and `sap_enable_tools` can activate permitted tiers at runtime. For an HTTP deployment, the server supports an API key for MCP access and a separate webhook secret for inbound IDocs.

The Docker image includes OData and HTTP/XML IDoc functionality. RFC and BAPI use requires the SAP NW RFC SDK, which must be installed on the host because it cannot be included in the public image.

## Tools and capabilities

GuniWeb SAP MCP MCP server includes tools for:

- Diagnosing DNS, TLS, authentication, client, and catalog connection stages.
- Discovering OData services and entity sets, with category filters, search, and paging.
- Reading metadata and determining whether entity sets support create, update, or delete operations.
- Reading and querying entities with OData filters, selections, expansions, and paging.
- Creating, updating, and deleting entities with deep insert, draft support, and automatic ETag handling.
- Calling OData functions, actions, RFC-enabled function modules, and BAPIs.
- Sending and tracking IDocs, including received-IDoc webhook records.
- Executing multiple operations in one batch and enabling permitted tool tiers.

## Limitations and notes

Writes are disabled unless explicitly enabled. Per-token policies can impose more restrictive read-only and tool-tier limits. IDoc and RFC tools are hidden when their required configuration is unavailable.

The server communicates with the SAP and BTP endpoints configured by the operator and does not send usage statistics, update checks, or crash reports. Tool calls and individual SAP requests have configurable timeouts. When a whole-tool timeout is reached, the client receives a valid MCP response that indicates truncation rather than an indefinitely hanging connection.

_Full upstream README: https://allmcps.com/mcp/guniweb-sap-mcp/readme_