Super Productivity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SP_API_URL | No | Base URL for the Super Productivity 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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Checks whether the Super Productivity local REST API is reachable and the renderer is ready. |
| list_tasksC | Returns tasks from Super Productivity with optional filters. |
| search_tasksB | Searches tasks by title text and optional filters. |
| get_taskB | Returns details of a specific task by ID. |
| get_statusB | Returns the current task and task-count status. |
| get_current_taskA | Returns the currently active task, if any. |
| create_taskB | Creates a new task in Super Productivity. Extra fields are passed through to the local API if supported by your app version. |
| update_taskC | Updates one or more fields of an existing task. |
| complete_taskC | Marks a task as done. |
| start_taskC | Starts the specified task and makes it the current task. |
| set_current_taskA | Sets the current task explicitly, or clears it when id is null. |
| stop_current_taskB | Stops tracking the current task. |
| archive_taskC | Archives a task. |
| restore_taskB | Restores an archived task. |
| delete_taskA | Permanently deletes a task. |
| get_projectsB | Returns all projects in Super Productivity. |
| get_tagsB | Returns all tags in Super Productivity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily-planning | Generates a daily planning session based on the active task list. |
| weekly-review | Guides a weekly review of completed and pending tasks. |
| break-down-task | Breaks a large task into smaller subtasks and creates them. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status | |
| active-tasks | |
| archived-tasks | |
| current-task | |
| projects | |
| tags |
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose. For example, start_task begins tracking, set_current_task just assigns the current task, and get_current_task retrieves it. No two tools have ambiguous boundaries.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., archive_task, complete_task, get_projects). The only slight deviation is health_check, but it is still clearly readable and fits the pattern.
With 17 tools, the server is well-scoped for a task management system. Each tool covers a necessary operation without being excessive or too few.
The tool set covers the full CRUD lifecycle for tasks (create, read, update, delete), plus lifecycle operations (start, stop, complete, archive, restore) and status queries. Project and tag retrieval are included, leaving no obvious gaps for the intended domain.