The link mentioned by Vijitha Kumara above was the first thing that came to mind when reading your question.
In short, Spring MVC controllers have traditionally been used to produce HTML output, but improvements introduced in Spring 3.0 make it even easier to write controllers that serve content in whatever format the client wants. But even then that's probably not how
you should look at it...
Thinking with a RESTful mindset, controllers should serve *resources*. A resource is a *thing*...an Order, a Product, an Employee...some noun in your application. The resource that the controller serves and how it's represented are separate matters. Depending on how it's developed, the controller either returns the resource object or puts the resource into the model, but plays no direct role in deciding how it should be represented. A view resolver will decide how it's represented. Or you can use the @ResponseBody annotation along with message converters to help convert that object into XML, JSON, or whatever representation the client is asking for.
So, once the representation is settled, it is returned to the caller...whoever that may be. The caller could be another Spring application using RestTemplate to retrieve the resource. Or it could be a web browser. Or it could be some JQuery-enabled JavaScript. My point is that you don't really "hook" JQuery into Spring--but you can use JQuery to consume a resource, represented as JSON and served by a Spring MVC controller.