Skip to main content
Glama
Sign In
bw-modeling-mcp

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

    • coBWeb

      oliverluette
      A
      license
      A
      quality
      C
      maintenance
      Enables language models to model SAP BW/4HANA through the BW Modeling Tools REST interface, with intent-based tools for searching, reading, writing, activating, querying data, monitoring, runtime actions, and transports. It uses compact schemas and safe-by-default permissions to complete changes in few calls.
      6
      MIT

    • 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.
      172 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
      576 npm
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.6/5.0

    Scored across 131 tools

    Disambiguation4/5

    Most tools have clearly distinct object/action scopes, and the descriptions explicitly route between similar options such as REST reads versus bw_read_metadata_tables, bw_search versus type-specific getters, and targeted process-chain edits versus bw_update_process_chain. The main ambiguity risk comes from the sheer number of closely related tools, especially across the query, planning, and process-chain families, but the guidance generally resolves it.

    Naming Consistency4/5

    The set is overwhelmingly snake_case with a consistent bw_ prefix and predictable verb_noun naming such as bw_create_adso, bw_get_query, bw_update_dtp, and bw_delete_request. Minor deviations exist, such as bw_xref, bw_system_profile, bw_query_data, and plural getters like bw_get_dtps, but they remain readable and do not create a mixed-convention problem.

    Tool Count1/5

    131 tools is far beyond the appropriate range for a single MCP server and creates a large selection and maintenance burden even for a broad SAP BW modeling domain. Many tools are well-scoped individually, but the overall surface should be consolidated or split into smaller domain-specific servers.

    Completeness4/5

    Coverage is very broad across BW modeling, runtime monitoring, planning, queries, process chains, transports, and data sources, with create/read/update/delete paths for most core objects. Some gaps remain, such as only read support for Open Hub destinations and incomplete lifecycle coverage for a few specialized object types, but core workflows are well covered.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources