Refactor: JenkinsServer runs the risk of being a God Class

The JenkinsServer class is pretty large already, and is growing with every new feature.
In the spirit of single-principle responsibility, would it be more scalable going forward grouping related methods i.e. all job accessor/mutators, all view accessor/mutators methods into their own manager classes, meaning that the JenkinServer has methods to retrieve these managers to call existing methods on, rather than calling existing methods directly on the JenkinsServer class?