A
licenseA
qualityC
maintenanceEnables natural-language control of Super Productivity tasks, projects, and tags via MCP tools that bridge to the app's local REST API.
15
2
MIT
Super Productivity REST MCP
by maystar
Related Servers
Alternatives to Super Productivity REST MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables interaction with Super Productivity's local REST API to manage tasks, projects, and time tracking through natural language.1597 npmMIT
- AlicenseAqualityFmaintenanceEnables Claude to interact with Super Productivity's local REST API for task, project, and tag management, including CRUD operations, status checks, and daily planning prompts.1797 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage TickTick tasks, projects, habits, and focus sessions through the MCP server.141MIT
- AlicenseAqualityAmaintenanceAn MCP server that connects ChatGPT Desktop or Codex to Super Productivity's local REST API, enabling explicit task selection, planning, timer control, and completion via natural language.1020 npmMIT
- AlicenseNot gradedqualityDmaintenanceBridge between Super Productivity app and MCP servers, allowing Claude Desktop to directly interact with Super Productivity for task management, project organization, and information retrieval.120MIT
TDQS
B3.1/5.0
Scored across 16 tools
Disambiguation2/5
Several tools overlap around the 'current task' concept: sp_task_start, sp_task_control_set_current, sp_task_control_stop, sp_status, and sp_task_control_get_current all describe the same state from slightly different angles. This makes it unclear which tool an agent should select for starting, stopping, or querying the active task.
Naming Consistency3/5
The sp_ prefix is consistent, but naming patterns vary: sp_task_get and sp_tasks_list mix singular/plural, while sp_task_start vs sp_task_control_set_current and sp_health/sp_status break the verb_noun rhythm. The names are readable but not predictable enough to be a 4 or 5.
Tool Count3/5
16 tools is on the borderline of being heavy for the scope, and the redundant current-task control tools make the count feel inflated. It is not excessive, but several tools could be consolidated without losing capability.
Completeness3/5
Tasks have solid lifecycle coverage with create, get, list, update, delete, archive, restore, start, and stop. However, projects and tags only have list operations, and focus only has a getter, leaving no way to manage those resources through the MCP server.
Maintenance
ActivityMaintained
ResponsivenessNo issues