ABAP Model Context Protocol Server SDK
About
ABAP MCP - Model Context Protocol - Server SDK
Details
- Author
- abap-ai
- GitHub stars
- 75
- Downloads
- 373
- Categories
- Developer Tools
Jump to
- 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
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.
ABAP Model Context Protocol Server SDK
Discord - for all ABAP-AI repos.
Overview
ABAP implementation of the Model Context Protocol, supporting up to version 2025-11-25. \
Note that this is only a server implementation as I currently see no realistic way to support SSE streaming which is mandatory for the client.
Supported protocol versions: 2025-03-26, 2025-06-18, 2025-11-25
Note that old protocol versions might be dropped after a while especially if they increase maintenance effort.
Documentation
See Overview in docs folder.
Used ABAP OpenSource projects
Special thanks to:
- ajson integrated as zmcp_ajson
- abaplint for review and more important 7.02 downport
- abapGit for source code control
Find more awesome projects at dotabap.
Features & Limitations
Currently implemented:
- Prompts
- Resources
- Tools (incl. optional output schemas and task-augmented execution)
- Tasks - long-running background work with client polling
- Completions - autocomplete for prompt and resource-template arguments
- DDIC-based schema generation plus a JSON schema builder and validator
No SSE support --> no notifications and therefore no support of listChanged, subscribe and logging.\
Not implemented:
- Sampling - considered for the future, open an issue if you have a use case that would benefit from it
- Elicitation - without SSE I see no proper way to implement this
- Roots - likely irrelevant for ABAP
- Further notifications not relevant without SSE: Cancellation, Progress, Logging
Authorization
Implement the standard Authorization in ABAP via custom code is not feasible, we have to rely on ABAP features. \
An overview of likely options is outlined in Authentication Documentation.
Authentication
OAuth is suggested but outside of newer S/4HANA releases challenging, for options see Authentication. Further suggestions are welcome.
Roadmap
See currently open issues for the next planned steps. Longer term I intend to add features to create modular MCP servers based on reusable implementations.
FAQ
See FAQ.
Contributing
Feel free to:
- Open issues for bug reports
- Use Discord for discussions
- Suggest improvements
- Pull requests are welcome but ensure they are tested and follow the overall style, if in doubt open an issue first
GenAI Notice
Part of the coding was generated using AI, mostly with Sonnet 3.7/4 and GitHub Copilot. Detailed documentation is largely AI generated - only high-level reviewed.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





