> "it makes things a tiny bit easier than interfacing directly via api"
By what metric? I would expect that a thin API client (with readable code) is generally going to out-perform a tool-surface which you don't have the ability to manage/edit.
If you don’t use the MCP Claude will default to taking screenshots of figma designs.
This is what I don't get often when people say "ai will be the ui". Like pressing a button to get an action done for me will always be quicker than asking an LLM to do an action and then waiting for it to understand and do that action. Why will I not prefer to just press the button?
I run a lot of services to track my life and work and theoritically I could hook up their apis or mcp if supported to a harness and pretend like "oh its a talking computer that can do whatever i ask" but in reality, I can go through the native ui of those services esp with things like hot-keys for a faster and more ergonomic experience than talking to a jarvis and having to recorrect it if its wrong