Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Compact, source-linked context packs that reduce token waste for coding agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"capsule": {
"command": "npx",
"args": [
"-y",
"capsulectx"
]
}
}
}在终端中运行这条命令
claude mcp add capsule -- npx -y capsulectx粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"capsule": {
"command": "npx",
"args": [
"-y",
"capsulectx"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"capsule": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"capsulectx"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 dawitlabs 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.3.3)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Rystic
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Compact, source-linked context packs for coding agents.
Docs · Quickstart · Commands
MCP gives agents tools. Skills give agents procedures. Capsules give agents compact project context.
Large repositories make coding agents burn tokens rediscovering the same files, decisions, conventions, and setup details over and over. Capsule targets a 50–70% reduction in repeated repository-discovery context for large, multi-session agent work.
No install required — run directly with npx (always gets the latest version):
npx capsulectx init
Or install globally with your package manager:
# npm
npm install -g capsulectx
pnpm add -g capsulectx
yarn global add capsulectx
bun add -g capsulectx
Keep it up to date:
npm install -g capsulectx --prefer-online
Tip:
npxis the easiest option — it always runs the latest published version with no manual update step.
npx capsulectx init
Capsule scans your repo, optionally enriches capsules with AI (using your installed Claude CLI, API keys, or a generated prompt for any browser-based AI), and creates:
.capsules/
index.md architecture.md setup.md api.md data.md ui.md testing.md deployment.md
Each capsule is a Markdown file with source fingerprints in JSON frontmatter:
---json
{ "name": "api", "sources": ["src/api/**"], "fingerprints": { "src/api/users.ts": "sha256:..." }, "updated_at": "2026-06-20T14:00:00.000Z" }
Request handlers, routes, controllers, and service boundaries.
src/api/users.ts: source file matched by this capsule.
Agents read .capsules/index.md, choose the relevant capsule, check staleness, then inspect only the source files that actually matter.
| Command | What it does |
|---|---|
capsule init | Scan repo, run AI enrichment (optional), write all capsules |
capsule enrich | Re-run AI enrichment on existing capsules |
capsule apply | Apply AI-generated JSON to capsule Conventions and Decisions |
capsule write | Refresh one capsule from source (preserves your edits) |
capsule refresh | Explicitly refresh one capsule |
capsule refresh --all | Explicitly refresh all detected capsules |
capsule get | Print one capsule to stdout |
capsule scan | Print detected source groups without writing |
capsule stale [name] | Check which source files changed since last write |
capsule estimate | Show estimated token savings for one capsule |
capsule stats | Show token savings across all capsules |
capsule report [name] | Show reproducible source/capsule/stale token savings |
capsule report --write | Write .capsules/report.md as a proof artifact |
capsule check | CI-friendly freshness/config check; exits nonzero on stale or missing capsules |
capsule --mcp | Start MCP server for native agent integration |
Capsule ships an MCP server so Claude Code and other MCP-compatible agents can natively discover and consume capsules — no manual file reads needed.
Add to your project's `.claude/settings.json`:
{
"mcpServers": { "capsule": { "command": "npx", "args": ["capsulectx", "--mcp"] } } }
Or globally in `~/.claude/settings.json` to enable for all projects.
Once configured, agents get these tools automatically:
| Tool | What it does |
|---|---|
capsule_list | List all capsules with freshness status |
capsule_get | Read a capsule's compressed context; warns when stale but does not write |
capsule_refresh | Explicitly refresh one capsule or all capsules |
capsule_stale | Check which capsules have outdated sources |
capsule_stats | Show token savings per capsule |
capsule_report | Show machine-readable discovery-savings proof |
capsule_check | CI-style stale/missing/config check |
capsule_init | Generate capsules for the current repo |
Capsules are also available as MCP resources at capsule:///index and capsule:///{name}.
$ capsule report architecture
Capsule: architecture
capsule status source capsule stale saved architecture fresh 9,607 417 0 96%
Token counts use the cl100k_base tokenizer for accurate measurement.
For CI, run:
npx capsulectx check
It exits nonzero when capsules are stale, missing, or blocked by invalid config.
Add this to AGENTS.md, CLAUDE.md, Cursor rules, or your agent instructions:
Before working in this repo:
.capsules/index.md if it exists.capsule stale when the CLI is available.
Works with any agent that can read files — Claude Code, Codex, Cursor, Windsurf, Devin, custom MCP agents.
Capsule detects standard layouts out of the box. For non-standard structure, add .capsules/config.json:
{
"groups": [ { "name": "workers", "description": "Background jobs, queues, and scheduled tasks.", "sources": ["src/workers/", "src/jobs/"] } ], "ignore": ["legacy/**"] }
A groups entry with the same name as a default group overrides it. New names are appended. ignore patterns extend the default ignore list.
See docs/capsule-format.md for the public capsule file format.
The animation in this README is a generated GIF — no screen-recording tools required.
npm run demo
Requires rsvg-convert (librsvg / librsvg2-tools) and ffmpeg. The script outputs docs/demo.gif from SVG frames rendered at 2× for retina. See scripts/build-demo.mjs.
The OSS docs live in docs-site/ and are built with VitePress.
npm run docs:dev
npm run docs:build
Capsule is early but functional. Current capabilities:
report and CI-friendly check.capsules/config.jsonCLAUDE.md, AGENTS.md, .cursorrules, .windsurfrules with capsule instructionsRoadmap:
write that diffs source changes and suggests targeted updatescapsule checkgit clone https://github.com/dawitlabs/capsule.git
cd capsule npm install npm run build node dist/cli.js init
MIT