To connect Joule Work Desktop (JWD) to SAP systems, add ARC-1 on SAP BTP as an MCP connector, sign in with your work account and select it in a conversation. JWD can then use ARC-1’s SAP tools alongside the files and other context you provide.

For ABAP work, ARC-1 is my first choice. It gives the desktop tools to investigate errors, read custom code and understand software changes. Below is the short setup guide and a support workflow that shows why the connection is useful.

MCP, short for Model Context Protocol, lets AI applications use external tools. Your IT team prepares the server and SAP access; you add the connection in the desktop.

Why connect Joule Work Desktop to SAP?

An email says that order processing failed. A spreadsheet lists the affected cases. The SAP system holds the error details. Bringing those pieces into one conversation gives the investigation a useful starting point.

Joule Work Desktop can work with local files, connected services and reusable workspaces called Spaces. SAP’s October Devtoberfest demo shows how a conversation becomes a Space with cards and follow-up questions alongside it.

ARC-1 adds the SAP evidence: short dumps, relevant code and changes. A short dump is the technical report SAP creates when a program fails, usually investigated in transaction ST22. You can ask JWD to explain that information in plain language, making it useful for consultants and support colleagues as well as developers.

Local file access still involves cloud processing: SAP documents that conversation context is sent to AI models through SAP AI Core. See the desktop’s data-handling guide.

Why I recommend ARC-1 as the SAP MCP server

ARC-1 brings several investigation tools into the same connection. You can ask it to retrieve a short dump, inspect the code involved and compare changes in a transport, SAP’s way of moving software changes between systems. The tool reference explains the available capabilities.

That combination matters when the first error message leaves questions open. The conversation can move from what failed to the code behind it, then produce an explanation someone else can check against the evidence.

Deploying ARC-1 centrally on BTP also gives your IT team one place to manage connections and tool permissions. SAP’s own authorization checks still apply.

Which SAP systems can you connect to?

ARC-1 documents connections for:

Available tools depend on the system’s release, configuration and your access. Your IT team prepares each connection.

Joule Work Desktop connects through ARC-1 on SAP BTP to SAP systems, with access managed by your IT team.

This uses the hosting pattern SAP describes as a custom MCP server on SAP BTP. Your organization is responsible for operating and securing the deployment. SAP also describes Integration Suite MCP Gateway for central governance of MCP access.

For the administrator’s view, see the ARC-1 deployment guide and my earlier ARC-1 on BTP article.

How to connect Joule Work Desktop to SAP with ARC-1

Ask your IT team for the deployed ARC-1 connector URL, the OAuth sign-in option and access to the SAP system you need. Once those are ready:

  1. Open Extensions, choose New, then Add Connector.
  2. Enter a name such as ARC-1 | S4 DEV and paste the supplied URL.
  3. If prompted, choose the OAuth option specified by your IT team. Select Add and complete the sign-in in your browser.
  4. Return to JWD, open a conversation and select the ARC-1 connector for that conversation.
  5. Ask for details of the connected SAP system to check access before starting your task.

A single-system ARC-1 deployment on BTP Cloud Foundry can use a URL like this documented example:

https://arc1-s4-dev.cfapps.us10.hana.ondemand.com/mcp

Use the complete address supplied by your IT team. The hostname, region and path depend on the deployment; /mcp is the path in this example.

Illustrated Joule Work Desktop Add Connector dialog with the name ARC-1 S4 DEV and an example SAP BTP Cloud Foundry URL.

OAuth handles sign-in through the browser, so you do not paste your SAP password into the conversation. SAP’s connector guide covers the desktop options. Your administrator can use the ARC-1 OAuth guide for configuration and troubleshooting.

Bring SAP findings into a Space

With the connection ready, attach the issue description and affected-case spreadsheet. A request like this gives JWD a concrete task:

Investigate this order-processing issue using ARC-1.
Check relevant SAP short dumps and the code involved. Do not make changes.
Create a Space with the reported issue, SAP findings and next steps.
Include sources and retrieval times.
Separate confirmed findings from possible explanations.

Spaces organize information into cards with a related conversation. You can ask follow-up questions or update the findings as the investigation progresses.

Illustrated Joule Work Desktop Space with example short-dump findings and an incident conversation.

What about new orders and changed products?

For order and product data, add an approved business connector using the appropriate SAP business APIs. ARC-1 supplies the ABAP investigation tools. Both can contribute to the same workflow, as described in the ARC-1 architecture guide.

Ask to refresh the Space when you need an update. Automatic notifications require a separate automation setup.

Start with one SAP system

My recommendation is to start with ARC-1 on a development system, with read-only permissions. Take one incident your team already understands and use the desktop to bring the issue description and SAP evidence together. That gives you a concrete way to assess the answers before expanding to more workflows.

Updated 18 October 2026. SAP’s desktop help still carries an Early Adopter Care notice; availability depends on your organization. The UI images are illustrations based on public SAP demos.

Useful references

Part of my AI ABAP development series. Also see ARC-1 with Joule Studio.