Skip to main content
Glama

Related Servers

Alternatives to abap-config-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Lets Claude and other MCP hosts do real ABAP development on SAP systems through ADT: search objects, read and write source, transports, activation, ABAP Unit, ATC, short dumps, debugger and SQL queries. 173 tools, multi-system (S/4HANA Cloud and on-prem), with server-side guard rails and an audit log.
      2
      284 npm
      15
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables managed operations against SAP systems, preserving upstream tools while adding RAP and multiclient capabilities, with validated schemas, paged results, and session-bound access for object CRUD, activation, transports, debugging, refactoring, Git, and analysis.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Facilitates interaction with SAP ABAP systems via ADT APIs, enabling object management, transport handling, and code analysis.
      100
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access and work with an SAP ABAP system through the ABAP Development Tools (ADT) REST API. It supports searching and browsing the repository, reading, writing, activating and deleting source code and objects, running syntax checks, unit tests, ATC and SQL queries or classes, inspecting short dumps, and managing transport requests.
      335 PyPI
      MIT

    TDQS

    A3.9/5.0

    Scored across 58 tools

    Disambiguation4/5

    Despite 58 tools, descriptions explicitly cross-reference siblings and carve boundaries (get_abap_object_lines vs get_abap_batch_lines, customizing_apply vs customizing_create vs org_copy, engine_deploy vs customizing_engine_bootstrap). A few overlaps remain—lock_abap_object is admitted to be 'rarely needed' next to self-locking write_abap_object_source, and the several customizing preview/write tools (plan_change, diff, apply, status) take reading to keep apart—but each has a distinct role.

    Naming Consistency3/5

    There is useful domain grouping (abap_debug_*, customizing_*, hana_*, transport/get_/search_/create_ prefixes), but conventions are mixed: verb_noun (get_abap_object_lines, search_abap_objects), noun_verb/noun-only (version_history, syntax_check, img_search, retail_listing, where_used), and bare nouns (connected_systems, adt_discovery, org_copy). Names stay readable, but no single predictable pattern holds across the set.

    Tool Count2/5

    58 tools is well past the heavy threshold, and the surface spans several distinct domains—ABAP source editing, debugging, transports, ATC/unit tests, SM30 customizing engine, org-unit copying, HANA/ABAP memory diagnostics, and retail listing. Individually many earn their place, but the set is too large to be a well-scoped single server.

    Completeness3/5

    Core ABAP lifecycle (search, read, write, activate, create, delete, transports, debug, tests, where-used) and customizing lifecycle are broadly covered. However, descriptions repeatedly point to read_table_contents and execute_data_query, which are not in the tool list, and analyze_dump only lists dumps without returning dump text—leaving dead ends an agent will hit when following documented workflows.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data