SAP MCP server: connect AI agents to SAP S/4HANA from the EU

SAP SE, based in Walldorf, Germany, makes the S/4HANA and ECC ERP systems that run finance, procurement, sales and logistics in many large European companies. SAP publishes MCP servers for development work, such as @cap-js/mcp-server and the SAP Fiori MCP server, but not a general server for business data.

The open-source SAP OData to MCP server for BTP fills that gap. It runs on SAP Business Technology Platform, uses BTP destinations to reach S/4HANA or ECC, and exposes all OData services through three progressive discovery tools. It supports Streamable HTTP and stdio.

A buyer can ask which purchase orders for a supplier are still open this week, and the agent translates that into a filtered OData query. A sales assistant can look up a customer's credit status and recent orders before a call, or summarise delivery delays by plant.

With write access, an agent can prepare changes that people usually type by hand, such as updating a business partner's address after an email, or creating a sales order draft from a structured customer request, each confirmed by a person first.

Your SAP team deploys the server to a BTP Cloud Foundry space and configures a destination to the S/4HANA or ECC system, with principal propagation or OAuth 2.0. Access to the MCP endpoint itself is protected by XSUAA.

On inference.eu, add the SAP connector to an agent, enter the server's HTTP endpoint and sign in through OAuth. The token is stored encrypted in the EU and only reaches the agents you allow. With principal propagation, each request runs with the signed-in user's SAP authorisations.

The server runs in your own SAP BTP account, and requests go from there to your SAP system through the destination and connectivity services. Data therefore stays within SAP infrastructure you already contract for, in the BTP region you chose.

On inference.eu, the model that reads the OData results runs in EU data centres, and connection credentials are stored encrypted in the EU. ERP data often includes personal data of customers, suppliers and employees, so align the exposed services with your data protection team.

Expose only the OData services the agent needs, and give the technical or propagated users the narrowest SAP roles that work. Reading is low risk; PATCH, POST and DELETE change live business data and should be treated as such.

On inference.eu you can require a person to approve every write call before it runs, and leave read queries automatic. Combine this with SAP's own change documents and authorisation checks, so each change is traceable to a user and limited to what that user may do in SAP.