task-checkpoint-mcp (npm launcher)

这是 task-checkpoint-mcp 的 npm 启动器，不是服务器本体。

注意同名：PyPI 上也有一个同名的 task-checkpoint-mcp，那才是真正的服务器（纯标准库 Python）。npx task-checkpoint-mcp 装到的是这个壳，pipx install task-checkpoint-mcp 装到的才是本体。两者不冲突，但别以为是同一个东西。

推荐直接装 Python 包，不需要这个 npm 包：

pipx install task-checkpoint-mcp

装完把 MCP 客户端的 command 指向 tc-mcp 即可。

什么时候用这个包

只在你已经用不上 pipx 的场景：

npx -y task-checkpoint-mcp

它会找一个装了 tc_mcp 的 Python 解释器（依次试 python / py -3 / python3，可用 TC_PYTHON 指定），然后把 stdio 透传给 python -m tc_mcp。其余参数会透传过去，所以 npx -y task-checkpoint-mcp --install-skill ~/.claude/skills/task-checkpoint 也能用。

npx -y task-checkpoint-mcp --help / --version 是这个壳自己的，不需要本机有 Python。

它不会替你装 Python 包。 本机没有 pipx install task-checkpoint-mcp 过的话，它会打印上面那句安装命令然后退出码 1 —— 这是有意的，免得你在运行时拿到一堆看不懂的 traceback。

客户端配置

{
  "mcpServers": {
    "task-checkpoint": {
      "command": "npx",
      "args": ["-y", "task-checkpoint-mcp"]
    }
  }
}

如果本机已经装了 Python 包，用下面这段更直接，少一层 Node 中转：

{
  "mcpServers": {
    "task-checkpoint": { "command": "tc-mcp", "args": [] }
  }
}

许可：MIT。

task-checkpoint-mcp (npm launcher)

An npm launcher for task-checkpoint-mcp, not the server itself.

Mind the namesake. There is a package with the same name on PyPI, and that is the real server (pure standard-library Python). npx task-checkpoint-mcp gets you this launcher; pipx install task-checkpoint-mcp gets you the actual thing. They don't conflict, but they are not the same artifact.

Install the Python package instead — you don't need this npm package:

pipx install task-checkpoint-mcp

Then point your MCP client's command at tc-mcp.

When to use this package

Only where pipx isn't an option:

npx -y task-checkpoint-mcp

It locates a Python interpreter that has tc_mcp importable (trying python, py -3, python3 in turn; override with TC_PYTHON) and hands stdio through to python -m tc_mcp. Remaining arguments are passed through, so npx -y task-checkpoint-mcp --install-skill ~/.claude/skills/task-checkpoint works too.

npx -y task-checkpoint-mcp --help / --version belong to this launcher and need no local Python.

It will not install the Python package for you. If pipx install task-checkpoint-mcp has never been run, it prints that command and exits 1 — deliberately, so you don't get an opaque traceback at runtime.

Client config

{
  "mcpServers": {
    "task-checkpoint": {
      "command": "npx",
      "args": ["-y", "task-checkpoint-mcp"]
    }
  }
}

If the Python package is already installed, this is more direct — one less Node hop:

{
  "mcpServers": {
    "task-checkpoint": { "command": "tc-mcp", "args": [] }
  }
}

License: MIT.