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

chargehand

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

安装

概览

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

Runs coding-agent workers on a codebase question; every claim in the answer carries evidence.

PopNx MCP 的三大支柱

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

它能帮你做什么

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

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具
  • 你需要填写:CLAUDE_CODE_OAUTH_TOKEN, ANTHROPIC_API_KEY

安装

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

安装之前

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

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你用的是哪个应用?

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

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

{
  "mcpServers": {
    "chargehand": {
      "command": "dnx",
      "args": [
        "Chargehand",
        "--yes",
        "mcp"
      ],
      "env": {
        "CHARGEHAND_RUNTIME": "your-value",
        "CHARGEHAND_PROFILE": "your-value",
        "CLAUDE_CODE_OAUTH_TOKEN": "your-value",
        "ANTHROPIC_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add chargehand --env CHARGEHAND_RUNTIME=your-value --env CHARGEHAND_PROFILE=your-value --env CLAUDE_CODE_OAUTH_TOKEN=your-value --env ANTHROPIC_API_KEY=your-value -- dnx Chargehand --yes mcp

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

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "chargehand": {
      "command": "dnx",
      "args": [
        "Chargehand",
        "--yes",
        "mcp"
      ],
      "env": {
        "CHARGEHAND_RUNTIME": "your-value",
        "CHARGEHAND_PROFILE": "your-value",
        "CLAUDE_CODE_OAUTH_TOKEN": "your-value",
        "ANTHROPIC_API_KEY": "your-value"
      }
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "chargehand": {
      "type": "stdio",
      "command": "dnx",
      "args": [
        "Chargehand",
        "--yes",
        "mcp"
      ],
      "env": {
        "CHARGEHAND_RUNTIME": "your-value",
        "CHARGEHAND_PROFILE": "your-value",
        "CLAUDE_CODE_OAUTH_TOKEN": "your-value",
        "ANTHROPIC_API_KEY": "your-value"
      }
    }
  }
}

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

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

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

需要你填写的值

  • CHARGEHAND_RUNTIME env
    Worker runtime, when both or neither of claude and opencode are on PATH.
  • CHARGEHAND_PROFILE env
    A profile/v1 file for budgets, prices, memory or a pinned runtime version.
  • CLAUDE_CODE_OAUTH_TOKEN 机密 env
    Claude Code subscription token from claude setup-token. Set this or ANTHROPIC_API_KEY.
  • ANTHROPIC_API_KEY 机密 env
    Anthropic API key for Claude Code workers. Set this or CLAUDE_CODE_OAUTH_TOKEN.

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

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • … 尚未检查

    仍在维护

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

  • … 尚未检查

    有许可证

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

  • – 不适用

    端点有响应

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

  • – 不适用

    使用 OAuth 登录

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

  • … 尚未检查

    工具描述中没有隐藏指令

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

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

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

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

常见问题

chargehand 安全吗?

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

它需要哪些密钥或代码?

你需要填写:CLAUDE_CODE_OAUTH_TOKEN, ANTHROPIC_API_KEY

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

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

它还在维护吗?

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

哪些应用可以使用它?

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

有什么可以替代它?

同一分类中有: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,245MIT4天前更新
安装

Desktop Commander

作者:wonderwhy-er

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

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

Cloudflare MCP

作者:cloudflare

Cloudflare MCP servers

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

作者的 README

打开 README

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

chargehand

Ask a question about your code from Claude Code or any MCP client and get back claims that each cite a file at a pinned commit, checked before you see them.

Active. I work on it this month.

flowchart LR

caller[You or a program CLI · HTTP · MCP] -- request --> intake[Intake picks an action] intake -- answer or split --> workers[Agent sessions Claude Code or OpenCode] intake -- ask · deny · improve --> result workers -- claims + citations --> resolver[Evidence resolver checks each citation] resolver --> result[Typed result claims · open questions · cost] workers -. code preset, driven batches .-> branch[Tested branch or draft pull request] resolver --> log[(Run log tokens · cache · prompts)]

Why

Coding agents answer in prose. A program that calls one needs something it can check: claims tied to files at a commit, diffs, session messages or the caller's own inputs, plus a confidence and the exact prompts behind the answer. I also wanted the control flow (the task graph, budgets, retries, parallelism) in code rather than in a prompt, so each agent's context stays small, cached and disposable.

What it does

Answers with checked citations. You ask a question about a repository; chargehand runs a read-only agent session (Claude Code or OpenCode) on a clone at a pinned commit and returns typed JSON (result/v1): claims, open questions, a confidence, the cost and the prompts behind it. A *citation* is a file and line range, a commit, a diff range, a session message or an input id. Each one must exist at the pinned commit before a claim leaves its worker; the worker gets one repair turn, and claims that still fail move to open questions.

You reach it as an MCP server (stdio or HTTP), an HTTP API or a CLI. Presets (default, cheap, thorough, strict, draft, review) set the tools, the token and dollar budgets and whether a question may be split into 2 to 4 read-only subtasks.

Also in the box, each with its own guide:

  • A code preset and driven batches that write a tested branch or a draft pull request in a sandbox (Writing a branch, Driven sessions).
  • /chargehand:change, a Claude Code plugin command: one prompt to a reviewed change on a local branch (the change command).
  • An operator console in the browser (Web UI).
  • *Prompt CI*, which gates prompt and preset changes on paired evals; the run log records tokens, cache hits, cost and the prompt chain of every call (Prompt CI).

Not here: an agent loop of its own, direct calls to model providers, a model gateway, a memory store (it uses yours over MCP), a hosted service. A citation that resolves points at something that exists; checking that the cited text supports the claim is planned, not built (roadmap).

[!WARNING]

Before 1.0. The images have no latest tag: pin an exact version and read the changelog before you upgrade.

Quick start

Ask Claude Code a question about your own repository, with no clone of chargehand.

You need:

  • the .NET 10 SDK (dotnet --version prints 10.x), which provides dnx;
  • Claude Code 2.1.283 on PATH (claude --version), signed in (run claude once);
  • a token for the workers: claude setup-token prints one for your subscription (an ANTHROPIC_API_KEY works too and bills per token).
claude mcp add chargehand -e CLAUDE_CODE_OAUTH_TOKEN=<token> -- dnx Chargehand@0.19.4 --yes -- mcp

Replace 0.19.4 with the newest version of the Chargehand package on nuget.org and pin it: the package changes before 1.0. In a Claude Code session in the repository you want to ask about, say: *use chargehand to find where retries are decided, and cite the code.* The answer lists claims, each with its file and lines. Other editors and agents (Cursor, VS Code, Codex, Gemini CLI and more) are in Connect your editor or agent.

From a clone, to ask one question about chargehand itself without MCP: it needs the .NET 10 SDK, git and the same Claude Code, signed in. With no profile, the workers use the CLI's own login and default model.

git clone https://github.com/Egoushka/chargehand.git && cd chargehand

cat > request.json <<EOF { "contract_version": "request/v1", "text": "Where does a split node decide whether to fork the first node's session? Cite the code.", "context": { "interactive": false, "preset": "default", "repository": { "path": "$PWD", "commit": "$(git rev-parse HEAD)" } } } EOF dotnet run --project src/Chargehand.Cli -- run < request.json

It prints result/v1 on stdout: claims with citations, open questions, a confidence and the cost. The quickstart guide explains every field, OpenCode instead of Claude Code, and what to do when a run fails.

How it works

  1. Intake reads the request (request/v1) and writes a *Task Spec*: one action, answer, split, ask, deny or improve. The last three stop the run with questions, a reason or a better request. A preset can also stop a run for approval above a risk or cost estimate.
  2. Workers are ordinary Claude Code or OpenCode sessions on a clone of the repository at the pinned commit, inside the directories the profile allows. chargehand never calls a model provider itself.
  3. The evidence resolver checks every citation against git, the session and the request. The invariant: no claim reaches the result unless its citations resolved.
  4. The result (result/v1) carries the claims, the open questions, usage and the prompt chain. The same record goes to the run log, which show, cache and routes read.

Writing runs follow the same path with a sandboxed worker: the code preset verifies a branch with the repository's tests, and driven batches add an egress allowlist, a runner that alone holds the Docker socket, and a check gate before a pull request opens. ARCHITECTURE.md maps the code.

Numbers

ValueSource
Citations that resolved, read-only runs50 of 50 (phase 3), 99 of 99 (phase 4)benchmarks
Cost of a split against one plain session1.53× ($0.00754 vs $0.00492 a run) for a blind score of 0.967 vs 0.950phase 4
Deliberate prompt regressions Prompt CI blocked1 of 2, and only after the score added completenessPrompt CI
Quality benchmark on public repositories13 tasks over 4 pinned repositories; no real run yetbenchmark
Users1, mecounted

Lessons

  • Parallelism did not pay on the questions I measured. Splits resolved every citation but cost half again as much for a small score gain, so the shipped default, review and draft presets allow no split (ADR 0017).
  • A score that measures what run-time checks already enforce catches nothing. The first Prompt CI score measured grounding, which the resolver already forces, so a prompt that dropped a third of the claims passed. The score now multiplies grounding by completeness (ADR 0019).

Docs

  • Overview: what it is, how a run works, what it leaves out, status
  • What it does, and how we know: each capability with its status and evidence
  • Quickstart · Install with Docker Compose: from a clone, or from the release images
  • Use it from an MCP client · Run the HTTP server · Web UI
  • Writing a branch · Driven writing sessions · Several runners
  • The change command: the Claude Code plugin
  • Memory and services · Prompt CI · Benchmark
  • Reference: commands, routes, presets, contracts, profile fields, environment variables
  • Architecture · Decisions · Changelog · Roadmap
  • Contributing · Security · Apache-2.0 license
问 PopNx