coBWeb
A read-only MCP server for exploring SAP BW/4HANA models — it finds, reads, and maps BW objects and reports the spec formats writes would need.
Search (
bw_search): find objects by name/description wildcard or list an InfoArea's contents, with type filters and a limit.Read (
bw_read): pull one object's definition atsummary,full, orrawdetail, or just a singlepart(fields, keys, rules, steps, layout…).Map relationships (
bw_context): data flow (sources/targets with transformations and DTPs) or where-used impact analysis, up to 5 hops in either direction.Learn write specs (
bw_describe): get the spec format, fields, defaults, and examples thatbw_writeexpects for each object type — but note that write, activate, data, monitor, and run tools are not exposed in this configuration.Transports (
bw_transport): list changeable transport requests (own/all users, with objects, incl. released).System info (
bw_system): release, platform, enabled object types, and active safety settings.Coverage: InfoAreas, InfoObjects, ADSOs, CompositeProviders, InfoSources, transformations, DTPs, DataSources, process chains, queries and query components, planning objects, hierarchies, and Open Hub destinations.
Safety: everything is read-only here; writes, business-data reads, and runtime actions must be separately enabled via server flags.
Provides tools for modeling and operating SAP BW/4HANA through the BW Modeling Tools REST interface, including object search/read/write/activation, data queries, process monitoring and runtime actions, transports, and safety-scoped administration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@coBWeb create an ADSO for sales orders and activate it"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
coBWeb
An MCP server for modeling in SAP BW/4HANA. coBWeb talks to the REST interface of the BW
Modeling Tools (/sap/bw/modeling/…) and gives a language model eleven intent-based tools:
search, read, write, activate, data, monitoring, runtime actions and transports. It does not
offer one tool per object type and operation.
The design goal is a small, stable tool list that costs few input tokens on every step, and writes that finish a task in few calls:
Few tools, small schemas. The whole catalog has 11 tools and about 16,200 characters (roughly 4,600 tokens). The default profile
modelinghas 8 tools and about 10,600 characters.One call per change.
bw_writetakes several objects at once (InfoObjects, a DataStore object, a CompositeProvider, a transformation and its DTP), orders them by dependency, locks, saves, activates and unlocks. The model never handles lock handles or sessions.Declarative specs. An object is described by a spec; the same spec again reports
unchanged.bw_describereturns the spec format of a type.Compact answers. Reads return a summary first;
detailandpartgive more on request. Errors say what to change.Safe by default. Without flags the server only reads. Writes, data access and runtime actions are switched on separately and limited to packages and InfoAreas you allow.
Structured results for programs. With
COBWEB_STRUCTURED=true, reads and the data flow also come as JSON with an output schema, for applications that call coBWeb without a model.
Tools
Tool | Purpose |
| find objects by name or description; list an InfoArea |
| read one object: summary, full or raw; |
| data flow and where-used of an object in one answer |
| the spec format |
| create, update, delete several objects and activate them in one call; |
| check or activate inactive objects |
| query data (rows, columns, filters, variables, hierarchy nodes), DataSource preview, characteristic values |
| process chain runs, load requests, remodeling requests, query statistics |
| run a DTP, start a process chain, activate or delete requests, remodeling, push data into an ADSO |
| changeable transport requests, transport tasks, package assignment, moving objects between InfoAreas |
| system profile and active safety settings; release a lock after an aborted change |
Parameters and examples: docs/TOOLS.md.
Related MCP server: SAP BTP ABAP ADT MCP Server
Object types
Code | Object | Read | Write |
| InfoArea | ✔ | create, update, delete |
| InfoObject (characteristics, key figures, attributes, compounding, reference characteristics, text types, hierarchies) | ✔ | create, update, delete |
| DataStore object (advanced) incl. fields without InfoObject, keys, settings, planning | ✔ | create, update, delete |
| CompositeProvider (union, join), mappings, field groups | ✔ | create, update, delete |
| InfoSource | ✔ | create, update, delete |
| Transformation: rules, lookups, start, end and expert routines, runtime | ✔ | create, update, delete |
| Data transfer process: mode, filters, filter routines, semantic groups | ✔ | create, update, delete |
| DataSource: fields, delta | ✔ | create, update, delete |
| Source system and its entities | ✔ | – |
| Process chain: steps, decisions, scheduling; settings of each process variant | ✔ | create, update, delete |
| Query: layout, filter, members, characteristics, settings, cells, roles | ✔ | create, update, delete |
| Query components | ✔ | create, update, delete |
| Aggregation level, planning filter, planning function, planning sequence | ✔ | create, update, delete |
| Hierarchy of a characteristic ( | ✔ | create, update, delete |
| Open Hub destination | ✔ | delete |
| Roles and the queries published in them | ✔ | via the query ( |
coBWeb is developed and tested on SAP BW/4HANA 2.0 and later. The platform is detected at start; classic BW 7.5 on HANA is recognized but not supported.
Setup
Requirements: Node.js 22 or later; a BW/4HANA system with the BW Modeling Tools services active and a user with modeling authorization.
git clone https://github.com/oliverluette/coBWeb-mcp.git
cd coBWeb-mcp
npm install
npm run buildConfiguration
All settings are environment variables of the server process.
Connection:
Variable | Meaning |
| base URL of the BW system, e.g. |
| logon (basic authentication) |
| client, default |
| instead of user and password: cookies of a browser session (e.g. SAML) |
|
|
Tools and safety (all optional; without flags the server is read-only):
Variable | Default | Meaning |
|
| tool set: |
| – | explicit tool list, overrides the profile |
| all | allowed object types, e.g. |
|
| create, change, delete, activate, transports, unlock |
|
| read business data ( |
|
| runtime actions ( |
|
| packages writes may go to; patterns with |
|
| InfoAreas objects may be created in or changed |
| – | single actions to refuse, e.g. |
|
| upper bound of every tool result |
| – | file for the audit log (one JSON line per written object) |
|
|
|
|
| structured results for programs, not for model clients (see docs/TOOLS.md) |
Profiles:
Profile | Tools |
| search, read, context, describe, write, activate, transport, system |
| search, read, context, data |
| search, read, monitor, run, system |
| all eleven |
Tools that a profile or the flags leave out are not offered at all, so the model never sees
them. bw_system(action="profile") shows the active settings.
Claude Desktop
In claude_desktop_config.json:
{
"mcpServers": {
"cobweb": {
"command": "node",
"args": ["/path/to/coBWeb-mcp/dist/transport/stdio.js"],
"env": {
"BW_URL": "https://…",
"BW_USER": "…",
"BW_PASSWORD": "…",
"BW_CLIENT": "001",
"COBWEB_PROFILE": "modeling",
"COBWEB_ALLOW_WRITES": "true"
}
}
}
}Restart Claude Desktop after a change.
Claude Code
claude mcp add cobweb --env BW_URL=https://… --env BW_USER=… --env BW_PASSWORD=… --env BW_CLIENT=001 \
-- node /path/to/coBWeb-mcp/dist/transport/stdio.jsOther MCP hosts
Any host that starts stdio servers works: command node, argument
dist/transport/stdio.js, and the environment variables above.
Development
Command | Purpose |
| compile TypeScript to |
| type check without output |
| print the tool list a profile offers (JSON) |
| development launcher: runs the server as a child and restarts it before the next tool call when |
For development, point the host's args at scripts/dev-reload.mjs instead of
dist/transport/stdio.js; a new build then takes effect without restarting the host. A changed
tool list is announced with notifications/tools/list_changed; hosts that do not read it again
need a restart for that.
How the server is built: docs/ARCHITECTURE.md. Changes per version: CHANGELOG.md.
Origin
coBWeb started as a fork of bw-modeling-mcp
(MIT License). It keeps that project's BW client and its write, reporting and runtime paths
for the BW REST services (src/legacy/, parts of src/bw/), changed where needed; the tool
design, object adapters, write engine and policy are new. The details are in NOTICE.
License
Available Tools
6 toolsbw_contextData flow and where-usedARead-onlyIdempotent
Show how a BW object is connected: relation="dataflow" lists sources and targets with the transformations and DTPs between them; "where_used" lists objects that reference it (impact before a change). Use it instead of reading many objects one by one. depth controls how many hops are followed.
Inputs: name (required), type (required), depth, relation, +2 more.
bw_describeSpec format for bw_writeARead-onlyIdempotent
Return the spec format bw_write expects for one object type and action: allowed fields, data types, defaults, rules and a minimal example. Call it once per type before the first bw_write of that type; the result does not change during a session.
Inputs: type (required), action.
bw_readRead a BW objectARead-onlyIdempotent
Read the definition of one BW object. detail="summary" (default) returns a compact, model-friendly overview (fields, keys, settings, status); "full" adds every property; "raw" returns the backend XML/JSON and should only be used for debugging. Use part to read only one section of a large object, e.g. fields, keys, rules, steps, layout.
Inputs: name (required), type (required), part, detail, +1 more.
bw_searchSearch BW objectsARead-onlyIdempotent
Find BW objects by technical name or description, or list the contents of an InfoArea. Use it when you do not know the exact name or want to check that a name is free. Wildcard * is allowed. Returns type, name, description and active state, at most limit hits plus a total count.
Inputs: limit, query, types, info_area, +1 more.
bw_systemSystem profile and maintenanceARead-onlyIdempotent
System information: release, platform (BW/4HANA or classic), enabled object types and the active safety settings. Call it only when a call fails for a system reason, not as a first step.
Inputs: action.
bw_transportTransports and packagesBRead-onlyIdempotent
List the changeable transport requests (own, modifiable by default). Use it before bw_write when an object lives outside $TMP.
Inputs: action (required), user, objects, package, +5 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
The six tools have mostly distinct roles: search finds names, read returns object definitions, context shows relationships, describe returns write-spec metadata, transport lists transport requests, and system reports environment details. The main ambiguity is that bw_describe and bw_transport both reference a missing bw_write, so an agent may wonder how their outputs are actually meant to be used.
All tools use a consistent bw_ prefix and lowercase snake_case, which is predictable and readable. The suffix convention mixes nouns (bw_system, bw_transport, bw_context) with verbs (bw_search, bw_read, bw_describe), though this is a minor deviation rather than a serious inconsistency.
Six tools is a reasonable, well-scoped count for a BW metadata and inspection server. However, the set feels slightly thin for a domain whose own tool descriptions assume an available write operation.
The surface is read-heavy and severe gaps exist: bw_write is repeatedly referenced but absent, and there are no create, update, delete, or transport-release operations. This will cause dead ends for any agent trying to follow the documented workflow of inspecting then modifying BW objects.
Maintenance
Related MCP Connectors
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Schema modeling in JSON, JSON-LD, and other formats with CoreModels platform.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
List datasets, schemas, run APL queries, and use prompts for exploration, anomalies, and monitoring.
Related MCP Servers
- AlicenseBqualityAmaintenanceEnables AI assistants to read, create, and modify SAP BW/4HANA modeling objects via the internal REST API, including aDSOs, InfoObjects, transformations, DTPs, queries, and more.21173 npm85MIT
- FlicenseNot gradedqualityCmaintenanceEnables SAP ABAP development workflows including ADT login, object search, read, create, update, activate, delete, and OData service publishing.1-
- AlicenseNot gradedqualityDmaintenanceA 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.MIT
- FlicenseBqualityCmaintenanceEnables AI assistants to explore and query SAP BW/4HANA modeling objects and metadata, such as InfoAreas, InfoObjects, ADSOs, CompositeProviders, and Queries.15-