ABAP Model Context Protocol Server SDK

What is ABAP Model Context Protocol Server SDK?

An ABAP implementation of the Model Context Protocol (MCP), supporting protocol versions up to 2025-11-25. It is a server-only SDK — SSE streaming, which is mandatory for the client, is not supported. This SDK is intended for ABAP developers building MCP servers with capabilities like prompts, resources, tools, and tasks.

How to use ABAP Model Context Protocol Server SDK?

Refer to the Overview in the docs folder for installation and configuration details. The SDK integrates ABAP open-source projects including ajson, abaplint, and abapGit.

Key features of ABAP Model Context Protocol Server SDK

• Supports protocol versions 2025-03-26, 2025-06-18, and 2025-11-25
• Implements Prompts, Resources, Tools, Tasks, and Completions
• DDIC-based schema generation plus a JSON schema builder and validator
• Task-augmented tool execution with optional output schemas
• No SSE — no notifications, listChanged, subscribe, or logging
• Authorization relies on ABAP features; OAuth possible in newer S/4HANA

Use cases of ABAP Model Context Protocol Server SDK

• Building MCP server functionality directly within an ABAP system
• Long-running background work with client polling via Tasks
• Autocomplete for prompt and resource-template arguments
• Generating and validating JSON schemas from ABAP DDIC definitions

FAQ from ABAP Model Context Protocol Server SDK

What protocol versions are supported?

Supported versions: 2025-03-26, 2025-06-18, and 2025-11-25. Older versions may be dropped over time.

Does the SDK support SSE for client connections?

No. SSE streaming is required for the client side, and the maintainer sees no realistic way to implement it in ABAP. Only the server side is provided.

What ABAP open-source projects does it depend on?

It integrates ajson, abaplint, and abapGit. More related projects are listed at dotabap.org.

How is authorization handled?

Standard MCP authorization via custom code is not feasible in ABAP. The server relies on ABAP-native features; an overview of options is in the Authentication documentation.

Is client support planned?

No. The README states there is no realistic way to support SSE streaming, which is mandatory for an MCP client.