Kawa Code — Claude Code MCP server: team memory and conflicts
Gives your coding assistant team memory: what you are building, why a choice was made, and who else is editing the same file right now.
claude mcp add mcp -- npx -y @kawacode/mcpWhat Kawa Code does
@kawacode/mcp sits between the assistant and the Kawa Code desktop app. Git work, storage and syncing all happen inside that app, so the server is useless unless Kawa Code is running. Node.js 18.0.0 or newer is required.
What you get in practice: the assistant carries context across sessions, branches and machines. Decisions get recorded along with the reasoning behind them, and commits are tied to the task that produced them. A conflict shows up before anyone commits — if a teammate has the same files open in their working copy, you hear about it. An Anthropic API key is optional and feeds history inference. Installing gh unlocks deeper data such as pull request descriptions and issue threads; without it, two tiers are skipped.
On Claude there is an optional PreToolUse hook matched to Edit|Write. It surfaces earlier reasoning before a change lands, and can block the edit. To get past a block, record a new decision via record_decision with supersedes, or pass force: true for a one-off. Turn the hook off with KAWA_PRE_EDIT_CHECK=off. Telemetry stays on your machine under ~/.kawa-code/logs/ and is disabled with KAWA_PRE_EDIT_TELEMETRY=off. A global npm install does not update itself — pull a newer release with npm update -g @kawacode/mcp.
What it helps with
- spot a teammate editing the same file before either of you commits
- keep the reasoning behind an architectural choice for later sessions
- attach the originating task to each commit
- carry decision history into a rewritten repository
- stop an edit when recorded constraints already cover the file
Example prompts for the agent
- What is in progress in this repo, and which decisions are already recorded?
- Who on the team has
src/router.tsopen right now? - Record a decision: we are replacing the old client because it cannot handle the load
How to install Kawa Code
Platform CLI
claude mcp add mcp -- npx -y @kawacode/mcpPlatform CLI
codex mcp add kawa-code -- npx -y @kawacode/mcpConfig file
{
"mcpServers": {
"kawa-code": {
"command": "npx",
"args": [
"-y",
"@kawacode/mcp"
]
}
}
}Config file
{
"servers": {
"kawa-code": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@kawacode/mcp"
]
}
}
}Platform CLI
gemini mcp add kawa-code npx -y @kawacode/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Kawa Code
How do I install Kawa Code in Claude Code?
Run claude mcp add kawa-code -- npx -y @kawacode/mcp. Start the Kawa Code desktop app first and make sure Node.js 18.0.0 or newer is installed.
What does Kawa Code do?
It gives the assistant team memory: active tasks, decision history with reasoning, and who else is touching the same files. It runs on top of the desktop app.
What is the PreToolUse hook for?
It fires before Edit or Write and shows the reasoning recorded for those files. Depending on the record, the edit proceeds, gets context to review, or is blocked.
