Person
dnic-dev
GitHub@dnic-devlast push
Capabilities
Provides
Agent access to your codeBTPAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Analytic modellingBTPAnalytic modellingDefining what an analytical client actually reads — the multi-dimensional layer between stored rows and a chart: measures, dimensions, hierarchies, filters and parameters, and the associations somebody navigates them by. Distinct from [analytical queries](capability:analytical-queries), which is a service answering the request a chart sends, and from [loading a warehouse](capability:warehouse-loading), which fills the tables underneath it.Loading a warehouseBTPLoading a warehouseGetting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from [replication](capability:replication), which is an application reading data that lives elsewhere as if it were local rather than a warehouse being filled.Tool governanceBTPTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.
Entries
Group by
EntrySignals
Maintains
bw-modeling-mcpbw-modeling-mcpReads, creates and modifies BW/4HANA modelling objects through the same internal APIs Eclipse BWMT and the BW/4HANA Cockpit use — and can run centrally on BTP with each caller reaching BW as themselves.independent, btp
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
MCP server for BW/4HANA modelling objects
Details
History
- bw-modeling-mcpTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Filed on the BTP door: Datasphere, Analytics Cloud, Business Data Cloud, BW/4HANA and HANA Cloud are BTP services, and the atlas has no data-and-analytics door — an open question recorded in docs/NEIGHBOURS.md rather than settled by a placement. Written from the repository's own README.
- bw-modeling-mcpcapability:analytic-modelling was named the same day. Until then this artifact answered only "is an MCP server", which said what it is and not what it is for.
- bw-modeling-mcpcapability:warehouse-loading was named the same day. Until then this artifact answered only "is an MCP server", which said what it is and not what it is for.
- bw-modeling-mcpBW/4HANA entered as an external rather than a service — it is installed software with releases, not something you subscribe to and bind — which finally gave this edge something to point at.
- First entry seenDiscovered via sap-ai-mcp-servers.
For your agent
- Ref
actor:dnic-dev- JSON
- /actors/dnic-dev.json
- MCP
- Connecting an agent