Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Self-hosted kanban for humans and agents. One 4 MB binary, starts in 2 ms, zero setup.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
作者はレジストリにインストール情報を載せていません。下にある作者のREADMEをご覧ください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント emanuele-em で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.1.3)がレジストリに届いたのは11 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにRustも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drain unblocking, leak detection & plumbing in Varna, Bulgaria: services, prices, areas, contact
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
English | 简体中文
Kanzo is a kanban board in your browser and an MCP server in one 4.7 MB program, so you and your coding agents work on the same tasks: on one computer, or on one board shared by all of them. No account, no server, no setup: run kanzo and it works.
You never edit a file. Everything is done in one of three places:
[!TIP]
Just ask your agent: *"install Kanzo from github.com/emanuele-em/kanzo."*
curl -LsSf https://github.com/emanuele-em/kanzo/releases/latest/download/kanzo-installer.sh | sh
For macOS and Linux, including every Raspberry Pi. On Windows, in PowerShell:
powershell -ExecutionPolicy Bypass -c "irm https://github.com/emanuele-em/kanzo/releases/latest/download/kanzo-installer.ps1 | iex"
Both add Kanzo to your PATH, for terminals you open from then on. To use it in the one you installed from, run source $HOME/.cargo/env (env.fish in fish), or open a new one.
Or download the Windows zip from the latest release and put kanzo.exe in a folder named bin on your PATH, like %USERPROFILE%\.cargo\bin: the board updates itself only there.
Every release is signed by GitHub: check a download with gh attestation verify --repo emanuele-em/kanzo. Or with Cargo:
cargo install kanzo
[!TIP]
Just ask your agent: *"start Kanzo and keep it running at login."*
kanzo
The board opens at http://localhost:4242. That's all the setup there is: the first run creates ~/kanzo, and the whole board lives in it.
| Key | Does |
|---|---|
n | New task |
/ or ⌘K | Search every project |
f | Filter the board; ↵ keeps the filter |
Tab | Move to the description |
⌘↵ | Save and close |
Esc | Keep what you typed in a description or tags; cancel other fields |
[!TIP]
Just ask your agent: *"mark kanzo#12 as human, and set its URL to github.com/acme/api/pull/482."*
⌘-click them, or drag on empty board space, then move, tag or delete them together. Drag one and the rest follow.url.[name](file:///path) in a description or comment opens in your editor.⌘1–⌘8 pick a project, ⌘9 the last one, ⌘0 all of them. On macOS, kanzo then opens it instead of a tab, on the default port.[!TIP]
Just ask your agent: *"add Kanzo as your MCP server,"* then restart it.
claude mcp add kanzo --scope user -- kanzo mcp # Claude Code
codex mcp add kanzo -- kanzo mcp # Codex
Other MCP clients: run kanzo mcp (apps like Raycast need the full path, from which kanzo), or use the running board at http://localhost:4242/mcp.
Then ask: *"take the next task from kanzo and do it."* The agent:
doing and comments as it works;review, comments how to resume its session.Turn on Backlog in Settings for a column agents leave alone, until you move its tasks to todo.
[!TIP]
Just ask your agent: *"make kanzo#12 wait on #10 and #11."*
waits_on.next_task skips it, and its card is dimmed and says what it waits on. You can still move it yourself.done. A task in review still blocks.is:waiting.[!TIP]
Just ask your agent: *"take the next kanzo task tagged billing,"* or *"list what's left in kanzo with tag:billing."*
The board's filter (f), search (/) and the filter of list_tasks and next_task all understand the same words, like on GitHub:
- negates a qualifier: tag:billing -status:done.| Qualifier | Finds | Example |
|---|---|---|
tag: | that exact tag | tag:bug, tag:"needs review" |
status: | a column | status:doing |
project: | a project | project:api |
title:, description:, url:, comment: | text in that field | title:login, comment:"on hold" |
id:, comments:, images: | a number, or a range | id:12, comments:>2, images:1..3 |
created:, updated: | a date, or a range | created:2026-11-05, updated:<2026-01-31 |
is:human | tasks for you, not agents | -is:human |
is:waiting | tasks waiting on unfinished ones | -is:waiting |
has:, no: | description, tags, url, comments or images | has:url, no:tags |
Anything else is plain text. Use quotes for a phrase, "on hold", or to look for text that reads like a qualifier, "tag:bug". Agents can't filter through a property you've hidden in Settings.
Two ways, neither with any setup: share one board live, or sync it between machines.
[!TIP]
Just ask your agent: *"share my Kanzo board"* on one computer, and *"join the Kanzo board at 192.168.1.20"* on the others.
Several computers, one board, at the same time: everyone sees the same tasks, and every agent works on them.
Nothing restarts and nothing needs configuring. Their board shows the shared one, and their agents use it through the same kanzo mcp, still finding the project from the repo they work in. Turn sharing off, or click Leave, at any time.
From a terminal, or for an agent, it's kanzo share on and kanzo join , then kanzo share off and kanzo leave.
The same two commands work wherever the board lives; only the address changes:
Your computer shares its board. Others join it from theirs, on the same network.
flowchart LR
B["💻 Laptop B kanzo#nbsp;join#nbsp;192.168.1.20 "] -- home network --> A["💻 Laptop A 192.168.1.20 kanzo#nbsp;share#nbsp;on "]
A Raspberry Pi keeps the board. Every computer joins it, and none has to stay on.
flowchart LR
A["💻 Laptop A kanzo#nbsp;join#nbsp;192.168.1.50 "] -- home network --> pi["🍓 Raspberry Pi 192.168.1.50 kanzo#nbsp;share#nbsp;on "] B["💻 Laptop B kanzo#nbsp;join#nbsp;192.168.1.50 "] -- home network --> pi
The Raspberry Pi is somewhere else, over the internet. Put a VPN on the Pi and on each computer, like Tailscale, NetBird or WireGuard: kanzo share on then shows the Pi's VPN address too.
flowchart LR
A["💻 Laptop A kanzo#nbsp;join#nbsp;100.101.32.7 "] -- VPN --> net(("🌐 Internet")) B["💻 Laptop B kanzo#nbsp;join#nbsp;100.101.32.7 "] -- VPN --> net net -- VPN --> pi["🍓 Raspberry Pi 100.101.32.7 kanzo#nbsp;share#nbsp;on "]
On a Pi, kanzo service install keeps the board running after a restart. There are no logins: share only on a network you trust.
[!TIP]
Just ask your agent: *"sync my Kanzo board,"* or the first time, *"set up Kanzo sync with github.com/you/kanzo-data."*
To carry the board between machines you use one at a time, a private git repo you own keeps it in step.
~/kanzo a git repo and pushes the board.From then on, choose Sync, or run kanzo sync, when you switch machines. It commits the board and pulls or pushes it, and it's safe while the board and your agents are running. If both machines changed the board, Kanzo asks which one to keep. To move to another repo, change it in Settings, under Sync.
| Command | Does |
|---|
| kanzo | Starts the board at http://
冒頭だけを表示しています。続きはリポジトリで読めます