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 MCPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design 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 codeAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed.
Overview
No core answer is documented.
Not covered: At reading a developer's own running instance. The door's one provider, hybris-mcp-litehybris-mcp-liteA read-only MCP server that answers questions about a local SAP Commerce Cloud instance by calling HAC, so types, beans, configuration, cronjobs, logs and FlexibleSearch come back in the editor.independent, commerce, exposes a read-only slice of HAC and states local and development instances only, so what an agent reaches here is what HAC will answer about the system in front of the developer — nothing that writes, and nothing a deployed storefront serves to an agent of its own.
One provider and it is independent, so community-only is a assessment of the corpus. No SAP-published provider of this capability is behind this door in the corpus, which may be absence of evidence rather than evidence of absence; the product itself is SAP Commerce CloudSAP Commerce CloudSAP's commerce platform, once Hybris: a Java platform extended with extensions, ImpEx and its type system, run by SAP as SAP Commerce Cloud, with the composable storefront in front of it. The product behind the SAP Commerce door: what is entered there is the tooling that reaches into or builds on an instance, and the product itself is not an option., an external, and never an artifact here.
Policy
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 →Artifacts
Details
Coverage
For your agent
- Ref
capability:agent-systems-access- JSON
- /capabilities/agent-systems-access.json
- MCP
- Connecting an agent