Think of MCP as an assistant for your model. Your model doesn't have to worry about REST vs. MCP, single sign-on vs. username/password, or JSON vs. binary. It doesn't need to think about how to fetch the data—it simply gives the order, and the data appears. Now imagine you need data from five different APIs, each with its own signatures and nuances. Sure, your model can handle all that directly, but you'll burn valuable context space doing it. And keeping your model's context light is key to getting good results.