Kin MCP server
{
"mcpServers": {
"kinlab": {
"command": "npx",
"args": [
"-y",
"@kinlab/kin-mcp@latest"
]
}
}
}{
"mcpServers": {
"kinlab": {
"command": "npx",
"args": [
"-y",
"@kinlab/kin-mcp@latest"
]
}
}
}{
"mcpServers": {
"kinlab": {
"command": "npx",
"args": [
"-y",
"@kinlab/kin-mcp@latest"
]
}
}
}{
"servers": {
"kinlab": {
"command": "npx",
"args": [
"-y",
"@kinlab/kin-mcp@latest"
]
}
}
}{
"mcpServers": {
"kinlab": {
"command": "npx",
"args": [
"-y",
"@kinlab/kin-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 @kinlab/kin-mcpversion 0.7.21
What it does
Kin is a semantic system of record for AI-written software that builds a graph of entities, relations, changes, and provenance to help humans and AI agents understand what code changes affect. It exposes this graph through a CLI, MCP server, and VS Code extension, allowing developers to query impact and context without re-reading repositories or waiting for compilation.
- Query what entities and dependencies a code change affects before it merges, using semantic graph analysis instead of diffs.
- Provide AI agents with exact context about the codebase structure and change impact through MCP tools, so they can write code with full awareness of consequences.
- Review code changes by exploring affected entities, callers, and transitive dependencies through graph queries rather than line-by-line diffs.
Tools this server exposes
| Tool | Does |
|---|---|
| trace | Trace dependencies and impact paths through the codebase graph. |
| rename | Perform semantic renaming operations across entities in the graph. |
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.