Why combine a server-side MVC with a client-side MVC?
Honestly the ASP.NET MVC advocacy doesn't make sense to me. It is a solution that half brings .NET developers into the modern era. Using it purely as a service layer is that project essentially trying to maintain relevance in the face of irrelevance.
Also the routing is not RESTful at all and doesn't handle nesting very well, so you have to find a 3rd party routing library or role your own.
If you're developing an API or service, use WebAPI instead. It solves most of the issues people have with MVC. MVC is still simple and easy to use to create services with, and I'd still recommend it to people.