WhenLabs/When
Related Servers
Alternatives to WhenLabs/When
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.11 npmMIT
- AlicenseAqualityCmaintenanceMCP server for developer workflow automation — smart commits, secret scanning, PR descriptions, and more.5MIT
- AlicenseNot gradedqualityBmaintenanceTurns any AI coding agent or MCP client into a governed DevOps engineer by exposing policy-enforced tools for Kubernetes, Docker, Jira, Git/PR, CI/CD, AWS, Terraform, and incident response, with approvals, audit logging, secret redaction, and rollback enforced outside the model.5Apache 2.0
- AlicenseAqualityDmaintenanceZero-config MCP server that gives AI coding assistants a real-time diagnostic snapshot of your local dev environment. Detects framework, running services, recent errors, git state, and provides a health diagnosis in one call.317 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables developers to build, test, debug, and operate MCP servers from VS Code or CI, while also exposing trusted MCP capabilities to AI agents.MIT
- AlicenseNot gradedqualityDmaintenanceEnables spec-driven development workflows with AI assistants, providing tools for managing specification lifecycles, task dependencies, code navigation, testing, and automated reviews through a unified CLI and MCP interface.4MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: aware_sync handles AI context file generation, berth_check scans for port conflicts, envalid_validate validates environment files, stale_scan detects documentation drift, velocity_start_task/velocity_end_task manage task timing, and vow_scan audits dependency licenses. The descriptions clearly differentiate their domains and use cases.
Most tools follow a consistent verb_adjective or verb_noun pattern (e.g., aware_sync, berth_check, envalid_validate, stale_scan, vow_scan), but the velocity tools use a verb_noun_task pattern which slightly deviates. The naming is generally readable and follows a predictable structure across the set.
With 7 tools, the count is well-scoped for a development productivity server. Each tool addresses a specific, valuable aspect of project maintenance (context generation, port checking, env validation, docs drift, task timing, license scanning), and none feel redundant or out of place.
The tool set provides comprehensive coverage for development workflow automation: it includes tools for setup (aware_sync), pre-execution checks (berth_check, envalid_validate), quality assurance (stale_scan, vow_scan), and productivity tracking (velocity tools). There are no obvious gaps; agents can handle common development tasks end-to-end.