The server connection metadata are stored in the Eclipse instance scope. It means that if you have multiple workspaces, you don’t have to configure the server again and again.
I’m sorry I don’t know OOMPH in details, but I remember it was possible to record server preferences with the old workspace mechanics plugin.
Also, if you are packaging a custom Eclipse bundle in your company, you can provide a plugin_customization.ini to automatically provision the server.
The only thing missing is the ability to provide a token. Since it is stored in the secure storage, I’m not sure it is possible to automate that. So users will need to edit the server connection to set a token.