GuniWeb SAP MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add guniweb-sap-mcp -- npx -y guniweb-sap-mcp

{
  "mcpServers": {
    "guniweb-sap-mcp": {
      "args": [
        "-y",
        "guniweb-sap-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.guniweb-sap-mcp]
command = "npx"
args = ["-y", "guniweb-sap-mcp"]

{
  "mcpServers": {
    "guniweb-sap-mcp": {
      "args": [
        "-y",
        "guniweb-sap-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "guniweb-sap-mcp": {
      "args": [
        "-y",
        "guniweb-sap-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SAP_BASE_URL (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). The author declared them in the registry entry; get the values from the project itself.