Claude Checkpoint

MCP文档知识

提供方 未标注

文档知识 未标注 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code

将Claude Code会话状态(目标、任务、决策、涉及的文件、最近的命令)保存到本地文件,并在崩溃、/clear或上下文限制后将其恢复为简洁的恢复摘要。仅限本地使用,机密信息已脱敏。

一句话选型结论

按资料字段整理

Claude Checkpoint 属于文档知识类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

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

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Claude Checkpoint当前 未标注 未标注 未标注 无 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

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

claude-checkpoint-mcp

Save your Claude Code session state locally, so a crash, /clear, or context limit doesn't make Claude rebuild context from scratch.

claude-checkpoint-mcp is a local Model Context Protocol server with two tools:

  • save_session_checkpoint writes your session's working state to a small JSON file in the project.
  • load_session_checkpoint turns that file back into a compact resume brief.

It runs entirely on your machine. Nothing is sent anywhere.


Contents

  • Why: stop paying twice for the same context
  • How it works
  • Installation
  • Configuration
  • Claude Code
  • Claude Desktop
  • Other MCP clients
  • Usage
  • Tool reference & examples
  • The .claude-checkpoint file
  • Security & privacy
  • Troubleshooting
  • Development

Why: stop paying twice for the same context

A long Claude Code session builds up a lot of context:
- what you're trying to do;
- which approaches already failed;
- which files matter;
- which test is still red.

Several things can wipe that out mid-task:
- a terminal crash, SSH drop, or laptop sleep;
- running out of context window;
- a /clear to get a fresh window.

The next session starts cold. To get back to where you were, Claude has to rebuild that context:

  • Re-reading files to work out what was changed and why. Every file read is input tokens.
  • Re-running exploration: grep, git diff, ls, test runs, all just to rediscover state.
  • Re-explaining. You retype the goal, the constraints, and the dead ends, or Claude rediscovers the dead ends the hard way.

Each of those turns resends the growing conversation as input, so the cost compounds.

claude-checkpoint-mcp swaps that rebuild for one small, structured read:

Without a checkpoint With load_session_checkpoint
Restoring the goal & constraints You retype them, or Claude infers them One section of the brief
Knowing what's done vs. pending Re-derived from code and git Task list with statuses
Knowing which files matter Broad re-reading Exact list of touched files, with notes
Knowing what changed since Re-read everything to be safe Only files whose content actually changed are flagged
Remembering failed attempts Often repeated Recorded under Decisions & gotchas

The resume brief for a typical session is about 1.2 KB of markdown, a few hundred tokens. The example below is real output at that size.

The biggest saving comes from drift detection. At save time, the server records a content hash for every file with uncommitted changes. On load, it compares those hashes against the working tree and tells Claude exactly which files changed after the checkpoint. Everything else in the brief can be trusted as-is, so Claude re-reads only what it has to.


How it works```

Session 1 Session 2 (after crash / /clear)
───────── ────────────────────────────────
Claude ──save_session_checkpoint──┐ ┌──load_session_checkpoint── Claude
goal, tasks, summary, │ │ compact markdown brief
next steps, decisions, ▼ │ + "changed since checkpoint"
files, commands ┌─────────────────────┐
│ <project>/ │
server adds: │ .claude-checkpoint │◀── git: branch, HEAD,
git branch/HEAD, │ .claude-checkpoint │ dirty files + hashes
dirty files + hashes, │ .prev (backup) │
redacts secrets └─────────────────────┘


- **Claude supplies the meaning**: the goal, progress, decisions, next steps, and which commands mattered.
- **The server supplies the facts**: git branch and HEAD, every uncommitted or untracked file with its content hash, and timestamps.
- **The server instructions teach Claude when to act.** Claude is told to load at the start of a session and to save after milestones, before risky operations, and when the conversation gets long. It doesn&#x27;t need to be prompted every time.

---

## Installation

Requirements: **Node.js 20+** and **git**. Git is optional, but without it you lose drift detection.```sh
git clone https://github.com/tenlean/claude-checkpoint-mcp.git
cd claude-checkpoint-mcp
npm install
npm run build

The server entry point is now at dist/index.js.


Configuration

Claude Code

As a plugin (easiest). This repo is also a Claude Code plugin marketplace. You don't need to clone or build anything:```sh
claude plugin marketplace add tenlean/claude-checkpoint-mcp
claude plugin install claude-checkpoint-mcp@tenlean


Restart Claude Code, then `/mcp` should show `plugin:claude-checkpoint-mcp:claude-checkpoint` as connected.

