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.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
作者没有在注册中心列出安装信息。请查看下方作者的 README。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 emanuele-em 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.3)于11天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Rust。
同一分类中有:Spec Driven Development, Remote Desktop Commander, NexusWindows
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况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.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
按原文从作者的仓库复制。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://
只显示了开头部分;其余内容请在仓库中阅读