Hello,

the AdapterConfig property of the MetadataProviderServer (in your example Server.AdapterConfig) is used to pass a configuration file to the init of the MetadataProviderAdapter instance but no operations are performed on that file.
The AdapterConfig is expected to be a file path (but it could be any string) and it is passed as is to the MetadataProviderAdapter.
So the MetadataProviderAdapter will receive a string containing the path passed as AdapterConfig. This means that the file should be parsed by custom code.

An idea could be to parse the file early (eg in the StandaloneLauncher.cs) and pass it to the MetadataProviderServer instance (Server) as a list of properties in the AdapterParams property.

Obviously this means that you can use any kind of file as the reading of it is up to your code.

HTH.