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
      B
      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.
      134 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.
      Apache 2.0

    • abap-adt-mcp

      abap0917
      A
      license
      A
      quality
      C
      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
      278 npm
      MIT

    • abap-adt-mcp

      timkoehne
      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.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 107 tools

    Disambiguation4/5

    Each tool targets a distinct BW object type/action, and the long descriptions carefully separate near-neighbours such as bw_get_dtp vs bw_get_dtps or bw_activate vs bw_activate_request. However, with 107 tools there are many similarly named lifecycle and process-chain editing variants, so misselection remains a real risk despite the thorough descriptions.

    Naming Consistency5/5

    All tools follow the bw_<verb>_<noun> snake_case convention, with get/create/update/delete/activate as dominant verbs. Occasional plurals and specialized verbs like push, run, swap, and append still fit the same predictable pattern.

    Tool Count1/5

    107 tools is an extreme surface, far beyond the 3-15 well-scoped range even for a complex domain. Many fine-grained process-chain mutations and per-object getters could be consolidated, making the set difficult for an agent to navigate.

    Completeness4/5

    The toolkit covers create/read/update/delete and lifecycle operations across aDSOs, transformations, DTPs, queries, InfoObjects, CompositeProviders, process chains, planning objects, and data loads. Minor gaps remain—no real DataSource structure editing, no InfoArea/Open Hub update tools, and some process chain step types are unsupported—but core workflows have no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources