--- title: "SAP MCP server · Connect AI agents to SAP S/4HANA" description: "Connect inference.eu agents to SAP S/4HANA or ECC through an MCP server that exposes OData services via SAP BTP. Query and update business data with approvals." canonical: "https://inference.eu/connect/sap/" language: "en" --- MCP servers · ERP # SAP MCP server: connect AI agents to SAP S/4HANA from the EU SAP's own MCP servers help developers build Fiori, CAP and UI5 apps, but none of them gives an agent general access to business data in S/4HANA. For that, the most used option is the community SAP OData to MCP server for BTP, which turns your existing OData services into tools. inference.eu agents connect to it over HTTP with OAuth. [Contact sales](https://inference.eu/contact/)[What agents can do with it](#tools) 1. 01Authentication: OAuth 2. 02Community server 3. 03EU data centres ## What agents can do with it - 1 ### Service discovery A lightweight search lists the OData services and entities the connection can reach, such as business partners, sales orders or purchase orders, without loading every schema into the agent's context. - 2 ### Entity metadata For the entities the agent picks, a second tool returns the full schema: fields, keys, types and navigation properties, so the agent can build correct filters and payloads. - 3 ### Create, read, update and delete A third tool runs authenticated OData operations, from \`$filter\` and \`$top\` queries to POST, PATCH and DELETE requests, using the metadata from the previous step and the user's SAP authorisations. ## What SAP and this MCP server are 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. ## What agents can do with SAP 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. ## Setup and authentication 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. ## Data protection and where the data goes 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. ## Approvals and safe use 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. ## SAP S/4HANA Vendor SAP SE Vendor based in Germany Category ERP Authentication OAuth Transport Local or remote Server [Community server](https://github.com/lemaiwo/btp-sap-odata-to-mcp-server) Documentation [github.com](https://github.com/marianfoo/sap-ai-mcp-servers) ## SAP S/4HANA: common questions The questions buyers, developers and legal teams ask us most. Something missing? Ask us directly. SAP publishes several MCP servers for developers, including CAP, SAP Fiori, UI5 and ABAP tooling. As of November 2026 there is no official SAP server that gives agents general access to S/4HANA business data. Community servers such as this OData bridge fill that gap. An open-source server that runs on SAP BTP and exposes the OData services of an S/4HANA or ECC system as MCP tools. It uses three steps: discover services, load metadata for chosen entities, then run create, read, update or delete operations. Yes. The server works with any system whose OData services are reachable through a BTP destination, which includes S/4HANA and ECC with SAP Gateway. What the agent can do depends on which services are active and on the user's authorisations. Through OAuth against the server's XSUAA instance on BTP. You add the connector, enter the endpoint and sign in. The token is stored encrypted in the EU. Behind the server, BTP destinations reach SAP using principal propagation or OAuth 2.0. Yes, if the OData services and the user's roles allow it. The server supports POST, PATCH and DELETE. We recommend requiring a person's approval in inference.eu for every write, and limiting exposed services to what the workflow needs. The server runs in your SAP BTP account and talks to your SAP system there, so data stays in SAP infrastructure you already use. Results then reach the agent, whose model runs in EU data centres on inference.eu. Many. Community lists such as marianfoo/sap-ai-mcp-servers track ABAP and ADT servers, OData bridges in Go and Python, Datasphere and HANA servers, and commercial gateways. Pick based on whether you need development tooling or access to business data. For this server, yes. It relies on the BTP destination, connectivity and XSUAA services. Teams without BTP can look at OData bridges that run elsewhere, but they then handle SAP credentials and connectivity themselves. [Ask a question](https://inference.eu/contact/) ## Related [All MCP servers](https://inference.eu/connect/#directory) - [DATEVConnect inference.eu agents to DATEV through an MCP server. Read postings, clients and documents, and prepare uncommitted booking batches for review.Accounting](https://inference.eu/connect/datev/) - [SalesforceConnect inference.eu agents to Salesforce Hosted MCP Servers to query and update records with each user's own permissions, sharing rules and field security.CRM and sales](https://inference.eu/connect/salesforce/) - [OdooConnect inference.eu agents to the MCP server built into Odoo AI. Search and group records across apps, and create or update records you expose as tools.ERP](https://inference.eu/connect/odoo/) - [n8nConnect inference.eu agents to n8n's built-in MCP server to search and run the workflows you expose, and build workflows and data tables, with approvals.Automation](https://inference.eu/connect/n8n/) ## Move your AI workloads to EU infrastructure Tell us which models you use and roughly how much traffic you have. We reply within one working day with pricing and next steps. - Reply within one working day - Pricing for your volume - DPA ready to sign