Claude through MCP vs SAP Joule on ECC, 2026
Updated 2026-10-19 · ITERACTIVE
This comparison is current as of 19 October 2026. If your company runs SAP ECC 6.0 and wants an AI assistant over its data before a move to S/4HANA, SAP's own assistant is Joule, and SAP's public statements from May 2026 give ECC customers selected Joule scenarios in return for a cloud commitment. The other route is a Claude layer connected to ECC through MCP, the open Model Context Protocol: a custom integration beside ECC that needs no conversion and keeps the model under your own EU cloud account, with no production ECC reference yet. Other routes exist, from SAP BTP extensions to Microsoft Copilot Studio over SAP connectors, and the end of this page says when they fit. The comparison below uses SAP's published statements, linked under Sources at the end, and marks what still has to be confirmed for your contract.
The two routes in one table
| Question | SAP Joule on ECC | Claude through MCP on ECC |
|---|---|---|
| Runs on ECC 6.0 today? | Selected scenarios from Q3 2026 for customers with the cloud commitment, per SAP's May 2026 statements; the exact scenarios, product and prerequisites are in SAP's documentation and your contract | On the ECC 6.0 IDES and S/4HANA 2025 sandboxes we tested, yes; on your system it depends on the Gateway services, function modules, patches, roles and network path, which the readiness check lists |
| What SAP asks for | A commitment to move the majority of the landscape to SAP Cloud ERP (SAP News, 12 May 2026); SAP's chief strategy officer put it as half of the maintenance spend to the cloud first (CIO.com, 13 May 2026); confirm the terms for your contract | A scoped SAP technical account, the interface list, and SAP's contractual answer on named-user, indirect-access and Digital Access terms |
| Where the model runs | SAP's cloud; region and hyperscaler depend on the product and contract | Under your own cloud account on Amazon Bedrock in the Frankfurt region or Google Vertex AI in the EU; retention, logging and cross-region inference depend on the endpoint you configure and are documented per component |
| Scope on ECC | Selected SAP scenarios inside SAP products | The tables, services and allowlisted BAPIs the technical account may read; Microsoft 365 and other systems through separate MCP connectors |
| Writes to SAP | Agents inside SAP products | None in the published server; in a pilot, allowlisted BAPIs with a person's confirmation, recorded in the audit log; not an SAP workflow approval |
| User identity | SAP user | A scoped technical account in the pilot, so the user's own SAP roles and segregation-of-duties rules do not apply; named-user propagation is on the roadmap |
| Audit trail | SAP's own logging per product | One JSON line per call, forwarded to your SIEM; the local file is not tamper-proof and records the technical account |
| Vendor lock-in | SAP | Open protocol; the server is open source under MIT; a model switch is possible and means re-testing the tools and the confirmation step |
| Cost | Depends on product, edition and scenario; SAP sells premium AI capabilities through AI units; ask SAP for a quote | Model usage billed by your cloud account, plus a fixed-price pilot, plus your own cost for security review, network work and licensing clarification |
| Time to first result | Depends on your commitment and on which scenarios SAP releases for ECC; ask SAP for dates | Six weeks for two processes once procurement, security approval, network access and the licensing questions are done |
What SAP said in May 2026
At Sapphire on 12 May 2026 SAP said that customers on ECC and on-premise S/4HANA are not excluded from Joule, provided they commit to transitioning the majority of their current landscape to SAP Cloud ERP, and that they receive selected AI scenarios. A day later SAP's chief strategy officer told CIO.com that customers should commit half of their maintenance spending to the cloud first, because Joule assistants and agents are designed for the cloud. Reporting at the time said general availability for ECC had moved to the third quarter of 2026. These are public statements and press reporting; the entitlement that applies to a given customer is in that customer's contract.
The same week SAP and Anthropic announced an expanded partnership under which Claude becomes a primary reasoning and agentic capability behind Joule and Joule agents on the SAP Business AI Platform. As of 19 October 2026 SAP had published no availability date, price or hosting region for Claude inside its platform for ECC customers.
In the DSAG Investitionsreport 2026, published in February 2026, 54 percent of the German-speaking member companies surveyed still run ECC somewhere, and 77 percent of the AI use cases they run are on non-SAP solutions. For SAP ERP 6.0 enhancement packages 6 to 8, mainstream maintenance ends on 31 December 2027 and optional extended maintenance runs to the end of 2030 at a two-percentage-point surcharge; the dates for other Business Suite components and older enhancement packages differ.
What the MCP route is, concretely
MCP is the open protocol through which Claude and other AI clients call tools. An MCP server over SAP sits inside your network, next to the system, and uses OData on the Gateway and RFC on the application server. Claude never talks to SAP directly: it asks the server for a tool, the server checks whether the tool is allowed for that user, runs it with a scoped SAP account, writes the audit line and returns the result.
- The server we deploy is open source under MIT: OData and RFC/BAPI tools, an allowlist of read BAPIs, a denylist for tables with credentials or personal data, and a JSON audit line for every call. The RFC bridge is built on open-rfc, an independent implementation of the RFC protocol that SAP does not support and that gets its own security review before a pilot; where your Basis team requires SAP's stack, it runs on the SAP NetWeaver RFC SDK with PyRFC instead, and SAP supports the SDK, not PyRFC or this server.
- The published server is read-only. In a pilot a write is enabled per BAPI after your IT team approves it, and runs only after a named person confirms the proposal.
- Sign-in runs through the Microsoft or Google accounts people already have; personal identifiers are masked in the server before the model sees them. The pilot uses a scoped SAP technical account, so the person's own SAP roles do not apply and the account is limited to data every pilot user may see; named-user propagation is on the roadmap.
- It has been run against SAP ECC 6.0 and S/4HANA 2025 sandbox systems. There is no production ECC reference yet; the first ECC pilot is in preparation for the fourth quarter of 2026. The setup guide on this site takes you from clone to the first table read in about 20 minutes.
Licensing: the question your SAP account team will ask
SAP's Digital Access model covers specified document types that third-party applications create in SAP, so it applies to writes. Reads do not create such documents, but named-user and indirect-access terms in your contract can apply to an application that reads on behalf of many people, whatever account it uses. A technical account does not settle this. For a pilot we list every interface, table, BAPI and document type the server touches and ask SAP for a contractual answer before production; an account manager's e-mail is not that. Neither route is free of licensing questions.
When Joule, BTP or Copilot is the better answer
If you are already moving to S/4HANA Cloud under RISE in 2026 or 2027, Joule is part of that product set, with the scope and AI-unit consumption your contract defines, and custom Joule skills on SAP BTP extend it inside SAP products. If your company has standardised on Microsoft and the use cases are documents and email with SAP as a secondary source, Copilot Studio with Azure OpenAI over SAP connectors is a shorter path. If you already run an integration platform in front of ECC, an assistant on top of it reuses what you have. The MCP route then covers the cross-system work in one conversation and can run beside Joule.
When the MCP route is the better answer
- You stay on ECC until 2027 or 2030 and will not sign a cloud commitment this year.
- Your data policy requires the model to run in your own EU cloud account, under provider terms your security team has reviewed.
- The assistant has to reach Outlook, Teams, SharePoint and SAP in one conversation.
- You want to own the layer, the allowlists and the audit trail, and to be able to switch the model later.
What a six-week pilot looks like
Week one is assessment: which two processes, which tables and BAPIs, which roles, which hosting, and the licensing questions for your SAP account team. Weeks two and three put the MCP server into your network and connect it to Claude with sign-in and audit. Weeks four and five run the two processes with the people who own them, measured against the manual baseline. Week six is the audit review and a go or no-go for the next processes. The pilot has a fixed price, stated in the first conversation together with what it covers.
Questions we get asked
Can Joule run on ECC without RISE?
Not according to SAP's public statements from May 2026, which tie Joule for ECC to a commitment to move the majority of the landscape to SAP Cloud ERP, with availability for ECC reported for the third quarter of 2026 and selected scenarios only. Your contract and your SAP account team have the answer for your case.
Is a technical SAP account enough for licensing?
No. Digital Access covers specified document types an application creates in SAP, and named-user or indirect-access terms in your contract can cover reads made on behalf of people through an application. The pilot proposal lists every interface and document type the server touches so SAP can confirm the position contractually before production.
Does the MCP route change the ECC core?
No modification of the SAP core. It reads through OData services and remote-enabled function modules, with RFC_READ_TABLE for ad-hoc reads in a sandbox. Activating Gateway services, adding Z services or roles for production can need customizing and transports, which the pilot lists; the release status of each interface is checked with your Basis team.
Will the MCP route block a later move to S/4HANA?
No. The layer sits beside SAP. After a migration the tools are re-pointed at the new system's interfaces and re-validated against its data model; the audit history stays, and the prompts and processes are re-tested.
Where does the data go?
To the model under your own cloud account, on Amazon Bedrock in the Frankfurt region or Google Vertex AI in the EU. Retention, logging, cross-region inference and training terms depend on the provider, region, model and endpoint; the configuration is documented per component before go-live. Personal identifiers are masked in the server before the call.
Is Claude inside Joule the same as Claude through MCP?
No. SAP announced Claude as a primary reasoning capability behind Joule on its platform, without a published date, price or hosting region for ECC customers as of 19 October 2026. The MCP route is your own Claude under your own account, independent of SAP's roadmap.
What does the pilot cost?
A fixed price for six weeks and two processes, stated in the first conversation together with what it covers. The first conversation is 30 minutes and free.
Is your ECC ready for Claude?
A 30-minute technical readiness check: which interfaces your ECC exposes, which roles a pilot needs, where the model would run, the licensing questions for your SAP account team, and a two-page summary you can forward. Sandbox demo on request.
Request the ECC readiness check
Or write to us directly: info@iteractive.ai · +421 905 452 325