GuniWeb SAP MCP Server

GuniWeb SAP MCP is an MCP integration. SAP S/4HANA and ECC: OData V2/V4, IDoc and RFC/BAPI for n8n and other MCP clients.

Packages and local setup

The published npm package is guniweb-sap-mcp, version 0.9.0. Its declared MCP transport is stdio.

The package declares SAP_BASE_URL (required): Base URL of the SAP system, including any path segment in front of /sap/opu/odata (e.g. https://s4.example.com or https://gateway.example.com/prefix); SAP_AUTH_TYPE: Authentication type: basic, oauth2, apikey, ias, xsuaa, btp-principal, saml-bearer; SAP_CLIENT: SAP client (Mandant). Appended to every request — a client-dependent Gateway answers 401 without it; SAP_USERNAME: SAP user for basic authentication; SAP_PASSWORD: Password for basic authentication; SAP_MCP_DEMO: Set to true to start a built-in mock S/4HANA instead of connecting to a real system. No SAP_ configuration needed — for trying the server out.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.9.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related workflow automation MCP servers for tools that cover the same kind of work.