MCP for SAP
SAP reports as a question rather than a ticket
In most companies, the answer to an SAP question is not a report but a waiting period. The business department describes what it wants to know, IT builds a report, and two weeks later the question has changed. An MCP server shortens this loop to one sentence in the chat.
The connection
Access runs via the routes your SAP already offers: OData services via the SAP Gateway, and where needed RFC or BAPI for functions without an OData counterpart. For S/4HANA, many reporting scenarios are already available as standard OData services, which reduces the effort considerably.
We do not build Z tables or a parallel world. If a requirement can only be met through new development in SAP, we say so instead of rebuilding it in the MCP server.
Authorisations remain SAP authorisations
The authorisation system in SAP has grown over years and, in many organisations, represents the actual substance of compliance. An MCP server that works with a single service user undermines precisely that.
We therefore map the requesting user to their SAP user. A question only returns what this user would also be allowed to see via the regular user interface, including authorisation objects, plants, company codes and clients. Access that SAP denies remains denied in the chat.
Typical uses
- Controlling
- Variances against plan, contribution margins, development of individual cost centres over several periods, without building a new report for every variant.
- Purchasing
- Price development per supplier, open purchase orders, delivery reliability as a question rather than a report run.
- Sales
- Order situation, margins per customer and item, follow-up questions during the conversation rather than afterwards.
- Maintenance
- Notifications and orders in connection with equipment data — the bridge to the production side, which we also connect.
Limits we state up front
- No write access to SAP in the standard scope. Postings and document changes stay in SAP.
- No circumvention of the authorisation system through a collective user.
- No data replication into an external analytics database.
- No commitments regarding modules whose interfaces we have not checked.
Frequently asked questions
Does this work with S/4HANA and with SAP ECC?
With both. With S/4HANA, a large proportion of the required OData services is already available as standard. With ECC, activation or an additional service is more often necessary. We clarify the specific scope with your SAP team in the feasibility phase.
How do you prevent someone from seeing figures they are not allowed to see?
The MCP server maps the requesting user to their SAP user and calls SAP in that user's context. This means the existing authorisation objects, company codes and plant assignments apply unchanged. What SAP denies, the chat denies too.
Can the AI post in SAP?
Not in the standard scope. We only deliver read-only servers. Write functions are technically possible, but require an approval chain, an allowlist of permitted transactions and complete logging, and that is a separate project with its own risk assessment.
How quickly does the system respond?
A typical query takes a few seconds, determined by the response time of the OData service, not by the language model. In the server design, we deliberately limit reports over very long periods so that no query puts load on your production system.
Let’s check whether it holds up for your systems.
The feasibility study takes one to two weeks and ends with a document you can keep working with even without us. If an interface cannot meet your requirement, it says so.
Request a first call