It would have been possible to automatically wire up Qt slots from its signals and slots system because these are introspectable, but AFAIK that was not done. For any arguments that needed to be serialized as more than one element of a QDataStream, it would have required additional marshalling code. Objects would also have needed consistent and unique names.
It would have been hacky and questionable to incidentally expose application internals like that.
How it was apparently done was that eligible objects inherited DCOPObject, for which marshalling code was generated at build time using dcopidl2cpp.
https://api-staging.kde.org/legacy/3.0-api/classref/dcop/DCO...