**Manual setup.** If you cloned the repo, register the server once for your user account, so it&#x27;s available in every project:```sh
# Run from the claude-checkpoint-mcp directory
claude mcp add --scope user checkpoint -- node &quot;$PWD/dist/index.js&quot;

> Use an absolute path. A user-scoped server is launched from whichever project you open Claude Code in. A relative path like ./dist/index.js would resolve against that project, not this repo. &quot;$PWD/dist/index.js&quot; expands to the absolute path when you run the command, which is what gets saved.

Check that it's registered:```sh
claude mcp list


Inside a session, `/mcp` should show `checkpoint` as connected.

**Project-scoped alternative.** To share the server with a team through version control, add it to the project&#x27;s `.mcp.json`:```json
{
  &quot;mcpServers&quot;: {
    &quot;checkpoint&quot;: {
      &quot;command&quot;: &quot;node&quot;,
      &quot;args&quot;: [&quot;/absolute/path/to/claude-checkpoint-mcp/dist/index.js&quot;]
    }
  }
}

Either way, add the checkpoint files to the project's .gitignore, or to your global gitignore:```gitignore
.claude-checkpoint*


### Claude Desktop (`claude_desktop_config.json`)

Open the config file:

| OS | Path |
|---|---|
| macOS | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows | `%APPDATA%\Claude\claude_desktop_config.json` |

Add the server under `mcpServers`, using the absolute path to your local build:```json
{
  &quot;mcpServers&quot;: {
    &quot;checkpoint&quot;: {
      &quot;command&quot;: &quot;node&quot;,
      &quot;args&quot;: [&quot;/absolute/path/to/claude-checkpoint-mcp/dist/index.js&quot;],
      &quot;env&quot;: {
        &quot;CHECKPOINT_PROJECT_ROOT&quot;: &quot;/absolute/path/to/your/project&quot;
      }
    }
  }
}

Restart Claude Desktop after saving the file.

> Claude Desktop has no notion of a "current project". Use CHECKPOINT_PROJECT_ROOT to set the default project, or have Claude pass projectRoot on each call ("save a checkpoint for /home/me/code/my-app"). See project root resolution.

Other MCP clients

Any MCP client that supports the stdio transport can run the server:```sh
node /absolute/path/to/claude-checkpoint-mcp/dist/index.js


---

## Usage

The server&#x27;s built-in instructions cover the common cases automatically. You can also ask Claude directly.

**Save**:
- *&quot;Checkpoint our progress.&quot;*
- *&quot;Save a checkpoint before you run the migration.&quot;*
- *&quot;Update the checkpoint. Merge in what we just did.&quot;*

**Resume** (in a fresh session):
- *&quot;Resume where we left off.&quot;*
- *&quot;Load the checkpoint and continue.&quot;*

### Example resume brief

This is real output from `load_session_checkpoint`. In the scenario, one file was committed unchanged after the save, and a teammate then edited `session.ts`:```markdown
# Resuming: my-app (checkpoint saved 2m ago, 2026-10-08 02:23:55 UTC)
Branch `feat/github-oauth` @ b2ef1b591 (uncommitted changes)

## Goal
Add GitHub OAuth login with persistent sessions

## Tasks
- [x] OAuth callback route
- [~] Session cookie persistence
- [ ] Logout endpoint

## Where things stand
Callback exchanges the code and creates a session, but the cookie is dropped on reload. Suspect SameSite/secure flags in dev.

## Next steps
1. Set sameSite: &#x27;lax&#x27; and secure only in production in src/auth/session.ts
2. Re-run npm test -- auth
3. Start the logout endpoint

## Decisions &amp; gotchas
- Use iron-session, not express-session (needs edge runtime support)
- Don&#x27;t mock the GitHub API in e2e tests; use the recorded fixtures in test/fixtures

## Files touched (3)
- src/auth/session.ts (M) — cookie options
- src/auth/callback.ts (M)
- src/auth/session.spec.ts (??)

## Recent commands (last 2, oldest first)
- ✓ `GITHUB_CLIENT_SECRET=«redacted» npm run dev`
- ✗ exit 1 `npm test -- auth` — 2 failing in session.spec.ts: cookie missing after reload

## Since this checkpoint
- 1 new commit(s) on HEAD
- ⚠ Changed after the checkpoint, re-read before editing: `src/auth/session.ts`

callback.ts was committed after the save, but its content didn't change, so it isn't flagged. Only session.ts needs to be re-read.

Task markers: [x] done · [~] in progress · [ ] pending · [!] blocked.


Tool reference & examples

save_session_checkpoint

Writes /.claude-checkpoint.

Parameter · Type · Required · Description
goal · string (≤ 500) · ✅ · Primary objective of the session
tasks · { description, status }[] (≤ 30) · status: pending · in_progress · done · blocked
summary · string (≤ 4000) · Where things stand: what works, what's broken, what you were in the middle of
nextSteps · string[] (≤ 20) · Ordered next actions for whoever resumes
decisions · string[] (≤ 20) · Key decisions, constraints, dead ends to avoid
modifiedFiles · { path, note? }[] (≤ 100) · Files to annotate, or committed files to include. Uncommitted git changes are detected automatically. Absolute paths inside the project are stored as relative.
recentCommands · { command, exitCode?, note? }[] (≤ 50) · Significant commands, oldest first. Secrets are redacted.
mode · &quot;replace&quot; \ · &quot;merge&quot; · Default replace. See below.
projectRoot · string (absolute) · Overrides root resolution

Full save:```json
{
"goal": "Add GitHub OAuth login with persistent sessions",
"tasks": [
{ "description": "OAuth callback route", "status": "done" },
{ "description": "Session cookie persistence", "status": "in_progress" },
{ "description": "Logout endpoint", "status": "pending" }
],
"summary": "Callback exchanges the code and creates a session, but the cookie is dropped on reload. Suspect SameSite/secure flags in dev.",
"nextSteps": [
"Set sameSite: 'lax' and secure only in production in src/auth/session.ts",
"Re-run npm test -- auth"
],
"decisions": ["Use iron-session, not express-session (needs edge runtime support)"],
"modifiedFiles": [{ "path": "src/auth/session.ts", "note": "cookie options" }],
"recentCommands": [
{ "command": "GITHUB_CLIENT_SECRET=gh_live_8f2a91 npm run dev", "exitCode": 0 },
{ "command": "npm test -- auth", "exitCode": 1, "note": "2 failing in session.spec.ts" }
]
}


