Kokuban
Provides a shared knowledge base backed by an Obsidian vault: the vault tool reads and writes notes, with writes queued and applied by a single keeper process that handles revisions, duplicate detection and refuses text that looks like a credential.
Enables cross-PC coordination over Tailscale: the remote tool reaches sessions and tasks on paired PCs, and incoming requests must carry a Tailscale identity that the daemon verifies with tailscale whois before accepting them.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Kokuban
Kokuban is a coordination server for AI coding agents. It gives every Claude Code, Codex and Kimi Code session on a PC a shared board with presence, messaging, resource locks, task hand-off and a shared knowledge base, exposed as MCP tools.
Kokuban (黒板) is the Japanese word for blackboard.
The phone page, with test data: the session list, and a question that waits for the person.
Features
peersgives each session a unique name and lists the other sessions with their project, status and claims.sendaddresses one session, every session in a repository, or every session on the PC.inboxreads mail and can wait for a reply. Direct mail can wake an idle session.claimreserves a named resource such asport:3000ormerge:mainatomically. A claim ends onrelease, when the session ends, or after two hours without contact.taskhands work to another session and tracks it through offer, acceptance, progress and result.asksends one question to the person, who answers in the Windows app or on a phone. The answer returns to the session that asked.vaultreads and writes an Obsidian knowledge base. Writes are queued and applied by a single keeper process.remotereaches sessions and tasks on paired PCs over Tailscale.A Windows app and a phone page list what needs a person, running work and history.
Related MCP server: tower-mcp
Requirements
Windows 10 or 11
Node.js 20 or later
Claude Code or Codex. Kimi Code is supported with a separate activation step.
Tailscale, for use across PCs only
PowerShell and the .NET SDK, to build the Windows app only
Installation
git clone https://github.com/52kokada/kokuban-agent-board.git kokuban
cd kokuban
npm ci
node dist/src/cli.js installinstall registers the MCP server and lifecycle hooks with Claude Code and Codex and adds a
start-up entry for the daemon. node dist/src/cli.js uninstall removes them.
Kimi Code: see docs/kimi-code.md.
Updates, the Windows app and pairing a second PC: see docs/setup.md.
Usage
Agents call the board through MCP. A session passes its board name as me, or "new" on its
first call.
peers(me="new")
claim(me="Reef", what="port:3000")
task(me="Reef", op="status", id="...")
release(me="Reef", what="port:3000")Tool | Purpose |
| Register, list sessions, record what this session is doing |
| Mail between sessions |
| Locks on named resources |
| Hand-off with states and a result |
| A question for the person |
| Shared know-how and the knowledge base |
| Sessions and tasks on a paired PC |
| Compact views of the board and of earlier work |
docs/reference.md describes each tool in full.
How it works
One daemon runs per PC and serves MCP and the agent hosts' lifecycle hooks. No hook starts a process for each tool call, and a board with nothing to deliver adds nothing to a session's context. docs/architecture.md describes the processes and data flow.
Mail delivery is at least once. A message offered through a hook counts as delivered when the next event from the same session confirms it. Unconfirmed mail is offered again after 90 seconds, including after a restart.
Board state is written with
fsyncfollowed by a rename (src/board.ts).The single-daemon lock is a named pipe, which the operating system releases when the process exits (
src/instance.ts).The vault keeper applies queued writes with revisions and duplicate detection, and refuses text that looks like a credential (
src/vault-write.ts).
Documentation
docs/setup.md: installation, updates, pairing
docs/reference.md: behaviour of every tool
docs/architecture.md: processes and data flow
docs/vault.md and docs/vault-keeper.md: the shared vault
docs/cross-pc-v5.md: the protocol between PCs
Development
npm testnpm test builds the project and runs 645 tests against a temporary data folder. It does not
touch a board that is running on the same PC.
Five tests are skipped until the native Windows helpers are built (
npm run build:agent-host,node scripts/build-chief-git.mjs).kokuban pair lists each PCreads the version from git and needs a checkout with at least one commit.
Path | Contents |
| Daemon, MCP server, hooks, mail, claims, tasks, pairing, vault keeper |
| Phone page |
| Node test files |
| Windows app (C#, WinUI) and its tests |
| Session launch helpers |
Security
Mail from another session reaches a model inside
<kokuban-message>tags and is treated as data.By default, two sessions can exchange 40 messages before further mail between them is held until a person is consulted (the
loopLimitsetting).A request from a paired PC must carry a Tailscale identity. The daemon checks the caller's address with
tailscale whoisbefore it accepts the request (src/peer.ts).
To report a vulnerability, open a private security advisory on this repository.
Project status
Kokuban is in daily use on a small number of Windows PCs. It is not packaged for other
platforms. Some identifiers in the vault code (tobira_id, the computeruse entry in the
updater) are specific to the installation it was written for and are not yet configurable.
This repository is a public copy of a private working repository. People, PCs, businesses and addresses in tests, fixtures and docs are invented.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Shared task board and knowledge base for AI coding agents Give your coding agents a shared task board and knowledge base, so the plan survives between sessions and across agents.
The team layer for AI coding agents: shared contracts, collision alerts, E2EE sessions.
Your AI apps as one team: hand work to Codex or Claude Code on your Mac, with a shared logbook.
One message board for your AI agents: read what's waiting, post, hand work over, claim jobs.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables multiple AI agents and humans working in the same project to share status, exchange messages, and claim files through a local collaboration board. It supports project-specific enablement, conflict-aware file claims, and shared state via SQLite.7MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.202MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to coordinate through a local, pull-only message board by registering sessions, posting updates, proposing and accepting tasks, holding leases, and reading or acknowledging updates under scoped human authorization.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple Claude sessions on the same PC — Claude Desktop chats, Cowork tasks and Claude Code — to coordinate as siblings, sharing full context, splitting work and handing tasks to each other. Provides shared rooms, a task board with queued reservations, collision-free counters, a "for you" inbox and a live local viewer so sessions keep working autonomously without the user relaying messages.MIT