README.md

July 4, 2026 · View on GitHub

SP MCP Bridge icon

Super Productivity MCP Server

An MCP (Model Context Protocol) server that connects AI assistants to Super Productivity — manage tasks, projects, and tags through Claude Desktop, Kiro, or any MCP-compatible client.

What You Can Do

✅ Quick Capture

"Add a task: Buy milk #shopping @tomorrow 15m"

Parses the tag, due date, and time estimate from short syntax — one shot, no follow-up needed.

🧹 Batch Triage

"Show me all unscheduled tasks in my Work project, tag them #backlog, and set them due next Friday"

Filters, bulk-updates due dates, and adds tags — all in one conversation turn.

🧠 Full Planning Session

"Look at my week: show today's plan and anything overdue. Break 'Launch blog' into subtasks, start the first one, and move anything I finished yesterday to done. Give me a time summary when you're done."

Reads resources for context, creates subtasks in batch, starts the timer, bulk-completes tasks, pulls the worklog, and summarizes — a multi-step workflow in a single prompt.

More use cases

Installation

1. Install the SP Plugin

Option A — via npx:

npx -y super-productivity-mcp@latest --extract-plugin

Option B — manual download: Download plugin.zip from the latest release.

Then in Super Productivity: Settings → Plugins → Upload Plugin, select plugin.zip, restart SP.

SP ≥ 18.13.0: After enabling the plugin, SP shows a one-time Node execution consent dialog. Click Allow — the plugin requires Node access to communicate with the MCP server. Consent persists per device; only re-asked if you re-upload the plugin.

2. Configure Your MCP Client

{
  "mcpServers": {
    "super-productivity": {
      "command": "npx",
      "args": ["-y", "super-productivity-mcp"]
    }
  }
}

Config file locations:

  • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
  • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json

For Claude Code, don't edit the config file by hand — use the CLI:

# user scope (everywhere), project scope (-s project), or local scope (default)
claude mcp add -s user super-productivity npx -- -y super-productivity-mcp

To verify, run claude mcp list. Restart the session to load the server. Swap npx -- -y super-productivity-mcp for super-productivity-mcp (global install) or node /absolute/path/to/dist/index.js (from source) — see Running without npx.

3. Verify

Ask your AI assistant: "Check the Super Productivity connection"

Running without npx

npx is convenient but fetches the package on every cold cache and needs network access. If you'd rather pin a local copy, pick one of the options below.

Option A — Global install

npm install -g super-productivity-mcp
super-productivity-mcp --extract-plugin   # optional: write plugin.zip to cwd

Then point your MCP client at the installed binary:

{
  "mcpServers": {
    "super-productivity": {
      "command": "super-productivity-mcp"
    }
  }
}

If the binary isn't found, your MCP client may not inherit your shell's PATH. Use the absolute path from which super-productivity-mcp as command — or, if which doesn't resolve it, point at $(npm config get prefix)/bin/super-productivity-mcp (on macOS/Linux).

Option B — From source

git clone https://github.com/b0x42/Super-Productivity-MCP.git
cd Super-Productivity-MCP
npm install
npm run build              # produces dist/index.js and dist/plugin.zip

Then run the server directly with node:

{
  "mcpServers": {
    "super-productivity": {
      "command": "node",
      "args": ["/absolute/path/to/Super-Productivity-MCP/dist/index.js"]
    }
  }
}

The plugin to upload to Super Productivity is at dist/plugin.zip after npm run build.

Prerequisites

  • Super Productivity >= 14.0.0
  • Node.js >= 18
  • An MCP-compatible client (Claude Desktop, Kiro, etc.)

Available Tools

ToolDescription
create_taskCreate a task (supports SP short syntax)
create_task_with_subtasksCreate a parent task + subtasks in one operation
get_tasksList tasks — filter by project, tag, done, archived, search (title+notes), parents_only, overdue, unscheduled, planned_for_today, recurring_only, fields
update_taskUpdate title, notes, done state, due date, planned_at, time, tags
complete_taskMark a task as complete
delete_taskPermanently delete a task (parent deletes subtasks too)
start_taskStart the time tracker on a task
stop_taskStop the currently running time tracker
get_current_taskGet the currently tracked task (null if none)
plan_tasks_for_todayBatch plan/unplan tasks for today ⚠️ limited
bulk_complete_tasksMark multiple tasks complete in one operation
bulk_update_tasksUpdate multiple tasks in one operation
add_tag_to_taskAdd a tag without replacing other tags
remove_tag_from_taskRemove a single tag
move_task_to_projectMove a top-level task to a different project
reorder_tasksReorder tasks within a project or parent
get_projectsList all projects
create_projectCreate a new project
update_projectUpdate project properties
get_tagsList all tags
create_tagCreate a new tag
update_tagUpdate tag properties
get_task_repeat_cfgsList all recurring task configurations (schedule, cadence, day-of-week settings)
get_worklogTime tracking summary for a date range
show_notificationShow a snackbar in SP's UI
check_connectionVerify SP is running and the plugin is responding
debug_directoriesShow resolved data directory paths

SP Short Syntax

Include these in task titles and they are parsed automatically:

SyntaxExampleEffect
#tagBuy milk #shoppingAdds the "shopping" tag
+projectFix bug +workAssigns to "work" project (prefix match, min 3 chars)
@dueReport @fridaySets due date to Friday
@due timeCall @tomorrow 3pmSets due date and time
30mQuick fix 30mSets 30-minute time estimate
1h/2hResearch 1h/2hSets 1h spent, 2h estimate

Troubleshooting

Plugin not loading? Two common causes:

  • SP 18.6.0–18.9.x cold-boot race: toggle the plugin off and on in Settings → Plugins (no restart needed on ≥ 18.6.0).
  • SP 18.10.0–18.12.x hard block: update to SP ≥ 18.13.0. After re-uploading the plugin, accept the Node execution consent dialog that appears on first enable.

Commands timing out? Ask "Show debug info for Super Productivity" to check that both sides are using the same data directory. Mac App Store users may need to set SP_MCP_DATA_DIR.

Full troubleshooting guide

Known Limitations

ToolIssueStatus
plan_tasks_for_todaySets plannedAt on the task but does not add it to SP's internal Planner store, so the task may not appear in the Today view.Upstream request: super-productivity#7495

License

MIT