Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
The WhenLabs developer toolkit — 6 tools, 7 MCP endpoints, one install.
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": {
"when": {
"command": "npx",
"args": [
"-y",
"@whenlabs/when"
]
}
}
}Run this in your terminal
claude mcp add when -- npx -y @whenlabs/whenPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"when": {
"command": "npx",
"args": [
"-y",
"@whenlabs/when"
]
}
}
}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": {
"when": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@whenlabs/when"
]
}
}
}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 6, 2026
The registry name was verified with the GitHub account WhenLabs-org, 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.12.3) reached the registry 7 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, FOGA node
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.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
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.
Six tools. One install.
A single installable toolkit that brings six WhenLabs developer tools into your Claude Code workflow. After install, the tools are exposed over a single MCP server and Claude calls them automatically when relevant.
npx @whenlabs/when install
One-time setup. The installer:
whenlabs) in your Claude Code configurationvelocity-mcp registration (velocity is now bundled)| Tool | Purpose |
|---|---|
| aware | Auto-detect stack and generate AI context files (CLAUDE.md, .cursorrules, …) |
| berth | Detect port conflicts before starting dev servers |
| envalid | Validate .env files against a schema |
| stale | Detect documentation drift between docs and code |
| vow | Scan dependency licenses and validate against policy |
| velocity | Time coding tasks and learn from historical data |
Eight endpoints across the six tools:
| Endpoint | What it does |
|---|---|
aware_sync | Detect stack and regenerate AI context files |
berth_check | Scan project for port conflicts |
envalid_validate | Validate .env files against schema |
stale_scan | Detect documentation drift |
vow_scan | Scan licenses and validate against policy |
velocity_start_task | Start timing a coding task |
velocity_end_task | End timing and record results |
whenlabs_summary | Unified rollup across all five scanners in one call |
All eight are served by the single whenlabs MCP server (stdio, Node 20+). Fix/init/auxiliary commands remain available via each tool's CLI (npx @whenlabs/ --help).
when init # Onboard a project — detect stack, bootstrap configs, run all checks
when doctor # Run all six tools and show a unified health report when install # Register MCP server in Claude Code when uninstall # Remove MCP server
For per-tool operations, use the tool directly:
npx @whenlabs/stale scan
npx @whenlabs/envalid validate npx @whenlabs/berth check npx @whenlabs/aware sync npx @whenlabs/vow scan
If you're not using the install command, add this to your Claude Code MCP config:
{
"mcpServers": { "whenlabs": { "command": "npx", "args": ["@whenlabs/when", "when-mcp"] } } }
MIT — see LICENSE