start-work
Related Servers
Alternatives to start-work
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to create, list, claim, update, and log progress on markdown-based tickets stored in repositories across multiple projects. Supports shared ticket state, status workflows, and coordination between concurrent sessions.9 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to automate Jira and GitHub/GitLab workflows. It handles issues, branches, pull requests, and deployments with project-aware context and safety checks.3278 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to register, self-assign and coordinate tasks, track progress, review work, and manage GitHub Projects v2 with AI-powered PRD generation, sprint planning, issue triage, and PRD-to-issues pipelines backed entirely by GitHub-native storage.1,137 npmMIT
- AlicenseNot gradedqualityCmaintenanceGives AI coding agents native tools to pull their next prioritized, unblocked task with a full briefing (description, acceptance criteria, context files, conventions), comment and tick off criteria with evidence, ask the human decision-maker questions, and submit structured handoffs for review. It lets agents plan epics and sprints, report checks, create new tasks, and release work with checkpoints — all against a self-hosted board rather than files in the repo.4 npm1MIT
- AlicenseAqualityBmaintenanceEnables coding agents to turn Jira Cloud tickets into ready-to-build briefs, verify local branches against acceptance criteria, and prepare QA handoffs, with optional previewed and audited write-back.1081 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and project managers to turn GitHub Projects v2 into an autonomous project management platform with task checkout, multi-agent coordination, PRD-to-issue pipelines, sprint planning, triage, and GitHub-native storage.1,137 npmMIT
TDQS
Scored across 5 tools
Each tool maps to a distinct step in the workflow: listing, reading context, claiming, opening a PR, and setting status. The only mild overlap is between start_ticket (which implicitly sets in-progress) and set_ticket_status, but the descriptions clarify that start_ticket is the claim-and-brief action while set_ticket_status is for manual moves.
All five tools follow a consistent snake_case verb_noun pattern (list_my_tickets, get_ticket_context, start_ticket, open_pull_request, set_ticket_status). No mixed conventions or vague verbs.
Five tools is well-scoped for a focused start-work workflow, and each tool earns its place as a distinct step. Nothing feels redundant or missing at the count level.
The surface covers the core lifecycle: discover tickets, read context, claim, open PR, and adjust status. Minor gaps exist—no way to create tickets, add standalone comments, or search/filter beyond 'my tickets'—but these are outside the apparent narrow purpose and agents can work around them.