
When
io.github.WhenLabs-orgPublished by GitHub account WhenLabs-orgv0.12.3Updated Oct 24, 2026
The WhenLabs developer toolkit — 6 tools, 7 MCP endpoints, one install.
Overview
A local MCP server bundling six WhenLabs developer tools, letting an assistant scan projects for port conflicts, env schema issues, doc drift, license policy, a
- What you can do
- Detect the project stack and regenerate AI context files such as CLAUDE.md and .cursorrules, and scan for port conflicts before starting dev servers. Validate .env files against a schema and detect documentation drift between docs and code. Scan dependency licenses and check them against policy. Start and end timing for coding tasks and record results. Produce a unified rollup across the five scanners in one call.
- When to use it
- Useful for developers working in Claude Code who want project health checks — stack context files, port conflicts, env validation, doc drift, license policy and task timing — reachable from the assistant without leaving the editor.
- Requirements
- Runs locally over stdio with Node 20 or newer, installed via the npm package. The install command registers the server in the Claude Code configuration and injects a CLAUDE.md block; manual configuration is also documented. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open When in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@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.
[when doctor — six tools, one unified health report]
Install
One-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
MCP tools
Eight endpoints across the six tools:
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
For per-tool operations, use the tool directly:
Manual MCP configuration
If you're not using the install command, add this to your Claude Code MCP config:
License
MIT — see LICENSE
Source: README.md at commit c389d5f
Tools
0Version history
1- v0.12.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts