Agent access to your systems

Giving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. Serving your application over MCP exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to agent access to your code.

Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP

Overview

SAP SHIPS

No SAP artifact is confirmed here for ABAP Cloud.

A ABAP Cloud coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

No community artifact is confirmed here for ABAP Cloud.

A ABAP Cloud coverage assessment has not been written. View all flavors

Policy1

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2AlwaysAn MCP server uses SAP APIs to supply tools, resources or data to an agent.
  • § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
  • § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.

MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.

SAP API Policy 4.2026a →
SourceSAP API Policy v.4.2026achecked

Artifacts4

4 of 4 artifacts
ArtifactSignals
MCP servers4
btp-sap-odata-to-mcp-serverExposes S/4HANA or ECC OData services as MCP tools
Signals
Functional boundary
midasol/sap-mcp-serverPython MCP server for SAP Gateway OData operations
Signals
none
odata_mcpPython bridge generating MCP tools from OData v2 metadata
Signals
Functional boundary
odata_mcp_goGo binary bridging any OData v2 or v4 service to MCP
Signals
Functional boundary

Details

Coverage
statenot assessed, ABAP, ABAP Cloud
For your agent
Ref
capability:agent-systems-access
JSON
/capabilities/agent-systems-access.json
MCP
Connecting an agent