grasp
What it does
Review what your coding agent did, decision by decision, with real before/after behavior.
- Connects 在你的电脑上运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
archify
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
双击文件,然后在电脑版 Claude 应用中点击 Install
试一试
用 grasp 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 grasp,或回答中出现 grasp 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 grasp
grasp 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 grasp 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code 暂时无法连接 grasp
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 grasp 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
Cursor 暂时无法连接 grasp
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 grasp 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
VS Code 暂时无法连接 grasp
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 grasp 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月16日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 arsaljamal 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于今天
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/arsaljamal-grasp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 5964 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5964 个服务器的 99% 更新
- 基础检查结果等于或优于此分类中其他 5964 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
grasp 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于今天,最新版本(0.1.1)于今天进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 grasp | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
grasp
Review what your coding agent did, decision by decision.
AI agents write code faster than people can review it. grasp shows you what the software does now compared with before (real outputs, not the agent's summary), walks you through each decision with Approve / Reject, warns you what the change could break, and sends rejections back to the agent.
Install in Claude Code (no Go needed):
/plugin marketplace add arsaljamal/grasp
/plugin install grasp@grasp
Work as usual, then type /grasp:review. To see it first on a sample session, type /grasp:demo, or without Claude Code: go run github.com/arsaljamal/grasp/cmd/grasp@latest demo. For a pull request without an agent session, see PR mode.
| Start here: guess, then see; and what it could break | Reject with a note for the agent |
|---|---|
Watch mode: the session as a reel, one animated scene per step
How it works
you ask ──► agent decides ──► agent changes files
│ │ │ └──── grasp reads the session (hooks + transcript) ────┐ │ │ agent calls record_decision (MCP) every edit is linked to "what, why, files, alternatives, risk" the decision that explains it │ │ └────────► review page ◄──────────────────┘ approve · reject · comment │ agent calls get_review_feedback (MCP) and follows it next time
- Show, don't tell. The agent gives a short command that demonstrates a change (for example: start the server, send an empty title, print the response). grasp runs it on the code from before the session and on the code now, and shows both outputs side by side. The agent cannot fake them: grasp runs them itself. Decisions with no demonstration say so.
- Guess first, then see. On the start card the new output stays hidden until you think about what it should be. Then you say whether it matched. Anything that surprised you is flagged before you approve it.
- What it could break, checked by grasp, not the agent. It flags existing tests the agent changed or weakened, and finds code elsewhere in the project that uses a function the agent changed but was not updated (or a deleted function that is still called).
- Decisions, not lines. Each decision shows *why*, the options the agent rejected, the risk it saw, and the exact changes that carry it out.
- Nothing hides. Edits that no decision explains are grouped as *changes with no recorded reason*. Files a decision names but never touches are flagged as *unverified claims*.
- Works without cooperation too. If the agent records no decisions, grasp groups edits by what the agent said just before making them, and marks those groups as inferred.
- One thing at a time. Each decision is a card; the code and the full reasoning stay hidden until you ask for them. Watch plays the session like a reel: story bars on top, one animated scene per step (the request typing out, decision cards flipping in, changed lines sliding in, commands running), with speed control and tap-to-skip.
- Closes the loop. Rejections and comments become instructions the agent reads through
get_review_feedbackat the start of its next task.
Quick start (Claude Code)
The plugin (above) downloads the right grasp binary on first use and checks its checksum. Then work as usual and type /grasp:review when you want to review.
Or install the command yourself and set up one project:
go install github.com/arsaljamal/grasp/cmd/grasp@latest
cd your-project grasp init # adds the MCP server (.mcp.json), hooks (.claude/settings.json) and a CLAUDE.md note claude # work as usual grasp serve # open http://127.0.0.1:7080 and review; it updates live while the agent works
Already have sessions? grasp import --latest loads the newest Claude Code session for this folder, or pass transcript files: grasp import ~/.claude/projects/ / .jsonl.
Reviewing a pull request (no agent session)
Most changes reach reviewers as a pull request, not as a live agent session. Check out the branch and run:
grasp pr -base origin/main -title "PR title" -body "PR description" -explain
grasp serve
Without -explain, each commit becomes a decision (its message is the reason) and you still get the full "What it could break" check. With -explain, Claude Code reads the diff (as files, with no write access), records the real design decisions, says where to look first, and demonstrates behavior with show_behavior, which runs on the base commit and on the branch. Every claim is linked to the actual diff, and test files are grouped with the code they test.
Commands
| Command | What it does |
|---|---|
grasp demo | Open the review page on two sample Claude Code sessions. Nothing to set up, nothing is kept. |
grasp init | Set up Claude Code in this project. Merges into existing config files, never overwrites them. |
grasp serve [-addr] | The review page, on 127.0.0.1:7080 by default. |
grasp pr | Load a branch or pull request from git; -explain adds Claude's decisions and examples. |
grasp import | Load Claude Code transcripts. |
grasp feedback | Print reviewer feedback as Markdown instructions (the same text the agent gets). |
grasp mcp | The MCP server the agent starts: record_decision, show_behavior, get_review_feedback. |
grasp hook | Claude Code hook entry point. Always exits 0, so it never blocks the agent. |
State lives in .grasp/ in your project: parsed sessions, reviews.json (commit it to share verdicts with your team) and decisions.jsonl (decisions from agents grasp has no transcript for).
Safety
show_behavior runs shell commands the agent writes, from your project folder, so treat it like giving the agent shell access: approve it per call, or allow it only where you would allow the agent's own shell. The "before" side runs in a temporary git worktree of the commit the session started on; your working files are never touched. Each run is stopped after 90 seconds, along with anything it started in the background.
Other agents
Any MCP-capable agent can call record_decision and get_review_feedback; those decisions show up in an *agent log* session. Full timelines (edits, commands, Watch mode) currently come from Claude Code transcripts. Adapters for other agents' logs are welcome.
Status
Early, and built in the open. Tested end to end with Claude Code on a sample service (docs/example.md). Ideas next: checking decisions against a written spec, a GitHub PR check that blocks merges with rejected decisions, and team views across many sessions.
License
MIT