@whenlabs/when
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.
Install
npx @whenlabs/when installOne-time setup. The installer:
- Registers a single MCP server (
whenlabs) in your Claude Code configuration - Injects a CLAUDE.md block so Claude knows when to use each tool
- Cleans up any legacy
velocity-mcpregistration (velocity is now bundled)
The six tools
| 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 |
MCP tools
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 |
