Name: SAP Integration Suite
Author: 1nbuc

LABSCO SUMMARY

"Still experimental, use at your own risk" is the first line of the README, and it is about an integration platform.

SAP Integration Suite moves data between systems that a business runs on, so the blast radius of a mistake is not the tool, it is whatever the pipeline touches. An author who leads with that warning is being straight with you. Read it as an invitation to try it against a sandbox tenant, not as boilerplate. The companion server for trading-partner content is worth knowing about — the split is deliberate, not an oversight.

What it is

A server for SAP Integration Suite, written by a practitioner and published with an explicit experimental warning.

What you get

Interaction with SAP Integration Suite. The author recommends pairing it with their separate trading-partner server, which covers content the main one does not.

Requirements

Node with npm, at a version recent enough for native fetch. Built from source rather than installed from a registry, with configuration through an environment file.

Setup effort

Build from source — git clone https://github.com/1nbuc/mcp-integration-suite.git

See installation options

USE CASES

01

Asking about an integration

Reach the platform from where you are working.

search-docspackagespackageget-all-iflowsget-iflowget-iflow-endpointsiflow-imageget-messagescount-messages

02

Covering the partner side too

Pair it with the author's separate trading-partner server.

27 tools

Listed in project docs. Your client may show a different list.

packages

package

create-package

get-iflow

create-empty-iflow

update-iflow

get-iflow-endpoints

iflow-image

deploy-iflow

get-iflow-configurations

get-all-iflows

get-messagemapping

update-message-mapping

deploy-message-mapping

create-empty-mapping

BEFORE YOU INSTALL

What to know first

Tools you get

27 tools named in the project's documentation. Trading-partner tools such as create-trading-partner belong to the sibling server mcp-is-tpm, not this one. The server must be cloned and built before it runs.

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

You clone and build this one yourself.

Server setup

Prerequisite: NodeJs and NPM, Node version > 20 (native fetch is required)

TERMINAL

git clone https://github.com/1nbuc/mcp-integration-suite.git
cd mcp-integration-suite
npm install
npm run build
cp .env.example .env

Open .env and enter your SAP Integration Suite connection details

Add the mcpServers block to your AI client's MCP config — for Claude Desktop, that file is ~/Library/Application Support/Claude/claude_desktop_config.json

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "mcp-integration-suite": {
      "command": "node",
      "args": [
        "<YOUR_PROJECT_PATH>/dist/index.js"
      ],
      "autoApprove": []
    }
  }
}

SAP Integration Suite