MCP Kanban Server (io.github.theluckystrike/kanban)

This MCP server provides a local task board per project with columns, due dates, estimates, priorities, and overdue tracking, plus support for weekly review planning. Tasks are created and managed through an AI chat workflow. It stores task data as plain JSON on your own system.

🛠️ Key Features

Local-first task board per project
Columns (backlog, todo, doing, review, done)
Due dates, overdue detection
Estimates and priorities
Short stable task IDs (e.g., NS-12)
Task fields include title, notes, tags, due date, estimate, priority, and column
Task can pass exact arguments to a time-tracker server to align time to the same project name
Plain JSON storage

🚀 Use Cases

Add tasks from AI chat (e.g., write an email with due date, estimate, priority)
Query the board contents
List overdue tasks
Plan a week via weekly review

⚡ Developer Benefits

Plain JSON storage for portability and inspection
Stable task IDs for consistent references
Project-linked time tracking via handoff to a time-tracker server

⚠️ Limitations

Scope is limited to a local per-project task board with the listed task properties and board queries

Run task boards from Claude with a free MCP kanban server

A task board for each of your projects, driven from your AI chat. Say "add a task to the nova site board: write the launch email, due Friday, 90 minutes", then ask "what's on the nova board?", "what's overdue?" or "plan my week". Tasks carry a title, notes, tags, a due date, an estimate, a priority and a column (backlog, todo, doing, review, done by default), each one gets a short stable id like NS-12, and a task can hand its exact arguments to the time-tracker server so the time you spend on it lands against the same project name. Everything is stored as plain JSON on your own machine.

Built by theluckystrike.

In the official MCP Registry (io.github.theluckystrike/kanban-todo-tasks-projects-board).

kanban demo

A local kanban board per project, columns, due dates, estimates, weekly review, zero setup, all local.

60-second install

npm publish for @theluckystrike/mcp-kanban is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.

One-click (.mcpb): download kanban.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest

(claude_desktop_config.json):

json

{
  "mcpServers": {
    "kanban": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-kanban"]
    }
  }
}

Claude Code:

claude mcp add kanban -- npx -y @theluckystrike/mcp-kanban

(.cursor/mcp.json):

json

{
  "mcpServers": {
    "kanban": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-kanban"]
    }
  }
}

The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these three commands:

git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers
npm install
npm run build -w packages/mcp-license -w servers/kanban

Then point your client's command at node with one arg: the absolute path to servers/kanban/dist/index.js.

To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.

Tools

Tool	What it does
`task_add`	Add a task: title plus optional project, column, due date, estimate, priority, tags and notes. A new project name creates its board; a partial name that matches exactly one existing project is used as that project.
	Due dates accept `YYYY-MM-DD`, `today`, `tomorrow`, `yesterday`, `+3d`, a weekday (`friday`, the nearest one from today) and `next friday` (the one after that).
`task_list`	Table of tasks, filtered by project, column, tag, `due_before` or `overdue`. Finished tasks are hidden unless you ask for them. Prints 200 rows by default and says how many more there are; raise it with `limit` (max 2,000).
`task_move`	Move a task to another column on its board.
`task_update`	Change any field: title, notes, due (`none` clears it), estimate, priority, tags, column or project.
`task_done`	Mark a task done: it moves to the done column and is stamped with the time.
`task_delete`	Delete a task. The id is never reused.
	An identical `task_add` (same project, title, column, due date, estimate, priority, tags and notes as a task already open) is refused and names the task that already holds the slot, rather than writing a second copy.
`task_search`	Find tasks by text in the title, notes, tags or id.
`board`	Column-by-column summary of one board: tasks, estimate total, actual total, overdue count.
`task_start_timer`	Return the exact arguments to pass to the time-tracker server's `timer_start` for this task, and record the link on the task.
`task_log_time`	Add real minutes worked to a task, so estimate and actual can be compared.
`project_list`	Every board with open and done counts, remaining estimate and overdue count.
`project_delete`	Delete an empty board and free its project slot. A board that still holds tasks, open or done, is refused with a task named; clear them with `task_delete` first.
`overdue`	Everything past its due date, across all boards; `as_of` measures against another day.
`weekly_review`	Done versus planned for a week, with estimate against actual per project. This week is free; past weeks are Pro.
`columns_set`	Replace one board's columns (Pro). Tasks in a removed column move to the first column.
`license_status`	Free or Pro, and where to upgrade.
`license_activate`	Activate a Pro key (verified offline).

Also exposed: the resource kanban://today (due today plus everything overdue) and the prompt plan_week (turns the open board into a day-by-day plan that fits the hours you actually have).

What you can say

"Add a task to the nova site board: write the launch email, due Friday, 90 minutes, high priority."
"Move NS-3 to doing."
"What does the nova board look like?"
"What's overdue?"
"Start a timer on NS-3.", then pass the arguments it returns to the time-tracker server.
"I spent 40 minutes on NS-3."
"Weekly review."

Free vs Pro

	Free	Pro
Project boards	3	unlimited
Open tasks	200	unlimited
Columns	the default five (backlog, todo, doing, review, done)	custom columns per board (`columns_set`)
Weekly review	the current week	any week, full history
Estimate vs actual reports	current week only	every week
Listing output	200 rows per call, `limit` up to 2,000	same
Everything else	included	included

Pro is a one-time $19 for this server, or $39 for every server, lifetime.

Get Pro: https://mcp.zovo.one/buy/kanban

Pairs with

mcp-time-tracker, task_start_timer hands it the project and task name, so hours land against the same project.
mcp-calendar, due dates on the board next to what is actually in your week.
mcp-invoice, turn the tracked hours behind those tasks into invoice line items.

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/kanban/. Nothing is uploaded, no account is needed, and licence keys are verified offline.

License

MIT. Support: support@zovo.one

Frequently asked questions

Is there an MCP kanban server?

Yes. The kanban server at mcp.zovo.one gives Claude a hosted kanban board: create boards, columns and cards, move cards between columns, all from any MCP client. Unlike the local-only GitHub repos it is hosted and free to start - nothing to clone or run.

How do I manage a kanban board from Claude?

Connect https://mcp.zovo.one/mcp/kanban and say: 'Create a board with To do, Doing, Done and add a card Design the landing page to To do.'

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-kanban

io.github.theluckystrike/kanban