Deploy dcm4chee-arc-light using the dcm4che/dcm4chee-arc-psql Docker image, which bundles WildFly and PostgreSQL side-car
Obtain a bearer token from Keycloak (default realm dcm4che) using client credentials for the dcm4chee-arc-rs client before calling secured REST endpoints
Query the current device configuration with GET /dcm4chee-arc/ui2/rs/devices/{deviceName} and inspect AETitle definitions in the response JSON
Add or update a new Application Entity with PUT /dcm4chee-arc/ui2/rs/devices/{deviceName}/aets/{aetitle} supplying a JSON body conforming to the DICOM LDAP schema model
Validate the updated configuration is live by sending a C-ECHO from a remote SCU; confirm the server returns a Success status (0000H)
Known gotchas
dcm4chee-arc-light stores its configuration in an LDAP directory by default; REST updates modify LDAP entries, so changes persist across container restarts only if the LDAP volume is mounted
The WildFly admin console listens on port 9990 by default and is separate from the archive REST API on port 8080 — do not confuse the two when setting up firewall rules
Keycloak client secret rotation invalidates cached tokens; implement retry logic with a 401 trigger to re-authenticate before retrying the failed request
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp