Kin

Name: Kin
Author: LLM Mart

No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.

Kin is a graph-native code repository for people and AI agents. It stores source, recorded code relationships, and versioned history as repository state. The graph is the repository model, not a search index maintained beside another repository.

Functions, types, and the relationships between them are data you commit, branch, and merge. Exact source is preserved byte for byte, and filesystem projections let supported tools keep working with ordinary files.

Public alpha. Start with a small repository you know well. Expect rough edges and breaking changes.

Quickstart · Documentation · Browser demo

kin impact human_bytes --file crates/kin-cli/src/commands/cache.rs --kind function --depth 1, showing its direct callers in Kin's own codebase next to a git grep search for the same name

A star helps other people find Kin, and Discussions is where to bring a question about it.

See what connects

Before changing a shared function, what else should you inspect? Kin lets you look up its recorded callers and explore related code. The CLI and MCP server query the same graph, so you and your agent can work from the same record.

A recorded kin impact query on ripgrep, showing related entities for a signature change

Recorded on a prepared ripgrep graph at e89fff89ac9af12e8d4ce9d5fd07beb408ca730f. Raw run artifacts are not public. This illustrates a workflow, not a performance benchmark.

Use it from Claude Code, Codex or Cursor

For Claude Code:

/plugin marketplace add firelock-ai/kin
/plugin install kin@kin

For Codex, add the marketplace and install the plugin, or let kin setup --intent agent write the MCP server into ~/.codex/config.toml for you.

For Cursor, add the MCP server by hand; see plugins/kin-cursor for the exact snippet.

After installing, run kin init . in a small repository you know well; the kin-setup skill walks you through the rest.

Kin is not published on crates.io. The kin crate there is an unrelated project.

Quickstart

Use a disposable copy of a small Git repository. Import includes its full reachable history and can take substantial time and memory. Shallow clones, submodules, and Git LFS are not supported.

1. Install

One command, and it is the same on macOS, Linux, Windows and WSL. It installs Kin, connects the AI coding tools it finds, and needs Node.js 20 or newer:

npx -y @kinlab/kin setup

On a machine without Node, run the installer instead. get.kinlab.ai and get.kinlab.dev serve the same script:

curl -fsSL https://get.kinlab.dev/install | sh

Either way, reload your shell as a separate command, because the install puts kin in ~/.kin/bin and adds that directory to your shell profile for new sessions:

exec "$SHELL" -l

For Windows PowerShell, other installers, or troubleshooting, see the full quickstart.

2. Initialize the repository

At the new prompt, replace the path below:

cd /path/to/your/repository &&
kin init . &&
kin overview &&
kin status

kin overview shows the entities Kin imported. kin status shows what was admitted and the working tree's state against it. kin graph status reports the daemon's live query graph and coverage. Uncommitted and untracked changes are not part of the imported Git history; kin init reports what it left out.

3. Ask a question you can check

Look for something you already know is in the code:

kin locate "<something you already know is in this repository>"

Replace ExactEntityName below with a symbol from the result: