Task Board Todo Kanban MCP server

• boardFree

  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.

• columns_setFree

  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.

• license_activateFree

  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.

• license_statusFree

  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.

• overdueFree

  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.

• project_deletewrite actionFree

  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.

• project_listFree

  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.

• task_addFree

  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.

• task_deletewrite actionFree

  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.

• task_doneFree

  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.

• task_listFree

  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.

• task_log_timeFree

  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.

• task_moveFree

  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.

• task_searchFree

  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.

• task_start_timerFree

  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.

• task_updatewrite actionFree

  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.

• weekly_reviewFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 611ms20/20
• Tool poisoning17 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

88/100

higher than 75% of 1,299 Productivity servers

Tools

17

the typical Productivity server has 7

Tools that change things

18%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Productivity server answers 100%

Response time

10 ms

faster than 99% of 655 Productivity servers

Task Board Todo Kanban: common questions

Is Task Board Todo Kanban MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Task Board Todo Kanban safety report

How do I install Task Board Todo Kanban?

It runs remotely at mcp.zovo.one. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Task Board Todo Kanban need an API key?

Yes. The registry entry asks for Authorization.

Is Task Board Todo Kanban maintained?

The last commit was 39 days ago (2026-09-26). The latest release is v0.23.2.

Is Task Board Todo Kanban up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Task Board Todo Kanban?

Servers from other publishers that do the same job: Remnus MCP server, chat-recall MCP server and Trello MCP server.

How does Task Board Todo Kanban compare with other Productivity MCP servers?

safety score 88/100 (higher than 75% of 1,299 Productivity servers); tools 17 (the typical Productivity server has 7); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.