Skip to main content
Glama
Sign In
super-productivity-mcp

super-productivity-mcp

by kailasas-auspicious
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

super-productivity-mcp

An MCP server and two Claude skills for Super Productivity's Local REST API, plus a one-line installer so a teammate can onboard by pointing their Claude co-worker at this repo.

Super Productivity's API runs on http://127.0.0.1:3876, requires no auth (localhost-only), and must be turned on manually via Settings → Misc → Enable local REST API.

The two skills

  • super-productivity-onboarding — drives setup itself: detects the user's OS, briefs them on what it's about to install and why, gets explicit go-ahead, then installs Super Productivity (if missing), Bun, builds and registers the MCP server, installs both skills, and verifies everything works.

  • super-productivity-daily-schedule — day-to-day use: planning the day, adding/checking off tasks, time tracking, end-of-day review, via the sp_* MCP tools.

Related MCP server: Super Productivity MCP

Onboard someone else

Point their Claude Code at the raw URL of ONBOARDING.md and ask it to follow the steps — it directs Claude to read and execute skill/onboarding/SKILL.md, which will:

  1. Detect their OS and brief them on the plan, then wait for a clear go-ahead before installing anything.

  2. Check for the Super Productivity desktop app (and open the download page if it's missing).

  3. Install Bun if needed (no admin rights required).

  4. Download this repo and compile the MCP server into a single standalone executable — no Node/Bun required at runtime after this.

  5. Install both Claude skills into ~/.claude/skills/.

  6. Register the server with Claude Code: claude mcp add -s user super-productivity -- <path-to-exe>.

  7. Ask the user to flip the "Enable local REST API" checkbox in the app's Settings — the one step that can't be scripted safely, since it's in-app UI state rather than a config file — then verify with sp_health.

Manual equivalent (Windows PowerShell):

irm https://raw.githubusercontent.com/kailasas-auspicious/super-productivity-mcp/main/install/install.ps1 | iex

Manual equivalent (macOS/Linux):

curl -fsSL https://raw.githubusercontent.com/kailasas-auspicious/super-productivity-mcp/main/install/install.sh | bash

What's in here

  • src/ — the MCP server (TypeScript), wraps every endpoint of the Local REST API (sp_list_tasks, sp_create_task, sp_update_task, sp_start_task, sp_get_status, sp_list_projects, etc).

  • skill/onboarding/SKILL.md — drives first-time setup (OS detection, briefing, install, verify).

  • skill/daily-schedule/SKILL.md — day-to-day task/schedule management via the sp_* tools.

  • install/ — the underlying install scripts the onboarding skill runs.

  • ONBOARDING.md — a thin pointer for Claude, not a human, to the onboarding skill.

Local dev

bun install
bun run dev          # runs src/index.ts directly via tsx
bun run build        # tsc -> dist/
bun build ./src/index.ts --compile --outfile dist/super-productivity-mcp

Point Claude Code at your local build for testing:

claude mcp add -s user super-productivity -- bun run --cwd /path/to/super-productivity-mcp src/index.ts

Config

Set SP_API_URL if Super Productivity's API isn't on the default http://127.0.0.1:3876.

Available Tools

15 tools
sp_archive_taskArchive taskC

Archive a task.

Inputs: id (required).

sp_create_taskCreate taskB

Create a new task. Search with sp_list_tasks first to avoid creating duplicates of an existing task.

Inputs: title (required), notes, dueDay, isDone, +7 more.

sp_delete_taskDelete taskC

Permanently remove a task.

Inputs: id (required).

sp_get_current_taskGet current taskA

Get the task currently being tracked, if any.

Inputs: no named parameters.

sp_get_statusGet statusB

Get the current task and task counts.

Inputs: no named parameters.

sp_get_taskGet taskB

Fetch a single task by id.

Inputs: id (required).

sp_healthCheck Super Productivity connectionA

Checks whether the Super Productivity desktop app's local REST API is reachable.

Inputs: no named parameters.

sp_list_projectsList projectsB

List all projects, optionally filtered by title substring.

Inputs: query.

sp_list_tagsList tagsB

List all tags, optionally filtered by title substring.

Inputs: query.

sp_list_tasksList tasksB

List tasks, optionally filtered by title substring, project, tag, or done status. Use tagId 'TODAY' for today's tasks.

Inputs: query, tagId, source, projectId, +1 more.

sp_restore_taskRestore taskC

Restore a previously archived task.

Inputs: id (required).

sp_set_current_taskSet current taskA

Set (or clear, with taskId null) the currently tracked task.

Inputs: taskId (required).

sp_start_taskStart taskC

Set a task as the current (actively tracked) task.

Inputs: id (required).

sp_stop_current_taskStop current taskA

Stop tracking the current task without starting another.

Inputs: no named parameters.

sp_update_taskUpdate taskC

Patch fields on an existing task.

Inputs: id (required), notes, title, dueDay, +7 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 15 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • SP-MCP

      organicmoron
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridge between Super Productivity app and MCP servers, allowing Claude Desktop to directly interact with Super Productivity for task management, project organization, and information retrieval.
      132
      MIT