Kin

MCP开发工具

提供方 Troy Fortin, Jr. (Firelock, LLC) · 包名 @kinlab/kin-mcp

开发工具 stdio · 本地进程 会话登录 社区 / 第三方 ClaudeCursorVS CodeGemini CLI
查看接入方式

The system of record for AI-written software. A persistent graph of entities, relationships, changes, and provenance, so humans and AI agents see what a change touches before it merges. Beside Git today.

一句话选型结论

按资料字段整理

Kin 属于开发工具类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

code searchsemantic searchcode review

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
npx -y @kinlab/kin-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 rust,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Kin当前 未标注 stdio · 本地进程 本地部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Troy Fortin, Jr. (Firelock, LLC)上游标注的维护方 Troy Fortin, Jr. (Firelock, LLC)
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@kinlab/kin-mcp · rust本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

9.7 KB
来自项目仓库与上游目录的原文,未做删改

A new foundation for code.

Kin is a graph-native code repository for AI agents and the people who build with them. 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 beta. Try Kin on a real project you know well. Expect rough edges.

Quickstart · Documentation · Browser demo

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.

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 kinlab-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 fresh clone of a project 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

Start in a fresh, full clone of a project you know well. `kin init` reads your Git history without changing it or your tracked files. It keeps its store outside your checkout, in `~/.kin/stores`, and writes nothing into the repository; `kin store path` prints where a checkout's store is. By default it admits the checked-out commit first, so questions answer as soon as that tree is read, and then imports every commit your branches and tags reach in the background, at low priority; `kin init --history full` imports the whole history up front, and `--history none` never imports it. Importing history takes time, memory and disk that grow with history rather than with the size of the checkout. Before it starts, `kin init` checks memory and free disk and stops with the numbers when it can already tell the machine is short. **A shallow clone admits only its checked-out commit, and submodules and Git LFS are not supported**, and Git hooks, a sparse checkout or an unfinished merge or rebase also stop the import. `kin init` names the fix for each, and a fresh clone avoids most of them.

### 1. Install

On macOS, Linux and WSL2, one command installs Kin and connects the AI coding tools it
finds. It needs Node.js 20 or newer:```sh
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:```sh
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:```sh
exec "$SHELL" -l

On native Windows x64, install from PowerShell with irm https://get.kinlab.dev/install.ps1 | iex.
It installs the kin CLI and does not connect AI coding tools, because WSL2 remains the
recommended path on Windows. The Windows entry under Beta limits
says what works there. No native Windows ARM64 build is published. On an ARM64 machine, run
that line from x64 PowerShell to install the x86_64 build under emulation, or use WSL2.
The installer adds kin to your user PATH, so open a new PowerShell window in place of
exec "$SHELL" -l before the next step.

For other installers or troubleshooting, see the full quickstart.

2. Initialize the repository

At the new prompt, clone a repository with Kin:```sh
kin clone https://github.com/pallets/itsdangerous


Or initialize one you already have, replacing the path below:```sh
cd /path/to/your/repository &&
kin init . &&
kin overview &&
kin status

Both end with the next command to run, a kin refs question about a function in that
repository. They also connect Codex CLI and Grok CLI to it when you allowed that in setup,
because those clients keep one entry that names a repository.

Windows PowerShell 5.1 has no &&, so on native Windows run the same commands one at a
time and stop if one fails:```powershell
cd C:\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:```sh
kin locate "<something you already know is in this repository>"

Replace ExactEntityName below with a symbol from the result:```sh
kin refs ExactEntityName
kin trace ExactEntityName
kin impact ExactEntityName


`refs` returns recorded references, `trace` brings in nearby context, and `impact` explores potential effects through the graph. Check the results against the source.

### 4. Your AI coding tools and semantic search

`kin setup` already asked before connecting the AI coding tools it found, and connected them
if you said yes. There is no separate linking step. After you install another tool, run
`kin setup` again, and `kin setup status` shows what is connected. On Windows, connect AI
tools inside WSL2.

