Serve your application over MCP
Here the question is whether the system can be the server rather than the thing being read. abap-ai/mcpabap-ai/mcpAn MCP server SDK written in ABAP to run natively on the ABAP stack, so an ABAP system can expose its own prompts, resources and tools to an agent from inside itself.independent, abap implements the protocol in ABAP itself — prompts, resources, tools, long-running tasks and DDIC-derived schemas — installed with abapGitabapGitmaintains 1 entrycommunity org(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 ABAP Cloud applicability. View All ABAP
Overview
No core answer is documented.
SAP's own ABAP MCP Server, generally available from Q2 2026, answers the other direction of this concern: it runs inside ABAP Development Tools for VS Code and lets an agent perform ABAP development tasks against the system, which is 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 rather than the system serving its own business tools. abap-ai/mcpabap-ai/mcpAn MCP server SDK written in ABAP to run natively on the ABAP stack, so an ABAP system can expose its own prompts, resources and tools to an agent from inside itself.independent, abap names SAP NetWeaver 7.52 as its requirement, a classic-ABAP version number, and SAP_MCPMarkWuRY168/SAP_MCPPublishes SAP system functions as MCP tools from configuration tables held inside the SAP system, so adding a tool is a configuration change rather than a code change.independent, abap says nothing about which development model it needs.
No artifact is documented here yet.
Policy
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
Artifacts
Details
Coverage
Designs that place it
For your agent
- Ref
capability:mcp-servers- JSON
- /capabilities/mcp-servers.json
- MCP
- Connecting an agent