io.github.WhenLabs-org/when

Official registry Other

The WhenLabs developer toolkit — 6 tools, 7 MCP endpoints, one install.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @whenlabs/when
Claude Code
claude mcp add when -- npx -y @whenlabs/when@0.12.3
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "when": {
            "command": "npx",
            "args": [
                "-y",
                "@whenlabs/when@0.12.3"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. @whenlabs/when
  2. Install
  3. The six tools
  4. MCP tools
  5. CLI
  6. Manual MCP configuration
  7. License

@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 install

One-time setup. The installer:

  1. Registers a single MCP server (whenlabs) in your Claude Code configuration
  2. Injects a CLAUDE.md block so Claude knows when to use each tool
  3. Cleans up any legacy velocity-mcp registration (velocity is now bundled)

The six tools

ToolPurpose
awareAuto-detect stack and generate AI context files (CLAUDE.md, .cursorrules, …)
berthDetect port conflicts before starting dev servers
envalidValidate .env files against a schema
staleDetect documentation drift between docs and code
vowScan dependency licenses and validate against policy
velocityTime coding tasks and learn from historical data

MCP tools

Eight endpoints across the six tools:

EndpointWhat it does
aware_syncDetect stack and regenerate AI context files
berth_checkScan project for port conflicts
envalid_validateValidate .env files against schema
stale_scanDetect documentation drift
vow_scanScan licenses and validate against policy
velocity_start_taskStart timing a coding task
velocity_end_taskEnd timing and record results
whenlabs_summaryUnified 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).

CLI

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

Manual MCP configuration

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"]
    }
  }
}

License

MIT — see LICENSE


Built by Siddharth at WhenLabs

Frequently asked questions

What is io.github.WhenLabs-org/when?

The WhenLabs developer toolkit — 6 tools, 7 MCP endpoints, one install.

How do I install io.github.WhenLabs-org/when?

It runs on your machine. In Claude Code: claude mcp add when -- npx -y @whenlabs/when@0.12.3. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.WhenLabs-org/when need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.WhenLabs-org/when open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.WhenLabs-org/when?

It is published by WhenLabs-org. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.