Expose existing ABAP logic as MCP tools
These pages describe how to wrap an existing ABAP class as a Data Provider Class (DPC) for the Hub MCP Designer, so that its logic can be exposed as MCP tools without rewriting the underlying implementation.
The following source class types are covered:
Before you begin
Wrapping an existing class is a fast path to exposing logic as MCP tools and is well suited to prototyping, proofs of concept, and short-term use cases.
For productive, long-term implementations, creating a dedicated DPC class designed from the ground up according to the MCP tool design guidelines is recommended in most cases. A wrapper introduces a dependency between the source class and the MCP class. Parameter or method changes in the source class will require corresponding updates to the wrapper that can increase the maintenance overhead.
Where you do wrap an existing class, the MCP class definition gives you the opportunity to improve on the naming used in the source class, using cleaner method names, natural language parameter names, and the removal of Hungarian notation prefixes, without modifying the source class itself.
See MCP tool design best practices for full tool design guidelines.