CapabilityProtocols & APIsStandard ABAP, read from its artifacts

Serve your application over MCP

Here the question is whether the system can be the server rather than the thing being read. abap-ai/mcp implements the protocol in ABAP itself — prompts, resources, tools, long-running tasks and DDIC-derived schemas — installed with abapGit(artifact:abapgit-abapgit) and running inside the system, so what an agent sees is what you chose to expose rather than whatever ADT happens to reach.

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

Overview

SAP SHIPS

No SAP artifact is confirmed here for Standard ABAP.

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

THE COMMUNITY ADDS

abap-ai/mcp

Lets an ABAP system be the MCP server rather than the thing being read — prompts, resources, tools, tasks and completions implemented in ABAP and installed with abapGit.

Sourceabap-ai/mcp — READMEchecked 2026-09-10

abap-ai/mcp2

Lets an ABAP system be the MCP server rather than the thing read from outside: the tool catalog, resources, prompts, completions, elicitation and the tasks extension are ABAP classes behind one stateless ICF endpoint, served to both the legacy protocol versions and the 2026-07-28 draft.

Sourceabap-ai/mcp2 — READMEchecked 2026-10-21

abap-agent-runtime

Skybuffer AI MCP server

Makes the ABAP system itself the MCP server, behind an ICF node: a table, view or CDS view entered in /SKYBFR/YAICDSNM becomes a tool without code, and a custom tool is an ABAP class implementing /SKYBFR/IF_YAI_OPERATION and /SKYBFR/IF_YAI_SCHEMA, registered by name and class in /SKYBFR/YAICMCPN and listed to clients through tools/list.

SourceMCP Server Configuration in ABAP System – Documentationchecked 2026-10-22

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

Policy1

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2AlwaysAn MCP server exposes an SAP API, or 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 →

Sources

SourceSAP API Policy v.4.2026achecked 2026-09-16