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.
Sixteen tools against Cascade's ceiling of 100, and a board is read constantly through a work session, so it earns its seat more than a server you touch once a week.
| 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 mcp_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS, Windows and Linux | ~/.codeium/windsurf/mcp_config.json |
If you also run Claude Desktop, the shortest path there is one click: kanban.mcpb
from the bundle catalog opens as an extension, with no JSON and no terminal.
Windsurf reads its own config, so here it is:
The config block:
{
"mcpServers": {
"kanban": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/kanban/dist/index.js"]
}
}
}
The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/kanban
That writes servers/kanban/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
{
"mcpServers": {
"kanban": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-kanban"]
}
}
}
Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/kanban over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"kanban": {
"url": "https://mcp.zovo.one/mcp/kanban",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.
Free: 3 project boards, 200 open tasks, the default five columns. Pro is $19 once, verified offline.
~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.
That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.
Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Kanban contributes 16 tools, so keep the enabled list short rather than counting servers.
MCP Kanban in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs · Buy Pro
Run a kanban board in Claude, with time tracking on the same task · Work orders and job cards from chat, and why the markup goes on the unit cost