ADAM
Related Servers
Alternatives to ADAM
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to access SAP ADT APIs for reading, writing, debugging, deploying, and testing ABAP code through natural language or DSL automation.530MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform ABAP Development Tools operations on SAP ERP (ECC and S/4HANA) systems, including source code editing, object activation, syntax checks, and ABAP unit tests.14 npmMIT
- AlicenseBqualityCmaintenanceEnables AI coding assistants to connect directly to SAP ABAP systems via ABAP Development Tools, so they can retrieve and manage source code for programs, classes, interfaces, functions, tables, and CDS views. Also supports RAP development, running unit tests and coverage checks, inspecting transports and version history, and working across multiple SAP systems.65MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to work with SAP ABAP systems through the ADT REST API, supporting repository search, source code read/write, activation, syntax checks, and transport request management.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to debug code inside VS Code by setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions across multiple languages.583MIT
- AlicenseBqualityAmaintenanceEnables LLMs to develop, debug, test, and manage SAP ABAP objects on a live system through the ABAP Development Tools (ADT) protocol.2911MIT
TDQS
Scored across 5 tools
abap_debug and abap_debug_session share the debug prefix and can be confused: one runs a one-shot capture, the other performs a single interactive-session move. abap_breakpoints also overlaps with breakpoint arming in abap_debug, though the descriptions cross-reference each other and explain the boundaries.
All tool names use a consistent lower_snake_case abap_ prefix, making the set readable and predictable. The suffixes mix actions (debug, search) and nouns (breakpoints, source, session) rather than following a strict verb_noun pattern, but this is a minor deviation.
Five tools is well-scoped for complex ABAP debugging. Each tool maps to a distinct area: object search, source inspection, capture debugging, interactive stepping, and breakpoint cleanup.
The tool surface covers the debugging lifecycle end-to-end: finding objects, reading active source, arming and running captures, inspecting stops, stepping interactively, and cleaning up breakpoints/listeners. No significant gaps in ABAP debugging workflows are apparent.