原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

GitWarren

作者:klarluft版本 1.0.1i★ –i在你的电脑上运行
注册名称io.github.klarluft/gitwarren

安装

概览

作者提供的说明(英文原文)

Code review on your own machine, for you and your coding agent. Nothing leaves your computer.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: GITWARREN_DATA_DIR

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "gitwarren": {
      "command": "npx",
      "args": [
        "-y",
        "gitwarren",
        "mcp",
        "--serve",
        "your-value"
      ],
      "env": {
        "GITWARREN_DATA_DIR": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add gitwarren --env GITWARREN_DATA_DIR=your-value -- npx -y gitwarren mcp --serve your-value

运行前请先填写空着的值。

这个服务器需要在启动命令中填入值,请复制设置后自行填写。

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "gitwarren": {
      "command": "npx",
      "args": [
        "-y",
        "gitwarren",
        "mcp",
        "--serve",
        "your-value"
      ],
      "env": {
        "GITWARREN_DATA_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器需要在启动命令中填入值,请复制设置后自行填写。

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "gitwarren": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "gitwarren",
        "mcp",
        "--serve",
        "your-value"
      ],
      "env": {
        "GITWARREN_DATA_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • GITWARREN_DATA_DIR env
    Where the review database lives. Leave unset for the platform's application-data directory, which the app and the command line also use.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 klarluft 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 1385 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1385 个服务器的 68% 更新
  • 基础检查结果等于或优于此分类中其他 1385 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

GitWarren 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.0.1)于23天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者:github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新
安装

Desktop Commander

作者:wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新
安装

Cloudflare MCP

作者:cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

GitWarren

Code review for your own git repositories, on your own machines. Your machines, your agents, no one else's server — and no account.

Built for the moment a coding agent — Claude Code, Codex, or anything else that edits files on your disk — has just finished, and its work is sitting in your worktree uncommitted. Read that diff here, on your own machine, before it becomes a commit.

[gitwarren.com](https://gitwarren.com) has downloads for macOS, Windows and Linux.


What it does

Tell GitWarren which local git repositories you care about, then open reviews against them — a review is a comparison of two refs, presented the way a pull request is, with *conversation*, *commits* and *files changed* tabs, and a *browse files* tab for the code the change did not touch.

  • Review work before it is a commit. If the branch you are reviewing is checked out in a worktree, GitWarren finds that worktree — wherever it is — and folds its staged, unstaged and untracked changes into the diff. That is exactly when review is most useful, and it is the part that makes this worth having.
  • Prose as well as code. Diffs read unified or side by side, with the changed words picked out of a changed line. A Markdown file can be read rendered, with its edits marked like tracked changes, and commented on paragraph by paragraph.
  • Nothing is cached. Every branch name, commit and diff on screen is read from git at the moment it is shown.
  • Nothing leaves your machine. Reviews live in one SQLite file in your application-data directory. No account, no telemetry; the desktop app's one outbound request is the update check.
  • Agents are first-class. Local AI agents get the same capabilities through an MCP server over stdio — they open reviews, read your comments, reply in a thread and resolve what they fixed.
  • Desktop app or browser. It runs as an Electron app on macOS, Windows and Linux, or as a command that serves the same review UI into a browser tab. Same renderer either way; the shell is the only thing that differs.
  • Your other machines too. A machine with no screen at all — a VPS, a WSL distro, a box an agent works on — runs the headless half and is reviewed from somewhere else, over SSH, over wsl.exe, or over your own tailnet, and its repositories are listed on the same home screen as this machine's. Reviews live on the machine the code is on and stay there; nothing is replicated or relayed anywhere but the computers you already own.

Comments go on the line, the way a pull request does them. The agent that wrote the code answers in the same thread, while you are still reading the diff:


Install

The desktop app

Download it from [gitwarren.com](https://gitwarren.com), or on macOS:

brew install --cask klarluft/tap/gitwarren
The command line

Serves the same review UI in a browser instead of an Electron window — for a machine that will not have the app on it, or one with no screen at all:

brew install klarluft/tap/gitwarren-cli               # macOS and Linux, brings its own Node

curl -fsSL https://gitwarren.com/install.sh | sh # macOS and Linux, no Homebrew needed npx gitwarren serve # anywhere Node 22.14+ is, including Windows

Then gitwarren serve --open. See The gitwarren command line.

Into a coding agent

If you arrive from a coding agent, start here instead. The plugin brings the MCP server and a note that teaches the agent when to open a review and how to answer your comments:

/plugin marketplace add klarluft/gitwarren-app       # Claude Code, then:

/plugin install gitwarren@gitwarren gemini extensions install https://github.com/klarluft/gitwarren-app npx skills add klarluft/gitwarren-app # the note alone, for any agent

Cursor, Codex, VS Code and Kiro read the same repository from their plugin screens. See Installing it as a plugin.


Documentation

GuideWhat is in it
ReviewsWhat a review is, how uncommitted work is found, reading and navigating a large diff, side by side and wrapped lines, Markdown previews, browsing and searching the repository, marking files reviewed, opening a file in your editor, keyboard shortcuts
Agent access (MCP)The MCP tools, installing the plugin, how an agent links you back into the app, comment threads, images
The gitwarren command lineserve, service install, the four ways to install the CLI, updating and removing it
Your other machinesReaching a repository over SSH, over wsl.exe from Windows, on your tailnet, and from a phone
ArchitectureThe stack, the shared service layer both surfaces call, and what is and is not stored
DevelopmentRunning from source, the project layout, database migrations
ReleasingCutting a release, auto-update, code signing and notarization
The Glama build specThe fields Glama's admin page actually reads, and why they say what they say
Known limitationsWhat GitWarren does not do, and why
GitWarren across hostsThe design plan behind the remote-host model

Agents setting GitWarren up on a user's machine should read llms-install.md.


Contributing

Contributions are welcome. Anything larger than a bug fix starts as a discussion in Ideas, so the shape can be agreed before you spend time on it; once it is settled it becomes an issue. See CONTRIBUTING.md for the development workflow, the two design constraints that changes need to respect, and what a good pull request looks like here.

Before a first contribution can be merged you will be asked to sign the Contributor License Agreement. A bot handles it on your pull request; it takes about ten seconds and only happens once. The CLA keeps copyright in the codebase in one place, which is what makes it possible to offer GitWarren under a commercial licence alongside the GPL, or to change licence later, without having to track down every past contributor. You keep full ownership of your work and can use it elsewhere however you like.


Support and privacy

Questions, ideas and setups worth copying go to Discussions — Q&A if you are stuck on something, Ideas for a feature, and Show and tell for an agent or remote-machine arrangement other people should steal. Bugs you can describe — what GitWarren does, and when — go to issues. Anything you would rather not post publicly goes to contact@klarluft.com.

GitWarren keeps everything on your machine: reviews live in one SQLite file in your application-data directory, the diff is read from your git worktree, and there is no account and no telemetry. The desktop app's one outbound request is the auto-update check against this repository's GitHub Releases. The website's privacy policy covers gitwarren.com itself.


License

GitWarren is free software, licensed under the GNU General Public License, version 3 or (at your option) any later version. The full text is in LICENSE.

In short: you may use, study, modify and redistribute it, including commercially. If you distribute a modified version, or a program that incorporates this one, you must release that under the GPL as well and make the source available. That reciprocity is the point — it keeps GitWarren and anything built on it open.

The copyright is held by Klarluft B.V. (Rotterdam, The Netherlands · KVK 86875590), and every contribution is covered by the CLA. Because the copyright sits in one place rather than being spread across contributors, a licence other than the GPL — for embedding GitWarren in a closed-source product, for instance — can be granted on request: email contact@klarluft.com.

Michal Wrzosek ( ) is the creator of GitWarren and currently its main maintainer.

Copyright © 2026 Klarluft B.V.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/.

问 PopNx