What it does
Opens no connection of its own: the server runs inside Eclipse and reuses the ADT session of each connected ABAP project, so the agent acts under the developer's logon and the plugin stores and transmits no credentials. On that session it reads source, DDIC objects and short dumps, writes with one call that locks, writes, unlocks and activates, creates objects, opens and releases transport requests, and runs syntax check, ATC and ABAP Unit. Several projects can be connected at once and each tool call names its systemId, and access is per system: a connection starts in write, and Toggle Read-Only makes it refuse the 11 write tools and send no write request to SAP.
Conditions
Eclipse 2024-03 or later with SAP ADT installed on Java 21, and an ABAP project that is logged on: a tool returns The destination with ID <name> is not registered. when the project has no logon after an Eclipse restart.; The README states the connection as the ADT SNC/SSO session of an Eclipse ABAP project and names no release, edition or system type, so what is reachable is whatever that Eclipse is already connected to.; The server listens on 127.0.0.1 behind a bearer token and answers any request carrying an Origin header with HTTP 403, so the agent runs on the developer's machine.
Remaining work
Deciding which of the connected systems stays in write mode, since a new connection starts in write and the mode is stored per project. The session is a developer's Eclipse, so nothing on this path runs in a pipeline.