Kawa Code vs IWE
A side-by-side look at the Kawa Code and IWE MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kawa Code for knowledge & memory work as a local process; choose IWE for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kawa Code when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose IWE when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 40/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1,790 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Kawa Code | View IWE |
Tools & capabilities
Kawa Code tools
No tool names declared yet. Check the project README from the listing page.
IWE tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kawa Code
{
"mcpServers": {
"kawa-code": {
"command": "npx",
"args": [
"-y",
"@kawacode/mcp"
]
}
}
}
IWE
No confirmed install command for IWE yet — follow the setup steps linked from its listing page rather than a guessed package name.