Product
CGR MCP Server
for SAP
Connect any MCP-capable AI assistant to SAP ECC 6 and S/4HANA. Users ask in plain language; the agent reads, reports and posts in SAP under their own SAP user, using only the objects IT has approved.
cgr_get_whitelisted_objectsWhat this user may use, and nothing morecgr_get_object_metadataFields, parameters and defaults, read before each callcgr_read_tableTables, views and CDS views, filtered and pagedcgr_run_reportALV reports with variants, and ABAP queriescgr_call_functionBAPIs and function modules, with explicit commitRead-only variants of the report and function tools are used for read-only roles.
What it is
A governed path from your AI assistant into SAP
MCP, the Model Context Protocol, is the open standard AI assistants use to reach business systems. CGR MCP Server for SAP is an MCP server built on CGR SAP Connector, a native ABAP add-on already running in production at manufacturing companies.
The connector does the work inside SAP. The MCP server makes it available to your AI assistant. Users never need to know a table, BAPI or function module.
- UserSingle sign-on
- AI assistantAny MCP client
- CGR MCP ServerYour cloud or CGR’s Azure
- CGR SAP ConnectorABAP add-on in SAP
- SAP ECC / S/4HANAAny approved SAP object
What it can reach
Standard and custom SAP objects, with no RFC enablement
No RFC enablement needed
Most SAP integration tools can only call function modules flagged as remote-enabled. The connector runs inside SAP and calls every object locally, so internal and custom Z-objects are used as they are. Nothing has to be changed, wrapped or re-coded.
| Object type | What the agent gets |
|---|---|
| Tables | Any approved table, standard or Z, filtered and paged at the source |
| Views | Database and maintenance views, joined as SAP defines them |
| CDS views | Curated, business-shaped data sets |
| ALV reports | Standard and custom reports, with saved variants, returned as data |
| ABAP queries | Existing query definitions, used as they are |
| BAPIs | SAP’s standard interfaces to read, create, change and post |
| Function modules | Standard and custom, including those not RFC-enabled |
Where it runs
In your cloud, or hosted by us
In your own cloud
Installed in your Azure, AWS or other cloud tenant, under your network, firewall and security policies.
- SAP data never leaves infrastructure you control on its way to your assistant
- Your IT team owns access and monitoring; CGR supports the setup
Hosted by CGR Software
Run for you on CGR Software’s Microsoft Azure servers, as a managed service, for $6,000 a year.
- Fastest start, nothing to install or operate
- CGR handles updates, monitoring and availability
Your Basis team installs the connector via SAINT; whitelists and roles live in SAP.
SAP is never opened to the assistant directly, only to the connector’s secured endpoints.
All traffic between assistant, MCP server and SAP runs over HTTPS.
Hosting never limits which AI assistant your users work in.
How it compares
No BTP. No CPI. No coding.
| Feature | CGR MCP Server for SAP | SAP’s cloud AI route | Open-source SAP MCP servers |
|---|---|---|---|
| Runs on ECC 6 | Yes, any ECC 6 and S/4HANA release | Focused on SAP cloud solutions and S/4HANA | Usually, via RFC |
| Platform needed | None beyond SAP | SAP BTP subscription and services | Self-hosted server plus the SAP NW RFC SDK |
| Non-RFC function modules | Yes | Through published APIs | No |
| Views, CDS views, reports, queries | Yes | Through published APIs | Limited |
| Setup | Install the add-on, approve objects by name | BTP configuration and integration content | Development and maintenance by your team |
| Governance | SSO, named users, whitelist per role, full audit | Within SAP’s cloud services | Whatever your team builds |
| Pricing | Flat per production system, unlimited users and calls | Subscription and consumption based | Free software, your own effort |
Comparison reflects typical setups as of November 2026; individual offerings vary.
What you need
Three things, most of which you already have
- 1CGR SAP Connector in your SAP system, installed by your Basis team via SAINT.
- 2A home for the MCP server: your cloud, or CGR’s hosted service.
- 3Your identity provider for single sign-on, and an MCP-capable AI assistant your company already licenses.
Pricing
One flat price per SAP production system
$36,000 a year for your first production system, including CGR SAP Connector. Unlimited users and unlimited calls. DEV, QA and sandbox systems are included. You are never charged per user, per question or per record, so adoption is never capped by the budget.
See it work in a real SAP system
In 30 minutes an agent answers, acts and recovers from an SAP error, and you see a request it is refused.