Kawacode MCP server
{
"mcpServers": {
"kawa-intents": {
"command": "npx",
"args": [
"-y",
"@kawacode/mcp@latest"
]
}
}
}{
"mcpServers": {
"kawa-intents": {
"command": "npx",
"args": [
"-y",
"@kawacode/mcp@latest"
]
}
}
}{
"mcpServers": {
"kawa-intents": {
"command": "npx",
"args": [
"-y",
"@kawacode/mcp@latest"
]
}
}
}{
"servers": {
"kawa-intents": {
"command": "npx",
"args": [
"-y",
"@kawacode/mcp@latest"
]
}
}
}{
"mcpServers": {
"kawa-intents": {
"command": "npx",
"args": [
"-y",
"@kawacode/mcp@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @kawacode/mcpversion 8.1.0
What it does
Kawacode is an MCP server that connects AI coding assistants to Kawa Code, a team-aware memory system for tracking coding intent, architectural decisions, and real-time collaborator activity. It surfaces conflicts before they happen and maintains context across sessions and machines.
- Check for real-time team conflicts by seeing which teammates are currently editing the same files or functions before you commit.
- Preserve architectural decisions and their rationale across coding sessions so future AI interactions and team members understand the reasoning behind past choices.
- Link commits to their original intent automatically, so git history includes not just what changed but why it changed.
Tools this server exposes
| Tool | Does |
|---|---|
| record_decision | Capture architectural decisions with their reasoning, optionally marking decisions as forks that supersede prior decisions. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.