SAP launches ABAP MCP Server for agentic development in S/4

SAP has made its ABAP MCP Server generally available after Sapphire 2026, letting external agents such as Claude, Copilot and Amazon Q connect to S/4 via the Model Context Protocol through a single /mcp endpoint with bearer-token auth. The server exposes tools for reading tables, running RFCs, activating transports and ABAP Unit tests, plus resources and prompts. From mid-2026, agent calls are metered in AI Units.

• Server runs over HTTP/S with bearer tokens and a single /mcp endpoint
• Tools cover table reads, RFCs, transport activation, ABAP Unit and syntax checks
• Supported in Eclipse ADT and VS Code ADT, but object-type coverage differs
• From mid-2026 agent calls are billed in AI Units under RISE/GROW contracts