super-productivity-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SP_API_URL | No | HTTP(S) URL; loopback is enforced by default | http://127.0.0.1:3876 |
| SP_API_TOKEN | No | Optional Bearer token for an authenticated Super Productivity build | |
| SP_LOG_LEVEL | No | error, warn, info, or debug | warn |
| SP_API_TIMEOUT_MS | No | Integer from 1000 to 60000 | 15000 |
| SP_ALLOW_NON_LOOPBACK_URL | No | Use only for a trusted local proxy | false |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthB | Check whether the local Super Productivity desktop API is reachable and ready. |
| check_connectionA | Check whether the local Super Productivity desktop API is reachable and ready. |
| search_tasksA | Find tasks by title or project. Returns task IDs for explicit follow-up actions. |
| list_todayA | List tasks explicitly planned for Today in Super Productivity. |
| plan_task_todayA | Place exactly the supplied task ID in Today, optionally at an explicit ISO timestamp. |
| start_taskA | Start tracking exactly the supplied task ID as the current task. |
| stop_timerA | Stop the Super Productivity timer without selecting or changing another task. |
| complete_taskA | Mark exactly the supplied task ID as completed. |
| get_current_taskA | Return the task currently being tracked, or null when the timer is stopped. |
| ensure_github_issue_taskA | Find an existing native or Super Productivity MCP-marked task for owner/repo#number or a GitHub issue URL. Create at most one marked task if missing; it is not planned for Today unless planToday=true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Amorem/super-productivity-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server