`kin runtime status --json` checks the shared CLI and daemon installation, including
their exact source identity. Normal commands refuse mismatched pairs; development
builds use isolated state. See runtime installation.

Graph and lexical retrieval work without a model. Embeddings and reranking are optional,
and their model providers default to `none`. Standard CLI and daemon builds include external
HTTP model support. Built-in models require a build with optional local inference enabled.

To build an embedding index using an OpenAI-compatible endpoint you operate:```sh
KIN_MODEL_EMBEDDINGS_PROVIDER=external \
KIN_MODEL_EMBEDDINGS_BASE_URL=http://localhost:1234/v1 \
KIN_MODEL_EMBEDDINGS_MODEL=your-served-embedding-model kin embed

Model endpoints receive the selected entity text needed for their stage.
Model settings describe providers, model identities, and credential environment variable names.

Kin supports Claude Code, Codex, Cursor, Gemini, and other MCP clients. Use kin setup --intent editor for VS Code. Kin also includes kin agent run for local or hosted OpenAI-compatible model endpoints.

Client configuration · MCP tools · Built-in agent

Local imports, storage, and graph queries run on your machine. Installing Kin needs network access; the default graph retrieval path needs no model download. When an embedding provider is selected, queries report its vector coverage and any gaps.

Review a change

After running kin init on the Git branch you want to review, compare explicit commit SHAs against main:sh kin review shadow "$(git rev-parse main)..$(git rev-parse HEAD)"

The report returns PASS, NEEDS ATTENTION, or WOULD BLOCK, with graph-derived impact and supporting evidence. It is advisory: it does not block a merge or change graph state. Authorship is declared, not independently verified.

Use Kin with or without Git

Kin has its own commits, branches, merges, diffs, and history, including in repositories with no Git underneath. Existing Git repositories can be imported, and supported workflows can export a new Git repository.

Native version-control walkthrough · Git interoperability and export limits

Beta limits

Coverage is incomplete. Supported languages are parsed into entities and relationships; other files remain available as content and history. An empty result does not prove there are no callers or dependencies. Keep using your compiler, tests, and review. See language support.

Compatibility varies. Release archives do not include the deprecated kin-vfs filesystem projection, so there is no transparent projection to rely on. Check platform notes for what each platform supports.

Back up Kin-only state. Commits, branches, reviews and specs you record with Kin live in the repository's Kin store, not in Git. Deleting the store and re-importing from Git does not recover them, so run kin backup create first. kin store prune deletes stores only when you pass --yes, for the same reason. Read the import, recovery, and upgrade notes.

Windows. Native Windows x86_64 support is early. Repository admission works: kin init imports a Git repository and publishes graph authority, and graph, lexical, and daemon-backed queries answer natively. The end-to-end install proof also runs agent setup on native Windows and gets graph-backed answers from the installed MCP server. Transparent filesystem projection is not shipped on Windows, and review workflows are not yet tested there, so WSL2 remains the recommended path for the full Kin experience.

Why I built Kin

I kept watching coding agents piece together parts of a codebase we'd already worked through. Then I'd do a version of that work myself to review their changes. I started wondering why more of that structural understanding wasn't part of the repository itself.

That's what I'm building with Kin.

Troy

Learn more and contribute

Kin and its local stack, including kin-db, are Apache-2.0. KinLab is the separate proprietary hosted product. Public repository onboarding is still in development.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Kin 怎么安装?

在客户端按下面的安装命令接入:npx -y @kinlab/kin-mcp。对应的包名是 @kinlab/kin-mcp。装完在客户端配置里引用同一个包或端点。

Kin 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Kin 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Kin 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Kin 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Gemini CLI、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Kin 能提供哪些能力?

资料显示能力标签包括 code search、semantic search、code review、refactoring、git、developer tools。具体工具清单以官方文档为准。

Kin 需要什么运行环境?

运行时为 rust;属于本地进程,需要在本机装好运行环境。

Kin 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。