1. Conduid
  2. Developer Tools
  3. Kawa Code MCP
MCP server · Developer Tools

Kawa Code MCP

Intent tracking, decision recording, and team coordination for AI coding assistants

Unclaimed devtools
37Low

Scored 6 months ago · breakdown

About Kawa Code MCP

Kawa Code MCP is an MCP server in the Developer Tools category: intent tracking, decision recording, and team coordination for AI coding assistants.

Install

Claude Code
claude mcp add kawa-code-mcp -- npx -y @kawacode/mcp
npx
npx -y @kawacode/mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Kawa Code MCP

Powered by Claude · Grounded in docs

I know everything about Kawa Code MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

kawa.mcp

Reference implementation of the Kawa Code MCP protocol.

Overview

The Kawa Code MCP server provides the communication layer used by Kawa Code to record and align development intent between developers and AI systems.

It enables:

• Persistent AI reasoning context • Intent tracking during development workflows • Alignment between human and AI decisions over time

This repository contains the reference implementation of the Kawa MCP server used by Kawa Code tools.

This MCP server enables AI coding assistants to understand what you're working on and maintain context across sessions. It connects to the Kawa Code desktop application to provide:

  • Intent tracking: Create and manage development intents with decision history
  • Team collaboration: See what teammates are working on, detect conflicts
  • Decision recording: Track architectural decisions and trade-offs with constraint validation
  • Code block assignment: Associate code changes with intents for better commit history

Prerequisites

Required

  • Node.js >= 18.0.0 — runtime for the MCP server
  • Kawa Code desktop app running — kawa.mcp is a thin MCP-to-IPC adapter; all git operations, storage, and API communication happen in Kawa Code

Optional (for history inference)

  • Anthropic API key — your own Claude API key, passed as a parameter to the inference tools
  • GitHub CLI (gh) — enables richer data tiers (PR descriptions, review comments, issue discussions). Without gh, tiers 2 and 4 are skipped automatically

Installation

Add the MCP in your AI configuration, for example on Claude Code:

claude mcp add -s user kawa-intents -- npx -y @kawacode/mcp

For Cursor AI, install the MCP with npm install -g @kawacode/mcp and add it to ~/.cursor/mcp.json.

{
  "mcpServers": {
    "kawa-intents": {
      "command": "kawacode-mcp"
    }
  }
}

Note that the MCP will not be automatically updated to future versions in this scenario. To upgrade to a newer release, run npm update -g @kawacode/mcp.

Manual Installation

For the project you want Kawa Code to run on, create a .mcp.json file in your project root (recommended for teams — commit it to git):

{
  "mcpServers": {
    "kawa-intents": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@kawacode/mcp"]
    }
  }
}

Usage

The MCP server works together with the Kawa Code application, Kawa Code IDE extensions, and AI code generators such as Cursor AI and Claude Code.

Key Features

  • Context Persistence: Never lose track of what you were working on across AI sessions
  • Smart Context Retrieval: Relevance-based context loading - only fetch what's needed for the current task
  • Zero-Knowledge Encryption: Code blocks encrypted client-side before cloud sync, API cannot decrypt
  • Team Conflict Detection: Know when teammates are working on the same files/lines
  • Decision Tracking: Record architectural decisions with constraint validation and conflict detection
  • Commit Integration: Link all code changes to intent context for better git history
  • Cross-Platform: Works with Claude Code and Cursor AI via MCP protocol

Development

# Watch mode (auto-rebuild on file changes)
npm run dev

# Build TypeScript to JavaScript
npm run build

# Clean build artifacts
npm run clean

# Run the MCP server directly
npm start

Testing the MCP Server

To test the MCP server without integrating it into an AI assistant:

  1. Build the project: npm run build
  2. Run the server: npm start
  3. The server communicates via stdio (standard input/output)
  4. You can send MCP protocol messages via stdin to test tool functionality

Development Tips

  • Use npm run dev to auto-rebuild during development
  • Check stderr for server logs (stdout is reserved for MCP protocol)
  • Ensure Kawa Code is running before testing

Architecture

Claude Code / Cursor AI
    ↓ MCP Protocol (stdio)
kawa.mcp (this server)
    ↓ Huginn IPC (Unix socket / Named pipe)
Kawa Code Desktop App
    └─ HTTP Client
        ↓ REST + SSE
    Kawa API (cloud)
        └─ Team sync & zero-knowledge encryption

Contributing

Contributions are welcome. Please read CONTRIBUTING.md and CLA.md.

License

This project is source-available under the Kawa Code Source Available License.

You may run and modify the software for personal or internal use.

See LICENSE for details.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Kawa Code MCP

How do I install Kawa Code MCP?

Run claude mcp add kawa-code-mcp -- npx -y @kawacode/mcp, then add the server to your MCP client's configuration.

Is Kawa Code MCP safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Kawa Code MCP still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.