CGR MCP Server for SAP
AI agents that
work in SAP.
Ask SAP a question in plain language and get the answer from live SAP data. Hand your AI assistant an SAP task and it runs it, under your own SAP user and authorizations. On SAP ECC 6 and S/4HANA, with no BTP and no middleware.
Where is sales order 19205? Has it shipped, and has it been invoiced?
Order 19205 for Smith Inc. is complete: shipped and invoiced for $7,401.00.
Read as your SAP user · whitelisted objects only · logged in SAP
From CGR’s SAP ECC 6 demo system.
The SAP add-on underneath runs in production at
What agents do
Three kinds of SAP work, in plain language
Users ask in business terms. They never need to know a table, a BAPI or a transaction code.
Ask
Answers from live SAP data: tables, views, CDS views, ALV reports and queries. The agent filters at the source and reads only what it needs.
Act
Create, change and post SAP documents through standard BAPIs and function modules: purchase orders, sales orders, goods movements, invoices. Test run first where SAP offers one, read back after.
Understand
When SAP rejects something, the agent reads SAP’s own message, explains it in plain language and corrects the input. Nothing is half-posted.
How it works
Your AI assistant, connected to SAP through one governed path
- 1UserSingle sign-on with your company account
- 2AI assistantAny MCP-capable client you already license
- 3CGR MCP ServerIn your cloud, or hosted on CGR’s Azure
- 4CGR SAP ConnectorNative ABAP add-on inside SAP
- 5SAP ECC / S/4HANATables, reports, BAPIs, Z-objects
Every call reaches SAP as the asking user’s own SAP user, inside their SAP authorizations and a whitelist IT sets per role, and every call is logged.
Why it is different
Inside SAP, not beside it
No new platform
A native ABAP add-on in the /CGR/ namespace does the work inside SAP. No BTP, no Integration Suite, no middleware to buy or run.
Runs on ECC 6
Any ECC 6 release and any S/4HANA release, on-premise, in private cloud or with RISE. You don’t have to migrate to get AI in SAP.
Reaches your custom logic
BAPIs, function modules, reports and Z-objects, including function modules that are not RFC-enabled. Nothing has to be wrapped or re-coded.
Priced for adoption
Flat per SAP production system, with unlimited users and calls. You never pay per user, per question or per record.
A real session
From customer order to posted invoice in one conversation
A session in CGR’s SAP ECC 6 demo system. The user never named a table or a BAPI.
Shortened for the page. Each step ran through standard SAP BAPIs and function modules on IT’s approved list, under a dedicated demo user.
- 1
Create a sales order for Smith Inc.: one P-103 pump and one P-104 pump, delivery today.
Sales order 19205 created and priced at $7,401.00.
- 2
Create the delivery, pack it and post goods issue.
Delivery 80018926, packed on two pallets, goods issue posted.
- 3
Put it on a truck and invoice it.
Shipment 1458 completed; invoice 90040440 posted to accounting.
- 4
Show me everything we created.
The full document flow, each document read back from SAP, and the order’s gross margin: 65.4%.
Governance
IT decides what the agent can touch
Single sign-on
Users sign in with their company accounts through your identity provider.
Named SAP users
Each person maps to one SAP user. Never a shared account.
Two gates on every call
A whitelist per role, inside the user’s own SAP authorizations.
Read and write apart
A role can be read-only; writes need an explicit commit.
Full audit
Every call logged in SAP with user, object, time and the full request and response.
Getting started
From first look to production in weeks
Step 1 · 30 minutes
Live demo
An agent answers, acts and recovers from an SAP error in a real SAP system, including a request it is refused.
Step 2 · 4 weeks
Pilot
5–10 named users, read-only, on the questions they already ask SAP every week.
$8,000 fixed, credited in full against the licence
Step 3 · Week 4
Review
Measured against targets agreed up front for adoption, accuracy, speed and security. Go, extend or stop.
CGR SAP Connector
Need applications, not assistants, talking to SAP?
The same add-on that powers the MCP server gives your storefronts, asset systems and BI tools direct REST and OData APIs into SAP, with no middleware. Install in hours, first working integration in days.
Partners
Bring AI to your SAP clients
Agencies, consultancies and software vendors resell or refer CGR with a published margin. Your clients get AI in SAP; you keep the client relationship.
What is MCP?
The Model Context Protocol is the open standard AI assistants use to connect to business systems. CGR’s MCP server gives your assistant governed tools for SAP.
Does the AI see all of our SAP data?
No. It sees only the objects IT has added to the whitelist for the user’s role, and only what that user’s own SAP authorizations allow. Row limits stop any single request from pulling bulk data.
Do we need SAP BTP or S/4HANA?
No. It runs on any SAP ECC 6 release and any S/4HANA release, on-premise, in private cloud or with RISE. No BTP, Integration Suite or middleware is needed.
Where does our SAP data go?
From SAP to the MCP server, in your own cloud or CGR’s hosted Azure, and then to your AI assistant. Your AI provider handles questions and answers under your own agreement with it.
Which AI assistants work with it?
Any MCP-capable assistant your company already licenses.
Tell us the SAP task you’d hand to an AI agent first.
We’ll show it running in a live SAP system in 30 minutes, then help you pilot it in yours.