Expose Subtasks as first class resources in the MCP API
It would be great if Subtasks were exposed as first class entities for both Aki and MCP compatible assistants, with the same level of support that Tasks currently have.
Right now, assistants such as Aki, ChatGPT, Codex, Claude, and other MCP compatible clients can perform the following operations on Tasks:
Read
Create
Update
Delete
Complete
Plan and reschedule
Reorganize
The current limitation is that Subtasks are not exposed as actionable entities for Aki or other MCP compatible clients. As a consequence, when asking an assistant to create a task with several subtasks, it typically falls back to writing a checklist inside the task description instead of creating actual Subtasks.
Ideally, both Aki and the MCP integration should support operations such as:
Read subtasks
Create subtasks
Update subtasks
Delete subtasks
Complete/uncomplete subtasks
Reorder subtasks
Move subtasks between parent tasks
Convert a task into a subtask, and vice versa if supported
This would allow AI assistants to treat Subtasks as first class entities and interact with them in the same way they currently interact with Tasks.
Log in to comment and vote
Comments1
Tadej J.
Jul 14
Hi everyone. Akiflow Subtasks are now available through MCP.
AI assistants can now work with real Akiflow subtasks.
You can ask your assistant to:
Create a parent task with real subtasks
Read the parent and subtask hierarchy
Edit, plan, reschedule, complete, or delete subtasks
Move subtasks between parent tasks
Convert a regular task into a subtask
Detach a subtask and turn it back into a regular task
Subtasks remain independent: completing a parent does not automatically complete its subtasks, and deleting a parent keeps its direct subtasks as standalone tasks.
Subtask reordering, uncompleting, and recurring task/subtask relationships are not currently supported through MCP.
Learn more in our Akiflow MCP guide.