Log inSubmit server
Kawa Code MCP logo

Kawa Code MCP

Tracks coding intent, architectural decisions, session context, and overlapping team edits through Kawa Code.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Kawa Code MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kawa-code-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@kawacode/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 20 tools correctly (29d ago).

Overview

Kawa Code MCP MCP server connects MCP-compatible coding assistants to the Kawa Code desktop application for shared memory and coordination. It tracks intent across sessions, records decisions with their reasoning, links commits to intent, and reports overlapping uncommitted edits from teammates. Install it as a Node.js stdio server through npx or a global npm package, with Kawa Code running locally. Reach for it when multiple developers or agents need shared repository context and early warning about conflicting work.

Use cases

  • Resume coding work across sessions and branches
  • Record architectural decisions for future agents
  • Detect overlapping teammate edits before committing
  • Coordinate parallel agents in separate Git worktrees

Key features

  • Cross-session intent and context memory
  • Decision recording with reasoning
  • Pre-commit team conflict detection
  • Commit-to-intent linkage
  • Relevance-based context retrieval
  • Client-side encryption for synced code blocks

Tools20

What Kawa Code MCP lets your agent do. Expand a tool for its parameters.

Verified live~8.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

21/21 checks healthy over the last 90d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @kawacode/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed20Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Kawa Code MCP works

What Kawa Code MCP does

Kawa Code MCP MCP server gives AI coding assistants access to team-aware repository context through the Kawa Code desktop application. It helps an assistant continue work across sessions, branches, and machines without reconstructing the project background each time. It also stores architectural decisions together with their reasoning, so later sessions can review the choices behind the current code.

The coordination features cover active work as well as historical context. Agents and teammates can see overlapping in-progress edits in working copies before either change is committed. Commits are associated with the intent that motivated them, adding rationale alongside the changes shown by Git.

How it works

The package is an MCP-to-IPC adapter. Kawa Code performs the Git operations, data storage, and API communication, while the MCP process exposes that functionality to an AI assistant. The setup therefore depends on the Kawa Code desktop application being open for the project.

Context retrieval is relevance-based rather than loading every recorded item. The documented get_relevant_context capability can surface information related to the current task. Intent tracking is session-specific, allowing several agents to work on one repository with separate active focuses.

For parallel agent work, each worker should use its own Git worktree. Separate worktrees prevent agents from overwriting one another without Git being able to represent the conflict. Kawa's coordination features then report overlapping edits across those working copies. The live edit-level signal is provided by the Stop hook; the former pre-edit decision-check hook was retired on August 14, 2026.

Setup and configuration

Kawa Code MCP MCP server requires Node.js 18 or later and a running Kawa Code desktop application. A project-level .mcp.json can run it with npx -y @kawacode/mcp, which is suitable for committing shared configuration to a repository. Claude Code can add the same package with its MCP command. Cursor can use a global installation and a kawacode-mcp command in ~/.cursor/mcp.json.

A global npm installation does not update itself. Upgrade it with npm update -g @kawacode/mcp. An Anthropic API key is optional and is passed to history-inference tools as a parameter. Installing GitHub CLI is also optional; it enables richer history sources such as pull request descriptions, review comments, and issue discussions. Without it, the corresponding data tiers are skipped.

Tools and capabilities

  • Maintains intent and context across sessions, branches, and machines.
  • Records architectural decisions, trade-offs, and abandoned approaches with their reasoning.
  • Retrieves task-relevant context instead of requiring all history to be loaded.
  • Detects teammates editing overlapping files or lines before commits create merge conflicts.
  • Associates commits with the intent behind them.
  • Supports safe-tier overlap resolution when operating in an agent-owned worktree.
  • Encrypts code blocks client-side before synchronization; Kawa cloud cannot decrypt that code.

Limitations and notes

Kawa Code MCP MCP server does not replace the Kawa Code desktop application: the application must be running, and it owns storage, Git operations, and API communication. Agents sharing one checkout can still overwrite one another without conflict markers, so worktrees are required for isolated parallel agent sessions.

The retired pre-edit hook should not be newly configured. Existing installations continue to work until removed manually, but current edit coordination uses the Stop hook. Compiled-language build output should not be shared between worktrees through symlinks because separate checkouts can overwrite the same artifacts. GitHub CLI and the Anthropic API key extend optional history features but are not required for the base MCP process.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Kawa Code MCP

Kawa Code MCP is an MCP server that connects Claude Code, Cursor, and other MCP-compatible assistants to the Kawa Code desktop app. Its main tools support intent tracking, relevant-context retrieval, decision recording, commit-to-intent links, and detection of overlapping uncommitted edits across teammates or agent worktrees.

Install it with Node.js 18 or later using `npx -y @kawacode/mcp` in an MCP configuration. You can add it through Claude Code, use a project `.mcp.json`, or install `@kawacode/mcp` globally for Cursor. Kawa Code desktop must also be running.

Yes, Kawa Code MCP works with Cursor. Install `@kawacode/mcp` globally with npm and add a `kawacode-mcp` command entry to `~/.cursor/mcp.json`; the Kawa Code desktop application must be running.

Kawa Code detects overlapping in-progress, uncommitted edits across working copies and reports the overlap through the Stop hook. Each parallel agent should use its own Git worktree; agents sharing one checkout can overwrite changes without a detectable Git conflict.

No, GitHub CLI is optional. Installing `gh` enables richer history data such as pull request descriptions, review comments, and issue discussions; without it, those history tiers are skipped automatically.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKawa Code MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kawa-code-mcp?style=directory)](https://allmcps.com/mcp/kawa-code-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/kawa-code-mcp"><img src="https://allmcps.com/api/badge/kawa-code-mcp?style=directory" alt="Kawa Code MCP on AllMCPs" /></a>