io.github.theluckystrike/task-board-todo-kanban

Official17 toolsLive

by theluckystrike · JavaScript

A todo and task board in kanban form, driven from chat with full CRUD.

MCP Server: io.github.theluckystrike/task-board-todo-kanban

A Model Context Protocol (MCP) server that provides a todo and task board in Kanban form. It is driven from chat and supports full CRUD (create, read, update, delete) operations.

🛠️ Key Features

Todo and task board UI in Kanban form
Chat-driven interaction
Full CRUD capability

🚀 Use Cases

Managing tasks using a Kanban workflow via chat
Creating, updating, and deleting todo items through MCP

⚡ Developer Benefits

Defines task management around CRUD operations
Fits chat-based control for a Kanban todo/task board

Topics

claudecursorinvoicemcpmcp-servermodel-context-protocolspreadsheetaccountingai-toolsbookkeepingclaude-desktopfreelanceinvoicinglocal-firstmcp-serverspdfself-hostedtime-trackingvatproductivity

Captured live from the server via tools/list.

license_status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

license_activate

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Parameters1

key

string

required

License key from checkout, MCPL1.<payload>.<signature>

Raw schema

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_add

Add one task to a board and return its id, board and column. The board is created on first use, so pass an existing project or leave it out. An identical open task is refused. Free: 3 boards, 200 open.

Parameters8

title	string	required	What the task is, e.g. 'Write the launch email'
project	string	optional	Project or board name. A partial name matching exactly one existing project is used as that project. Defaults to your only board.
column	string	optional	Column to start in; defaults to the first column (backlog)
due	string	optional	Due date: YYYY-MM-DD, 'today', 'tomorrow', 'Friday', 'next Monday' or '+3d'
estimate_minutes	integer	optional	How long you think it will take, in minutes
priority	string	optional	Priority; defaults to normal
tags	array	optional	Free-form tags, e.g. ['writing','client']
notes	string	optional	Longer notes for the task

