↓ Skip to main content
Rillsoft AI
Connect Rillsoft

Developers: the MCP server contract

Connect SAP and Rillsoft in one AI client

Set up the bridge and AI client, then verify the SAP and Rillsoft connections separately before creating a project.

Connect the SAP Gateway and the local Rillsoft MCP server in the same AI client. Test each connection read-only before creating a planning example.

Verification scope: Rillsoft Project 10.0.626, SAP S/4HANA Cloud sandbox via the MCP Gateway. iFlow import checked on 22 October 2026; packaged scenarios, SAP connection, reconciliation and restoration rechecked on 23 October 2026; free prompt run in German and English through to the report passed on 24 October 2026. A rebuild in a fresh environment with a new SAP account follows the publication; whatever it finds will be corrected.

Starting point: Set up SAP MCP Gateway for Rillsoft is complete through the started MCP server; the package from Reproduce the Rillsoft SAP demo step by step is unpacked. Node.js and Python must run locally. Credentials remain in your private file.

Check the bridge and connect Claude
#

AI: check the local files, then the connection. Replace only the path to the credentials file; never put keys in command lines:

cd C:\Rillsoft-SAP
node --check bridge.js
$env:SAP_MCP_ENV_FILE = 'C:\Rillsoft-SAP-Keys\sap_mcp.env'
node check.js

Check: initialize: OK, tools/list: 6 tools, finally PASS for three orders in plant 1710 with descending start dates. Missing tools, a failed filter or a timeout produce a failing exit code. Order data is not printed. Investigate changes in sandbox data instead of reporting success.

For Claude Code:

claude mcp add sap-gateway --scope user -e SAP_MCP_ENV_FILE=C:\Rillsoft-SAP-Keys\sap_mcp.env -- node C:\Rillsoft-SAP\bridge.js

For Claude Desktop: Settings → Developer → Edit Config. Add sap-gateway from claude_desktop_config.example.json under mcpServers, preserving existing entries. Use absolute paths, then fully restart Desktop.

Start Rillsoft Project before Claude. Connect the second server using Connect Claude to Rillsoft MCP. In Claude /mcp or Developer, check that both servers are connected. Begin read-only: query SAP work centres in plant 1710 and read the Rillsoft project name with rillsoft_project_tree_get. The subsequent transfer needs write access in Rillsoft; SAP remains GET-only.

Recognise errors
#

If tools/list stays empty, the filter check fails or Rillsoft Project reports its session limit, use the error table of the reproduction guide: Recognise and resolve errors.

Next step
#

Check SAP production order capacity with AI · Check SAP maintenance workforce capacity with AI · Reproduce the Rillsoft SAP demo step by step

Back to Connect Rillsoft Project to SAP.

Product version
Rillsoft Project 10.0.626; SAP Integration Suite Trial