Private todo and MCP workflow
Tasks, context and tool calls for agentic work.
WebEdge project
Private todo and MCP workflow
Challenge
Agentic work needs visibility into tasks, context and the tools connected to them.
What we did
We built a task module where the work queue connects with MCP-style tool flows.
Result
Internal work is easier to track and hand over between people and agents.
Dev-story article
Private todo and MCP workflow: how the project was built
Agentic work needs more than a task checkbox. The private task and MCP workflow connects work items with context, tool calls and handoff states between people and agents.
Sections
06
Modules
04
Stack
Vue 3 + Convex
Why the project exists
Agentic work needs visibility into tasks, context and the tools connected to them.
Agentic work needs more than a task checkbox. The private task and MCP workflow connects work items with context, tool calls and handoff states between people and agents.
What was built
We built a task module where the work queue connects with MCP-style tool flows.
The project creates a task module where queue records, instructions, context notes and MCP-style tool flow data live together. It supports internal work that moves between manual review and agent execution.
Main modules and user path
Task records hold title, status, priority, owner and expected result, giving every work item a clear contract before it is picked up.
Context fields connect tasks to references, notes and previous decisions so agents or people can start with the right background.
MCP-style tool call records show which tools were used or are available for a task, making execution steps easier to inspect later.
Handoff states separate pending, in progress, review and completed work, helping internal queues stay readable as tasks move between operators.
Architecture and technology decisions
Technical foundation: Vue 3, Convex, MCP. This matters not as a logo list, but as the set of choices that keeps data, state, user actions and future maintenance manageable.
Vue and Convex provide the live task interface and data store. Tools and context are part of the task model, which matters for agent work where process is as important as output.
How it works in a real scenario
In real use, “Private todo and MCP workflow” works as a clear sequence: it starts from the original problem, then the user takes the primary action, follows a clear data path and reaches the result. The experience stays logical instead of being a random set of screens.
The practical value shows where manual work used to be needed: part of the process is automated, responsibilities are clearly separated, and each module does one understandable job. That is what keeps the solution easy to maintain and extend.
Result and lessons
Internal work is easier to track and hand over between people and agents.
Internal work becomes easier to track, review and repeat. People and agents can share one queue with clearer context and fewer hidden steps.
Related articles
Read next
Related project stories
These projects share nearby technical or product decisions, so they show how the same principle behaves in another context.
Dev-storyWebEdge CMS and public content API
Content management that feeds websites and lets the team publish without developer intervention.
WebEdge project
AI agent control plane
AI agent control plane
An internal workspace for agent jobs, instructions and run status.
WebEdge project
Calendar booking platform
Calendar booking platform
Time booking, team schedules and notifications in one interface.
Have a similar idea?
Discuss your project