Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bw-modeling-mcp

No user-submitted related servers found.

    Related Servers

    • BW-Modeeling-mcp

      shreemanrs6
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants like Claude to work directly inside SAP BW/4HANA systems — reading, creating and modifying BW modeling objects via the internal REST API used by Eclipse BWMT.
      80 npm
      MIT

    • sap-adt-mcp

      engoetz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      Apache 2.0

    • abap-adt-mcp

      abap0917
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.
      24
      361 npm
      MIT

    • abap-adt-mcp

      timkoehne
      A
      license
      Not graded
      quality
      A
      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.
      26 PyPI
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 123 tools

    Disambiguation4/5

    Most tools have a distinct resource+action, and descriptions explicitly distinguish overlapping cases (e.g., bw_activate vs bw_activate_request, bw_get_dtp vs bw_get_dtps, in-place process-chain edits vs full replacement). However the 123-tool surface includes several confusable pairs (query/role tools, REST vs metadata-table fallbacks) that require careful reading.

    Naming Consistency4/5

    All names use a consistent bw_ prefix and lower snake_case, mostly verb_noun (create/get/update/delete/list). A few deviations (bw_system_profile, bw_search, bw_xref) and verb variety (set/change/move/swap) are minor, so the pattern remains predictable.

    Tool Count1/5

    123 tools far exceed the practical 3-15 range and exceed the 50+ threshold for extreme mismatch. Even for a large domain like SAP BW modeling, the set is overwhelming for reliable agent selection.

    Completeness4/5

    Coverage is very deep: create/get/update/delete/activate for aDSOs, InfoObjects, queries, transformations, DTPs, planning objects, process chains, datasources, and more. Gaps remain for a few object types (Open Hub destination, analysis process, InfoPackage, classic providers) that are read-only, and some lifecycle operations rely on generic bw_delete/bw_activate.

    Maintenance

    ActivityNo data
    ResponsivenessWithin a week

    Resources