Raw schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "maxLength": 300,
      "description": "What the task is, e.g. 'Write the launch email'"
    },
    "project": {
      "type": "string",
      "maxLength": 100,
      "description": "Project or board name. A partial name matching exactly one existing project is used as that project. Defaults to your only board."
    },
    "column": {
      "type": "string",
      "maxLength": 40,
      "description": "Column to start in; defaults to the first column (backlog)"
    },
    "due": {
      "type": "string",
      "maxLength": 64,
      "description": "Due date: YYYY-MM-DD, 'today', 'tomorrow', 'Friday', 'next Monday' or '+3d'"
    },
    "estimate_minutes": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100000,
      "description": "How long you think it will take, in minutes"
    },
    "priority": {
      "type": "string",
      "enum": [
        "low",
        "normal",
        "high",
        "urgent"
      ],
      "description": "Priority; defaults to normal"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 60
      },
      "maxItems": 30,
      "description": "Free-form tags, e.g. ['writing','client']"
    },
    "notes": {
      "type": "string",
      "maxLength": 5000,
      "description": "Longer notes for the task"
    }
  },
  "required": [
    "title"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_list

List tasks as a table of id, project, column, title, priority, due, estimate, actual and tags, sorted by due date, with the total estimate. Done tasks are left out unless include_done. 200 rows default.

Parameters7

project	string	optional	Only this project
column	string	optional	Only this column, e.g. 'doing'
tag	string	optional	Only tasks carrying this tag
due_before	string	optional	Only tasks due on or before this day (YYYY-MM-DD, 'today', 'Friday', '+7d')
overdue	boolean	optional	Only tasks past their due date
include_done	boolean	optional	Include finished tasks; default false
limit	integer	optional	Rows to print; default 200

Raw schema

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "maxLength": 100,
      "description": "Only this project"
    },
    "column": {
      "type": "string",
      "maxLength": 40,
      "description": "Only this column, e.g. 'doing'"
    },
    "tag": {
      "type": "string",
      "maxLength": 60,
      "description": "Only tasks carrying this tag"
    },
    "due_before": {
      "type": "string",
      "maxLength": 64,
      "description": "Only tasks due on or before this day (YYYY-MM-DD, 'today', 'Friday', '+7d')"
    },
    "overdue": {
      "type": "boolean",
      "description": "Only tasks past their due date"
    },
    "include_done": {
      "type": "boolean",
      "description": "Include finished tasks; default false"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 2000,
      "description": "Rows to print; default 200"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_move

Move one task to another column of its own board and report the old and new column. An unknown column is refused, listing the real ones. Entering the done column stamps completion; leaving it clears it.

Parameters2

id	string	required	Task id, e.g. NOVA-12
column	string	required	Target column, e.g. 'doing'

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "description": "Task id, e.g. NOVA-12"
    },
    "column": {
      "type": "string",
      "maxLength": 40,
      "description": "Target column, e.g. 'doing'"
    }
  },
  "required": [
    "id",
    "column"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_update

Change a task by id: only the fields you pass are touched. tags REPLACES the whole list, due 'none' clears it, and project moves the task to a board that already exists. Returns the task's new row.

Parameters9

id	string	required	Task id, e.g. NOVA-12
title	string	optional
notes	string	optional
due	string	optional	New due date, or 'none' to clear it
estimate_minutes	integer	optional
priority	string	optional
tags	array	optional	Replaces the whole tag list
column	string	optional
project	string	optional	Move the task to another existing project board

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "description": "Task id, e.g. NOVA-12"
    },
    "title": {
      "type": "string",
      "maxLength": 300
    },
    "notes": {
      "type": "string",
      "maxLength": 5000
    },
    "due": {
      "type": "string",
      "maxLength": 64,
      "description": "New due date, or 'none' to clear it"
    },
    "estimate_minutes": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100000
    },
    "priority": {
      "type": "string",
      "enum": [
        "low",
        "normal",
        "high",
        "urgent"
      ]
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 60
      },
      "maxItems": 30,
      "description": "Replaces the whole tag list"
    },
    "column": {
      "type": "string",
      "maxLength": 40
    },
    "project": {
      "type": "string",
      "maxLength": 100,
      "description": "Move the task to another existing project board"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_done

Mark one task finished: it moves to the board's done column (named done, else the last) and is stamped, leaving task_list and the open counts. Returns estimate against actual when both are known.

Parameters1

string

required

Task id, e.g. NOVA-12

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "description": "Task id, e.g. NOVA-12"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_delete

Delete one task by id, permanently; the id is never reused. The answer names any logged minutes lost. time-tracker entries are a separate store and are untouched. Use task_done to keep the record.

Parameters1

string

required

Task id, e.g. NOVA-12

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "description": "Task id, e.g. NOVA-12"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_search

Find tasks whose id, title, notes or tags contain the query, across every board, finished ones included. Plain case-insensitive substring, never a regex. Use task_list for structured filters.

Parameters2

query	string	required	Text to look for
limit	integer	optional	Rows to print; default 200

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Text to look for"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 2000,
      "description": "Rows to print; default 200"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

board

Show one board column by column: tasks, estimate, actual and overdue count in each, then the board totals and the estimate still open. Defaults to your busiest board. Use project_list for every board.

Parameters1

project

string

optional

Which board; defaults to your busiest one

Raw schema

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "maxLength": 100,
      "description": "Which board; defaults to your busiest one"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_start_timer

Return the exact arguments to pass to the time-tracker's timer_start for one task, and record the link here. It starts nothing itself, and warns when the tracker's own project names would misfile the time.

Parameters1

string

required

Task id, e.g. NOVA-12

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "description": "Task id, e.g. NOVA-12"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

task_log_time

Add real minutes worked to one task so estimate and actual can be compared. Minutes ADD; a negative corrects an over-count. Below zero or past 100,000 is refused. This counter is the board's own.

Parameters2

id	string	required	Task id, e.g. NOVA-12
minutes	integer	required	Minutes to add; a negative number corrects an over-count

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "description": "Task id, e.g. NOVA-12"
    },
    "minutes": {
      "type": "integer",
      "minimum": -100000,
      "maximum": 100000,
      "description": "Minutes to add; a negative number corrects an over-count"
    }
  },
  "required": [
    "id",
    "minutes"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

project_list

List every board with its task-id prefix, open and done counts, estimate still open and overdue count, plus free-tier use (3 boards, 200 open tasks). Use board for one board broken down by column.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

project_delete

Delete an empty board and give its free-tier slot back. A board still holding tasks, open or done, is refused with one named, because task_add creates boards as a side effect and the work would be lost.

Parameters1

project

string

required

Board to remove, e.g. 'Nova Site'. It must hold no tasks at all.

Raw schema

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "maxLength": 100,
      "description": "Board to remove, e.g. 'Nova Site'. It must hold no tasks at all."
    }
  },
  "required": [
    "project"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

overdue

List every task whose due day is already past, across all boards, oldest first, in the task_list table. as_of measures against a day you name. A finished task, or one with no due date, never counts.

Parameters2

as_of	string	optional	Measure against this day instead of today (YYYY-MM-DD, 'next Monday', '+7d')
limit	integer	optional	Rows to print; default 200

Raw schema

{
  "type": "object",
  "properties": {
    "as_of": {
      "type": "string",
      "maxLength": 64,
      "description": "Measure against this day instead of today (YYYY-MM-DD, 'next Monday', '+7d')"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 2000,
      "description": "Rows to print; default 200"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

weekly_review

Compare done against planned for one ISO week per project: how many were due, how many of those are finished, how many were completed, and estimate against actual minutes. Any week but this one is Pro.

Parameters1

week

string

optional

ISO week, e.g. '2026-W36'. Defaults to this week. Past weeks are a Pro feature.

Raw schema

{
  "type": "object",
  "properties": {
    "week": {
      "type": "string",
      "maxLength": 16,
      "description": "ISO week, e.g. '2026-W36'. Defaults to this week. Past weeks are a Pro feature."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

columns_set

Replace one board's columns, in order, with 2 to 12 unique names. Tasks in a removed column move to the FIRST column. Blanks are dropped first, so a list normalising below two names is refused. Pro.

Parameters2

project	string	required	Which board
columns	array	required	The new column names in order, at most 12, e.g. ['inbox','next','doing','done']

Raw schema

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "maxLength": 100,
      "description": "Which board"
    },
    "columns": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 40
      },
      "minItems": 2,
      "maxItems": 12,
      "description": "The new column names in order, at most 12, e.g. ['inbox','next','doing','done']"
    }
  },
  "required": [
    "project",
    "columns"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

servers/kanban/README.md7 KBView on GitHub

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

Install

Tools (17)

license_statuslicense_activatetask_addtask_listtask_movetask_updatetask_donetask_delete

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.zovo.one/mcp/task-board-todo-kanban

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "task-board-todo-kanban": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zovo.one/mcp/task-board-todo-kanban"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

MCP Server: io.github.theluckystrike/task-board-todo-kanban

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

Topics

license_status

license_activate

task_add

task_list

task_move

task_update

task_done

task_delete

task_search

board

task_start_timer

task_log_time

project_list

project_delete

overdue

weekly_review

columns_set

Run task boards from Claude with a free MCP kanban server

60-second install

Tools

What you can say

Free vs Pro

Pairs with

Privacy

License

Frequently asked questions

Is there an MCP kanban server?

How do I manage a kanban board from Claude?

Use these docs as an MCP server

Install

Remote endpoint

Related servers