Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Compact, source-linked context packs that reduce token waste for coding agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"capsule": {
"command": "npx",
"args": [
"-y",
"capsulectx"
]
}
}
}Run this in your terminal
claude mcp add capsule -- npx -y capsulectxPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capsule": {
"command": "npx",
"args": [
"-y",
"capsulectx"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"capsule": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"capsulectx"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account dawitlabs, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.3) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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