onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
Outside the atlasOutside the atlastypeA thing outside the atlas that something inside it depends on or talks to. It is named here so that the dependency or the connection can be an edge; it is not rated, not covered and never an artifact.See every one →

Google Chrome

Google's web browser, installed on the developer's own machine. For the things here it is the browser a server starts with a persistent profile of its own, so an SAP login happens once in a real session and later requests run from inside the signed-in page.

Open google.comchecked

Where it sits

Kind
Software

Used by1

sac-workbench-mcpindependently maintained

Required dependency. The browser the server drives with a persistent profile of its own, where the SSO login happens and from inside whose SAC page the requests are sent; another channel can be set with SAC_BROWSER_CHANNEL.

Functional boundary

Large parts of it ride on undocumented SAC internals, and the maintainer states both halves of that: the interfaces may change or break with any SAC update, and SAP does not support this software or any change it makes to your tenant. Writes are gated, since a changing tool refuses without `allowalteration: true` and `readOnly: true` blocks them altogether, and the README still asks you to test in a sandbox tenant or folder first and keep backups. The three expert tools (raw JavaScript in the SAC page, raw HTTP to the tenant, replay of a recorded request) bypass the guard rails the regular tools apply, from the automatic snapshot to the signal-colour check, which is why they are off by default.

Details

Graph1
← POINTS HERE
dependency ofsac-workbench-mcp
POINTS OUT →
nothing yet
For your agent
Ref
external:google-chrome
JSON
/externals/google-chrome.json
MCP
Connecting an agent