super-productivity-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SP_API_URL | No | The URL of the Super Productivity local REST API. | http://127.0.0.1:3876 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sp_healthA | Checks whether the Super Productivity desktop app's local REST API is reachable. |
| sp_list_tasksB | List tasks, optionally filtered by title substring, project, tag, or done status. Use tagId 'TODAY' for today's tasks. |
| sp_get_taskB | Fetch a single task by id. |
| sp_create_taskB | Create a new task. Search with sp_list_tasks first to avoid creating duplicates of an existing task. |
| sp_update_taskC | Patch fields on an existing task. |
| sp_delete_taskC | Permanently remove a task. |
| sp_start_taskC | Set a task as the current (actively tracked) task. |
| sp_archive_taskC | Archive a task. |
| sp_restore_taskC | Restore a previously archived task. |
| sp_get_statusB | Get the current task and task counts. |
| sp_get_current_taskA | Get the task currently being tracked, if any. |
| sp_set_current_taskA | Set (or clear, with taskId null) the currently tracked task. |
| sp_stop_current_taskA | Stop tracking the current task without starting another. |
| sp_list_projectsB | List all projects, optionally filtered by title substring. |
| sp_list_tagsB | List all tags, optionally filtered by title substring. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have distinct purposes, but sp_set_current_task and sp_start_task are nearly identical in description, causing potential confusion. Also, sp_get_current_task and sp_get_status overlap in returning current task info.
All tools use 'sp_' prefix and underscore-separated verb_noun pattern, which is consistent. Minor deviations: 'sp_health' lacks a noun, and 'sp_get_status' vs 'sp_get_current_task' use different nouns for similar actions.
15 tools is a reasonable number for a task management system, covering necessary operations without being excessive. Slightly on the higher side but well within acceptable range.
CRUD for tasks is covered, plus listing projects/tags, tracking current task, and health check. Missing features like subtasks or notes, and no explicit way to list archived tasks. The redundancy in set/start task suggests a gap in tool design.