**Response** (text shown to the model):```
Checkpoint saved to /home/me/code/my-app/.claude-checkpoint (2202 bytes, replace).
3 task(s), 3 file(s), 2 command(s) on feat/github-oauth@b2ef1b591.
⚠ Redacted 1 secret-looking value(s).

Incremental update with merge:```json
{
"goal": "Add GitHub OAuth login with persistent sessions",
"mode": "merge",
"tasks": [
{ "description": "Session cookie persistence", "status": "done" },
{ "description": "Logout endpoint", "status": "in_progress" }
],
"recentCommands": [{ "command": "npm test -- auth", "exitCode": 0, "note": "all green" }]
}


| Field | `replace` | `merge` |
|---|---|---|
| `goal` | set | set |
| `tasks` | set | updated by matching `description`; new tasks appended |
| `summary`, `nextSteps` | set | replaced if provided, otherwise kept |
| `decisions` | set | appended (deduplicated) |
| `recentCommands` | set | appended; the oldest are dropped beyond 50 |
| `modifiedFiles` | fresh git scan + provided | fresh git scan + provided + previously recorded |
| `id`, `createdAt` | new | preserved |

**Structured output** (`structuredContent`):```json
{
  &quot;path&quot;: &quot;/home/me/code/my-app/.claude-checkpoint&quot;,
  &quot;bytes&quot;: 2202,
  &quot;mode&quot;: &quot;replace&quot;,
  &quot;counts&quot;: { &quot;tasks&quot;: 3, &quot;modifiedFiles&quot;: 3, &quot;recentCommands&quot;: 2, &quot;redactions&quot;: 1 },
  &quot;warnings&quot;: [&quot;Redacted 1 secret-looking value(s).&quot;]
}

load_session_checkpoint

Read-only. Reads the checkpoint, checks for drift, and returns the brief.

Parameter · Type · Required · Description
format · &quot;brief&quot; \ · &quot;full&quot; · Default brief (markdown, as above). full returns the complete checkpoint JSON plus drift.
projectRoot · string (absolute) · Overrides root resolution

Examples:```json
{}

{ &quot;format&quot;: &quot;full&quot;, &quot;projectRoot&quot;: &quot;/home/me/code/my-app&quot; }
```

**Structured output** (`structuredContent`):```json
{
  &quot;found&quot;: true,
  &quot;path&quot;: &quot;/home/me/code/my-app/.claude-checkpoint&quot;,
  &quot;fromBackup&quot;: false,
  &quot;updatedAt&quot;: &quot;2026-10-08T02:23:55.477Z&quot;,
  &quot;drift&quot;: {
    &quot;branchChanged&quot;: false,
    &quot;currentBranch&quot;: &quot;feat/github-oauth&quot;,
    &quot;commitsSince&quot;: 1,
    &quot;changedSince&quot;: [&quot;src/auth/session.ts&quot;]
  },
  &quot;warnings&quot;: []
}
```

If no checkpoint exists, the tool returns `found: false` with a &quot;nothing to resume&quot; message. That isn&#x27;t treated as an error.

### How the project root is chosen

1. The `projectRoot` argument
2. The `CHECKPOINT_PROJECT_ROOT` environment variable
3. The client&#x27;s first `file://` root, if the client supports MCP roots
4. The server process&#x27;s working directory

