Log inSubmit server
GuniWeb SAP MCP logo

GuniWeb SAP MCP

Connects n8n and MCP clients to SAP S/4HANA and ECC through OData, IDoc, RFC, and BAPI tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install GuniWeb SAP MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "guniweb-sap-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "guniweb-sap-mcp"
      ],
      "env": {
        "SAP_BASE_URL": "YOUR_VALUE_HERE",
        "SAP_AUTH_TYPE": "YOUR_VALUE_HERE",
        "SAP_USERNAME": "YOUR_VALUE_HERE",
        "SAP_PASSWORD": "YOUR_VALUE_HERE",
        "SAP_CLIENT": "YOUR_VALUE_HERE",
        "SAP_MCP_TRANSPORT": "YOUR_VALUE_HERE",
        "SAP_MCP_PORT": "YOUR_VALUE_HERE",
        "SAP_MCP_DEMO": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y guniweb-sap-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 29d ago.

Overview

GuniWeb SAP MCP MCP server connects n8n and other MCP clients to SAP S/4HANA and ECC through OData V2/V4, IDoc, and RFC/BAPI interfaces. It provides discovery, metadata inspection, reads, queries, writes, function calls, batching, IDoc operations, and RFC/BAPI access through MCP tools. Read-only operation is enabled by default, while write access and tool tiers can be controlled with flags and token policies. Reach for it when an agent-assisted workflow needs governed access to SAP business data or operations.

Use cases

  • Discover SAP OData services for an n8n workflow
  • Query business partners or sales orders with OData filters
  • Create and update SAP entities with governed write access
  • Send IDocs and inspect their processing status
  • Call RFC functions or BAPIs from an MCP client

Key features

  • OData V2 and V4 CRUD, queries, metadata, and batch operations
  • IDoc sending, receiving, discovery, and status checks
  • RFC and BAPI calls with metadata and commit support
  • Natural-language to structured OData queries
  • Read-only defaults with configurable tool tiers
  • stdio, Streamable HTTP, and SSE transports

Tools22

What GuniWeb SAP MCP lets your agent do. Expand a tool for its parameters.

Self-reported~375 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · guniweb-sap-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads1.7kPackage downloads in the last 30 days.
Last commit12d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed22Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How GuniWeb SAP MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about GuniWeb SAP MCP

GuniWeb SAP MCP is an MCP server that connects n8n and other MCP clients to SAP S/4HANA and ECC. Its main tools cover OData V2/V4 discovery, reads, queries, and writes; IDoc operations; and RFC/BAPI calls. It also supports metadata inspection, function calls, batching, and connection diagnosis.

Install it globally with npm using `npm install -g guniweb-sap-mcp`, or run the published Docker image. Configure the SAP endpoint and authentication, then start the command in stdio mode or select HTTP or SSE transport as needed.

Set `SAP_BASE_URL`, choose an `SAP_AUTH_TYPE`, and provide the credentials required by that authentication mode. For a typical basic-auth setup, also set `SAP_USERNAME`, `SAP_PASSWORD`, and `SAP_CLIENT`, then start the server.

No, writes are disabled by default. Enable them explicitly with `--allow-write`; per-token policies and tool-tier limits can still restrict access further. The write-capable tools include entity creation, updates, deletes, and batch operations.

Yes, use the `--demo` option or set `SAP_MCP_DEMO=true`. Demo mode starts an in-memory mock OData gateway with sample services and data, and all changes disappear when the process ends.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGuniWeb SAP MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/guniweb-sap-mcp?style=directory)](https://allmcps.com/mcp/guniweb-sap-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/guniweb-sap-mcp"><img src="https://allmcps.com/api/badge/guniweb-sap-mcp?style=directory" alt="GuniWeb SAP MCP on AllMCPs" /></a>