MVC pattern in Java application

I am trying to understand MVC pattern. This question has been asked answered before, but I still can't understand.

Right now I am developing a simple Swing multithreaded program that downloads a various csv-files from DropBox and fills JTable with the data from these files.

I think that Model is represented by DropBoxDownloader class, FileParser class, some utility classes and that's all. View is simply my frame classes.

I am curious about Controller. What is it supposed to do? It feels like controller is supposed to be communication coordinator for Model View, but I can't understand it completely. It is said that controller makes it easy to change both View and Model without changing entire application. Am I right?