The path must be absolute and must be an existing directory. Symlinks are resolved. The file is always written at exactly `/.claude-checkpoint`.

---

## The `.claude-checkpoint` file

This is plain, versioned JSON, so it&#x27;s easy to read, diff, or edit by hand. Real example:```json
{
  &quot;version&quot;: 1,
  &quot;id&quot;: &quot;ee5507c0-855e-44a5-85c1-d97b767537c9&quot;,
  &quot;createdAt&quot;: &quot;2026-10-08T02:23:55.477Z&quot;,
  &quot;updatedAt&quot;: &quot;2026-10-08T02:23:55.477Z&quot;,
  &quot;generator&quot;: { &quot;name&quot;: &quot;claude-checkpoint-mcp&quot;, &quot;version&quot;: &quot;0.1.0&quot; },
  &quot;project&quot;: { &quot;name&quot;: &quot;my-app&quot; },
  &quot;git&quot;: {
    &quot;branch&quot;: &quot;feat/github-oauth&quot;,
    &quot;head&quot;: &quot;b2ef1b5919ee5d456ea146c9362a7abc92b1e556&quot;,
    &quot;dirty&quot;: true
  },
  &quot;goal&quot;: {
    &quot;primary&quot;: &quot;Add GitHub OAuth login with persistent sessions&quot;,
    &quot;tasks&quot;: [
      { &quot;description&quot;: &quot;OAuth callback route&quot;, &quot;status&quot;: &quot;done&quot; },
      { &quot;description&quot;: &quot;Session cookie persistence&quot;, &quot;status&quot;: &quot;in_progress&quot; },
      { &quot;description&quot;: &quot;Logout endpoint&quot;, &quot;status&quot;: &quot;pending&quot; }
    ]
  },
  &quot;summary&quot;: &quot;Callback exchanges the code and creates a session, but the cookie is dropped on reload. Suspect SameSite/secure flags in dev.&quot;,
  &quot;nextSteps&quot;: [
    &quot;Set sameSite: &#x27;lax&#x27; and secure only in production in src/auth/session.ts&quot;,
    &quot;Re-run npm test -- auth&quot;,
    &quot;Start the logout endpoint&quot;
  ],
  &quot;decisions&quot;: [
    &quot;Use iron-session, not express-session (needs edge runtime support)&quot;,
    &quot;Don&#x27;t mock the GitHub API in e2e tests; use the recorded fixtures in test/fixtures&quot;
  ],
  &quot;modifiedFiles&quot;: [
    { &quot;path&quot;: &quot;src/auth/session.ts&quot;, &quot;status&quot;: &quot;M&quot;, &quot;source&quot;: &quot;git&quot;, &quot;note&quot;: &quot;cookie options&quot;, &quot;hash&quot;: &quot;9ec893ef673dac860e7e2b6fcaad602983eeb0b1&quot; },
    { &quot;path&quot;: &quot;src/auth/callback.ts&quot;, &quot;status&quot;: &quot;M&quot;, &quot;source&quot;: &quot;git&quot;, &quot;hash&quot;: &quot;f3ecc849c3875d4f11bb42ae0e5ab6c71931d7f1&quot; },
    { &quot;path&quot;: &quot;src/auth/session.spec.ts&quot;, &quot;status&quot;: &quot;??&quot;, &quot;source&quot;: &quot;git&quot;, &quot;hash&quot;: &quot;9daeafb9864cf43055ae93beb0afd6c7d144bfa4&quot; }
  ],
  &quot;recentCommands&quot;: [
    { &quot;command&quot;: &quot;GITHUB_CLIENT_SECRET=«redacted» npm run dev&quot;, &quot;exitCode&quot;: 0, &quot;at&quot;: &quot;2026-10-08T02:23:55.477Z&quot; },
    { &quot;command&quot;: &quot;npm test -- auth&quot;, &quot;exitCode&quot;: 1, &quot;note&quot;: &quot;2 failing in session.spec.ts: cookie missing after reload&quot;, &quot;at&quot;: &quot;2026-10-08T02:23:55.477Z&quot; }
  ],
  &quot;meta&quot;: { &quot;redactions&quot;: 1, &quot;truncated&quot;: false }
}
```

| Field | Notes |
|---|---|
| `version` | Schema version. Older versions are migrated on load; unknown versions are rejected. |
| `id` / `createdAt` | Stable across `merge` saves; new on `replace` |
| `git` | `null` outside a git repo, or before the repo&#x27;s first commit |
| `modifiedFiles[].status` | Git porcelain code (`M`, `A`, `D`, `R`, `??`), or `M` for files reported only by Claude |
| `modifiedFiles[].source` | `git` (detected) or `agent` (reported by Claude, or carried over from an earlier merge) |
| `modifiedFiles[].hash` | Git blob hash of the working-tree content at save time; drives drift detection |
| `meta.truncated` | `true` if anything was dropped to fit list or size limits |

Paths are always relative to the project root. The file never stores absolute paths.

---

## Security &amp; privacy

- **Local only.** There are no network calls. The server reads git metadata and one file, and writes one file.
- **Secret redaction.** The following are replaced with `«redacted»` in commands, notes, summaries, tasks and decisions before anything touches disk:
  - `*_KEY=`, `*_TOKEN=`, `*_SECRET=`, `*PASSWORD=` assignments, including `Header: value` and JSON forms
  - `Authorization: Bearer …` headers
  - credentials in URLs (`postgres://user:pass@…`)
  - `--password` / `--token` / `--api-key` / `--secret` flags
  - bare `sk-…`, `ghp_…`, `github_pat_…`, `AKIA…` and `xox?-…` tokens

  Redaction is a safety net, not a guarantee, so keep the file out of version control.
