AI that suggests vs. AI that acts: what I learned building an MCP-native task manager

By 2026, most "AI-powered" task managers are still just 

regular apps with GPT slapped on top. You ask, it suggests. 

You copy-paste. The AI never actually touches your data.

I spent the last few months building the opposite: a task 

manager where the AI is a first-class user. Native MCP 

server with 70+ tools and OAuth scopes. Claude doesn't 

suggest a task — it creates one, assigns it, runs the 

velocity report, moves it across the kanban. Same actions 

you can do, just via natural language.

A few things I learned along the way that surprised me:

— MCP changes the UX assumption. When the AI can actually 

write to your data, you stop building "AI features" and 

start building good primitives that compose well. The 

protocol does the rest.

— Offline-first is harder with AI in the loop. Had to do 

HLC conflict resolution + IndexedDB sync because users 

expect Claude commands to work even on a flight, then merge 

cleanly when they're back online.

— Most of the value isn't in the magic — it's in the boring 

stuff. "Create a project with 5 tasks for the website 

redesign, P1, due Friday" saves more time than any clever 

AI feature I tried to implement.

Question for the forum: are you actually using MCP-enabled 

tools day-to-day, or is it still tech-demo phase for most 

people? Curious what's working for you.

Quietly launching this on PH tomorrow morning PT — Vector 

ToDo, link in profile if anyone wants to poke around. But 

genuinely more interested in the MCP discussion