Problem:
The TickTick MCP integration currently only retrieves active tasks from projects. The /project/{id}/data endpoint used by get_project_tasks() doesn't return completed tasks, making it impossible for users to view finished work through the API.
Expected Behavior:
Users should be able to see both active and completed tasks when querying a project, allowing for full task visibility and audit trails.
Current Behavior:
Only active tasks are returned; completed tasks are silently omitted from results.
Solution:
Implement the proper POST /task/completed endpoint from TickTick's Open API to fetch completed tasks with configurable date range filtering, and update get_project_tasks() to display both task categories.
The tool can accept optional parameter controlling whether the completed tasks should be returned. The parameter has the default value of False, thus, maintaining backward compatibility.
Problem:
The TickTick MCP integration currently only retrieves active tasks from projects. The
/project/{id}/dataendpoint used byget_project_tasks()doesn't return completed tasks, making it impossible for users to view finished work through the API.Expected Behavior:
Users should be able to see both active and completed tasks when querying a project, allowing for full task visibility and audit trails.
Current Behavior:
Only active tasks are returned; completed tasks are silently omitted from results.
Solution:
Implement the proper
POST /task/completedendpoint from TickTick's Open API to fetch completed tasks with configurable date range filtering, and updateget_project_tasks()to display both task categories.The tool can accept optional parameter controlling whether the completed tasks should be returned. The parameter has the default value of
False, thus, maintaining backward compatibility.