Build MCP servers on SAP ABAP for enterprise integration

SAP ABAP MCP Server SDK is an ABAP implementation of the Model Context Protocol, supporting protocol versions 2025-03-26, 2025-06-18, and 2025-11-25. It is a server-only SDK - the maintainer notes there is currently no realistic way to support the SSE streaming that MCP clients require, so this SDK does not attempt a client implementation. It is built on ABAP open-source tooling: ajson (bundled as zmcp_ajson) for JSON handling, abaplint for code review and a 7.02 downport, and abapGit for source control.

Use this SDK to expose ABAP-side prompts, resources, and tools to MCP clients when SSE-dependent features aren't required - it implements Tasks (long-running background work with client polling), Completions (autocomplete for prompt and resource-template arguments), and DDIC-based JSON schema generation with a validator. This exact SDK version is frozen except for error corrections and only targets protocol versions up to 2025-11-25; projects needing 2026-07-28 or later protocol support should look at the newer ABAP MCP SDK V2 instead, which the same maintainer built specifically because the session-support changes across newer protocol versions made supporting them all in one SDK impractical - V2 supports older MCP versions back to 2025-03-26 on a best-effort basis as long as sessions aren't required. It is also not a fit if standard MCP OAuth-based authorization is a hard requirement: implementing the MCP Authorization spec via custom ABAP code isn't considered feasible, so authorization has to lean on ABAP's own features, and OAuth itself is described as challenging to use outside newer S/4HANA releases.

• Prompts, Resources, and Tools, including optional output schemas and task-augmented tool execution.
• Tasks: long-running background work that clients poll for completion.
• Completions: autocomplete support for prompt and resource-template arguments.
• DDIC-based schema generation, plus a JSON schema builder and validator.
• Explicitly not implemented: Sampling (open to future requests via an issue), Elicitation (no feasible path without SSE), Roots (considered largely irrelevant for ABAP), and the SSE-dependent notification types - Cancellation, Progress, Logging, listChanged, and subscribe.
• Roadmap: longer term, the maintainer intends to add features for building modular MCP servers out of reusable implementations; near-term plans are tracked as open GitHub issues.

ABAP and SAP developers who want to expose SAP-side prompts, resources, and tools to MCP clients without needing SSE-dependent protocol features, and who are prepared to handle authentication through ABAP's own mechanisms rather than a full OAuth-based MCP authorization flow. Community discussion happens on the project's Discord, shared across the abap-ai organization's repos. Worth noting: part of the implementation and most of the detailed documentation were generated with AI (Claude Sonnet 3.7/4, GitHub Copilot) and only reviewed at a high level.