In my opinion, MVC pattern works fine for “simple” servers. However, the way you implement it is important. For example, naming your packages “controllers”, “models” etc. will make it hard to maintain and scaling up. The most common problem you will face in my experience would be avoiding import cycles, since Go doesn’t allow circular imports. Even if you somehow end up avoiding this, I think ensuring different names for every controller/model is tiresome. Check this out. The approach suggested does avoid these basic concerns and is to some extent, if not totally, package oriented too. Feel free to go through the rest of the forum, many design patterns have been discussed with their pros and cons which you may find useful.
Hope it helps!