Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"whenlabs": {
"args": [
"@whenlabs/when",
"when-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@whenlabs/when' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @whenlabs/when against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Read, write, and manage files on the local filesystem
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
MCP Security Weekly
Get CVE alerts and security updates for io.github.WhenLabs-org/when and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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/<tool> --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