- **Owner-only, crash-safe writes.** Files are written with mode `0600`. Each save writes a temp file, fsyncs it, and renames it into place, so a crash mid-save can&#x27;t leave a half-written checkpoint.
- **Automatic backup.** The previous valid checkpoint is kept as `.claude-checkpoint.prev`. If the main file is corrupt, load falls back to the backup and says so. A corrupt file never overwrites a good backup.
- **Bounded size.** Every field has a length cap, and the file is capped at 64 KB (the oldest commands are dropped first), so a checkpoint can&#x27;t grow into a token sink.
- **No shell.** Git runs through `execFile` with a 3-second timeout and `GIT_OPTIONAL_LOCKS=0`, so it never contends with your own git commands.
- **Doesn&#x27;t touch your config.** If the checkpoint isn&#x27;t git-ignored, the save response warns you. It never edits `.gitignore` for you.
- **Safe with parallel tool calls.** Tool calls are serialized inside the server, so concurrent `merge` saves can&#x27;t lose updates.

---

## Troubleshooting

| Symptom | Fix |
|---|---|
| `checkpoint` doesn&#x27;t appear in `/mcp` | Run `claude mcp list` and check that the path is absolute and `dist/index.js` exists (`npm run build`). |
| Checkpoint is written to the wrong directory | The server fell back to its working directory. Pass `projectRoot`, or set `CHECKPOINT_PROJECT_ROOT`. |
| `projectRoot must be an absolute path` | Use a full path such as `/home/me/code/app`, not `./app`. |
| Brief says &quot;Saved commit … is no longer reachable&quot; | The branch was rebased or reset after the save. Drift can&#x27;t be computed against history, so treat the flagged files as needing a re-read. |
| Warning: &quot;not git-ignored&quot; | Add `.claude-checkpoint*` to `.gitignore`. |
| No &quot;Since this checkpoint&quot; section | The project isn&#x27;t a git repo, or had no commits at save time. |

Server logs go to **stderr**. Stdout is reserved for the MCP protocol.

---

## Development```sh
npm run typecheck   # strict TypeScript, src + tests
npm test            # unit tests + in-memory MCP end-to-end tests (vitest)
npm run build       # compile to dist/
npm run inspect     # open the MCP Inspector against dist/index.js

src/
├── index.ts # entry point: stdio transport, signals, stderr logging
├── server.ts # McpServer construction + server instructions
├── tools.ts # save/load tool schemas and handlers
├── schema.ts # zod schema for the checkpoint file (v1) + migrations
├── store.ts # project root resolution, atomic I/O, backup/fallback
├── git.ts # branch/HEAD/status snapshot, blob hashing, drift detection
├── redact.ts # secret scrubbing
└── render.ts # checkpoint → markdown resume brief
```

Built with the official @modelcontextprotocol/sdk and zod.

License

MIT

常见问题

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

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Claude Checkpoint 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Claude Checkpoint 收费吗?

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

Claude Checkpoint 需要 API Key 吗?

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

Claude Checkpoint 支持哪些客户端?

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

Claude Checkpoint 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

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

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