A task board per project that hands off to the time tracker. It keeps tasks per project in columns with due dates, estimates, priorities and tags, shows the board, overdue items and a weekly review of planned versus done, and starts a time-tracker timer from a task with the link recorded on it.
The pattern worth building is a chat that starts with "what's on the nova board" and ends with "start the timer on the one I'm about to work on," so the task you picked and the task the timer bills are the same string, not two names that drifted apart.
| You say | Tool |
|---|---|
| Add a task to the nova site board: write the launch email, due Friday, 90 minutes. | task_add |
| What's overdue, and start the timer on the API task. | overdue then task_start_timer |
| Weekly review. | weekly_review |
Two server processes on one data directory firing 40 concurrent task_add calls at the same board all persisted with unique ids and the counter landed on exactly 41, which is what the advisory lock around the id counter is there to guarantee.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
{
"mcpServers": {
"kanban": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-kanban"]
}
}
}The Customize page shows the server and its tools once it has started.
The npm publish of @theluckystrike/mcp-kanban is pending; until then use the .mcpb bundle or a clone and build from the latest release.
There is no hosted endpoint for this one yet. MCP Kanban runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Three of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP: time-tracker, price-tracker and invoice.
The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: 3 project boards, 200 open tasks, the default five columns. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Kanban pasting the config block above is the supported route.
MCP Kanban in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs