프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Kanzo

제작자: emanuele-em버전 0.1.3i★ –i내 컴퓨터에서 실행
레지스트리 이름io.github.emanuele-em/kanzo

설치

개요

제작자가 쓴 설명(영어 원문)

Self-hosted kanban for humans and agents. One 4 MB binary, starts in 2 ms, zero setup.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: stdio
  • 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

  • 기본 점검: 1개 중 1개 통과
  • 내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
  • 레지스트리에 입력해야 할 키가 나와 있지 않아요.

제작자가 레지스트리에 설치 정보를 올리지 않았어요. 아래 제작자의 README를 확인하세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 emanuele-em 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • – 해당 없음

    엔드포인트 응답

    내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요

  • – 해당 없음

    OAuth로 로그인

    내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 32686개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 32686개 중 76%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 32686개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Kanzo, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.3)은 11일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Rust도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Microsoft Exchange Online MCP

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211그저께 업데이트
설치

Microsoft Exchange Online MCP

제작자: servosity

Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell

내 컴퓨터에서 실행오늘 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. 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:

  • the board, in your browser, for you;
  • MCP, for your agents: they take tasks, move cards and comment;
  • the `kanzo` command, for the terminal and scripts.

Install

[!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

Start

[!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.

KeyDoes
nNew task
/ or ⌘KSearch every project
fFilter the board; ↵ keeps the filter
TabMove to the description
⌘↵Save and close
EscKeep what you typed in a description or tags; cancel other fields

Use the board

[!TIP]

Just ask your agent: *"mark kanzo#12 as human, and set its URL to github.com/acme/api/pull/482."*

  • Select tasks: ⌘-click them, or drag on empty board space, then move, tag or delete them together. Drag one and the rest follow.
  • List view: the list icon shows the same tasks as rows to sort and group.
  • Human tasks: mark a task Human and agents leave it to you. The person icon shows only those.
  • Images: paste or drop one into a task or a comment.
  • Links: give a task a URL, like its pull request, and open it from its card. Agents set it with url.
  • Files: [name](file:///path) in a description or comment opens in your editor.
  • Task panel: drag its left edge to resize it, or expand it to the whole window. Double-click the edge to reset it.
  • Sidebar: the panel button beside search folds it to its icons. Drag a project to reorder the list, for everyone on a shared board.
  • App: in Chrome or Edge, Install app at the bottom of the sidebar makes the board an app of its own. ⌘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.
  • Updates: when a new version is out, the sidebar offers it. One click installs it.

Connect your agents

[!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:

  • finds the project from the git remote of its repo; link more repos from the project's ⋯ menu;
  • moves the card to doing and comments as it works;
  • on review, comments how to resume its session.

Park ideas in a backlog

Turn on Backlog in Settings for a column agents leave alone, until you move its tasks to todo.

Make a task wait on others

[!TIP]

Just ask your agent: *"make kanzo#12 wait on #10 and #11."*

  • Set it: type in Waits on, in a task's panel, to find tasks in its project and pick them. Agents pass waits_on.
  • Until those tasks are done: next_task skips it, and its card is dimmed and says what it waits on. You can still move it yourself.
  • What counts: only done. A task in review still blocks.
  • Find them: filter by is:waiting.

Filter and search

[!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:

  • Every part must match.
  • - negates a qualifier: tag:billing -status:done.
  • Qualifiers turn blue as you type them.
QualifierFindsExample
tag:that exact tagtag:bug, tag:"needs review"
status:a columnstatus:doing
project:a projectproject:api
title:, description:, url:, comment:text in that fieldtitle:login, comment:"on hold"
id:, comments:, images:a number, or a rangeid:12, comments:>2, images:1..3
created:, updated:a date, or a rangecreated:2026-11-05, updated:<2026-01-31
is:humantasks for you, not agents-is:human
is:waitingtasks waiting on unfinished ones-is:waiting
has:, no:description, tags, url, comments or imageshas: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.

Use it on several computers

Two ways, neither with any setup: share one board live, or sync it between machines.

Share it live

[!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.

  1. On the computer with the board, click the share icon next to New task and turn on Share this board. Copy an address it shows.
  1. On each other computer, click the share icon, paste the address and click Join.

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.

Sync it between machines

[!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.

  1. Create an empty private repo on GitHub, or anywhere git can push.
  2. Click Settings at the bottom of the sidebar, choose Sync and paste its URL. Kanzo makes ~/kanzo a git repo and pushes the board.
  3. On each other machine, do the same with the same URL: Kanzo offers to use the board that's already there.

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.

Commands

CommandDoes

| kanzo | Starts the board at http://

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기