Filesystem-driven four-lane kanban board (todo / doing / blocked / done) exposed as a read-only MCP server and a Python API. Works with DeepSeek Harness and any MCP client.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"dsh-kanban-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# dsh-kanban-mcp > Filesystem-driven four-lane kanban board (todo / doing / blocked / done) exposed as a read-only MCP server and a Python API. Works with DeepSeek Harness and any MCP client. A kanban board is just a directory tree of markdown cards: ``` <base_dir>/YYYY/YYYY-MM/YYYY-MM-DD/{todo,doing,blocked,done}/YYYYMMDD-HHMMSS__agent__slug__status.md ``` That design is the whole point: the board survives restarts, is diffable in git, needs no database, and can be inspected by any file tool. This package manages those files and exposes the board to agents over MCP. ## Install ```bash pip install "dsh-kanban-mcp" # Python API pip install "dsh-kanban-mcp[mcp]" # + MCP server (fastmcp) ``` Requires Python 3.10+. ## Run the MCP server ```bash python -m kanban_mcp # stdio transport # or: kanban-mcp ``` Register it in **DeepSeek Harness** (MCP settings — the built-in MCP client) or any MCP client. The tools take an optional `base_dir` argument (default `.agent/kanban`) so one server can point at any board. ## Tools (read-only) | Tool | Description | |---|---| | `kanban_board` | Full four-lane board with card details (agent, work_item, purpose, status, outcome, priority, timestamps) | | `kanban_status` | Per-lane card counts + total | | `kanban_doing` | Cards currently in progress | | `kanban_blocked` | Blocked cards | | `kanban_done_today` | Cards completed today | All tools are read-only. Card **creation / update / movement** is available through the `KanbanManager` Python API (see below); write tools are planned but not yet exposed over MCP. ## Python API ```python from kanban_mcp import KanbanManager, LaneStatus kanban = KanbanManager(base_dir=".agent/kanban") card = kanban.create_doing_card( agent="coder", work_item="build-api", purpose="Build the REST API endpoint", ) kanban.update_card(card, outcome="GET /users implemented") kanban.move_to_done("coder", "buil…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.