> This looks awesome but I think I might still prefer to have an agent make these changes. Not sure though.

Not entirely sure what you mean here, but the next big feature for micasa is an autopopulation pipeline. Upload a quote PDF and populate the project, quote, and vendor tables. It might not be viable ultimately, but I would love to see how far I can get.

Overkill? Definitely.

Yep that's exactly what I'm talking about. I don't think it's overkill. It feels very natural and filling out forms feels archaic to me (unless it's a "edit this quickly" where that's almost always faster than asking an agent.)

So I've been building a full piece of software to manage my small business. And it looks like traditional software (forms, tables, etc). But every single thing also has an MCP tool.

So then I find myself just talking to the agent especially as an input mechanism way more than clicking around and editing a form.

I'm just saying, as an input method, I think forms, TUIs, etc will be good as a backup. Over time, as you've outlined, we'd just say "here's a PDF, figure it out" and the agent just inputs the right values into the right fields.

That's how I've approached my run-my-business app. I have models/tables for clients, purchase orders, invoices, support tasks, everything. But my interaction is more like "Add me to all the active projects, set my cost rate to __" and it'll run 15 MCP calls and put the data where it belongs.

Or I'll ask "what invoices are way overdue?" and it'll run the MCP calls to get it, even though I have pretty dashboards.

Glad to see you're already thinking of it.