Explore
Contribute
Sign In
Task Orchestrator

Task Orchestrator

Model Context Protocol (MCP) server for comprehensive task and feature management, providing AI assistants with a structured, context-efficient way to interact with project data.

42 Tools

Add to Docker Desktop

Version 4.43 or later needs to be installed to add the server automatically

OverviewTools (42)
Github repository⁠

Tools

NameDescription
create_featureCreate a new feature with required and optional fields. ## Purpose Features provide higher-level organization for related tasks, representing coherent functionality or project components. They bridge the gap between individual tasks and overall project goals. ## Feature vs Task Decision Guide **Create a Feature when**: - Work involves multiple related tasks (3+ tasks) - Functionality represents a user-facing feature or system component - Work has distinct phases (planning, development, testing, deployment) - Multiple developers or skill sets are involved - Work has independent business value or can be delivered as a unit **Use Direct Tasks when**: - Work is a single, focused implementation - Maintenance, bug fixes, or small enhancements - Infrastructure or tooling improvements - Work doesn't logically group with other tasks ## Template Integration Strategy **RECOMMENDED**: Apply templates at creation for consistent documentation structure. **Feature-Level Templates** (use `list_templates` with targetEntityType="FEATURE"): - Context & Background: Project context and business requirements - Requirements Specification: Detailed functional and non-functional requirements - Technical Approach: High-level architecture and technical strategy **Template Combinations for Features**: - **Planning Phase**: Context & Background + Requirements Specification - **Technical Phase**: Requirements Specification + Technical Approach - **Comprehensive**: All three templates for complex features ## Feature Lifecycle Management **Status Progression**: 1. `planning` - Requirements gathering, design, scope definition 2. `in-development` - Active implementation across multiple tasks 3. `completed` - All associated tasks completed, feature delivered 4. `archived` - Feature complete and no longer under active development **Priority Guidelines**: - `high`: Core functionality, user-facing features, business critical - `medium`: Important enhancements, internal tools, performance improvements - `low`: Nice-to-have features, experimental functionality ## Organizing Tasks Under Features **After creating a feature**, use the featureId in `create_task` to associate tasks: ```json { "title": "Implement OAuth Login", "summary": "Create OAuth authentication endpoints", "featureId": "feature-uuid-here", "templateIds": ["task-template-uuid"] } ``` **Task Organization Patterns**: - **Frontend + Backend**: Separate tasks for UI and API implementation - **By Component**: Database, API, UI, Tests as separate tasks - **By Phase**: Research, Implementation, Testing, Documentation - **By Complexity**: Break large features into manageable task chunks ## Integration with Project Hierarchy **Project → Features → Tasks** hierarchy: - Use projectId to associate feature with a project - Features group related functionality within a project - Tasks represent specific implementation work within features ## Best Practices **Naming Conventions**: - Use noun phrases describing functionality: "User Authentication", "Payment Processing" - Avoid implementation details in names: "OAuth Integration" not "Implement OAuth" - Be specific enough to distinguish from other features **Summary Guidelines**: - Include business value and user impact - Mention key technical components or integrations - Define success criteria or completion indicators - Keep scope clear and bounded **Tagging Strategy**: - Include functional area: "authentication", "payments", "reporting" - Add technical stack: "frontend", "backend", "database", "api" - Mark business importance: "core", "enhancement", "experimental" - Include user-facing impact: "user-experience", "admin-tools", "internal" Example successful response: { "success": true, "message": "Feature created successfully with 2 template(s) applied, creating 5 section(s)", "data": { "id": "550e8400-e29b-41d4-a716-446655440000", "name": "User Authentication System", "summary": "Complete user authentication system with OAuth 2.0, JWT tokens, and social login integration. Provides secure user registration, login, password reset, and session management.", "status": "planning", "priority": "high", "createdAt": "2025-05-10T14:30:00Z", "modifiedAt": "2025-05-10T14:30:00Z", "tags": ["core", "authentication", "security", "user-experience", "oauth"], "appliedTemplates": [ { "templateId": "context-background-uuid", "sectionsCreated": 2 }, { "templateId": "requirements-spec-uuid", "sectionsCreated": 3 } ] } } For feature creation patterns and best practices, see: task-orchestrator://guidelines/task-management Common error responses: - VALIDATION_ERROR: When provided parameters fail validation (empty name/summary) - RESOURCE_NOT_FOUND: When specified projectId or templateIds don't exist - DATABASE_ERROR: When there's an issue storing the feature or applying templates - INTERNAL_ERROR: For unexpected system errors
get_overviewRetrieves a lightweight, token-efficient overview of tasks and features. ## Purpose This tool provides a hierarchical project overview optimized for context efficiency. Essential for understanding current work state and making informed task planning decisions. ## Usage Guidance **RECOMMENDED WORKFLOW START**: Always begin work sessions with get_overview to: - Understand current project state and priorities - Identify in-progress tasks that need attention - Plan new work based on existing features and tasks - Locate orphaned tasks that might need feature association ## Data Organization - **Features**: Top-level functionality groupings with their associated tasks - **Orphaned Tasks**: Tasks not associated with any feature (may need organization) - **Hierarchical View**: Tasks organized under their parent features for clear context - **Essential Metadata**: Status, priority, complexity without full content for efficiency ## Context Efficiency Features - Configurable summary length (0-200 chars) to control token usage - Essential metadata only (no full task content or sections) - Hierarchical organization reduces cognitive overhead - Count summaries provide quick project metrics ## Integration with Other Tools Use this overview to inform decisions for: - `create_task`: Understand existing work before creating new tasks - `create_feature`: Identify orphaned tasks that could be grouped - `update_task`: Find tasks that need status updates - `search_tasks`: Narrow down specific searches based on overview insights ## Best Practices - Run get_overview at the start of work sessions - Use summaryLength=0 when you only need structure and metadata - Use summaryLength=100-200 when you need content context - Pay attention to orphaned tasks - they may need feature association - Monitor task status distribution across features Example response: { "success": true, "message": "Task overview retrieved successfully", "data": { "features": [ { "id": "661e8511-f30c-41d4-a716-557788990000", "name": "User Authentication", "status": "in-development", "summary": "Implements secure user authentication mechanisms with OAuth 2.0 and JWT tokens...", "tasks": [ { "id": "550e8400-e29b-41d4-a716-446655440000", "title": "Implement OAuth Authentication API", "summary": "Create secure authentication flow with OAuth 2.0 protocol and JWT token management...", "status": "in-progress", "priority": "high", "complexity": 8, "tags": "task-type-feature, oauth, authentication, api" } ] } ], "orphanedTasks": [ { "id": "772f9622-g41d-52e5-b827-668899101111", "title": "Setup CI/CD Pipeline", "summary": "Configure automated build and deployment pipeline using GitHub Actions...", "status": "pending", "priority": "medium", "complexity": 6, "tags": "task-type-infrastructure, ci-cd, automation" } ], "counts": { "features": 5, "tasks": 23, "orphanedTasks": 7 } } }
list_templatesRetrieve a list of templates with optional filtering. ## Purpose CRITICAL for template-driven workflow: Always check available templates before creating tasks or features to ensure consistent documentation structure and comprehensive coverage. ## Template System Overview The system provides focused, composable templates organized into categories: **AI Workflow Instructions** (process guidance): - Local Git Branching Workflow: Step-by-step git workflow with MCP tool integration - GitHub PR Workflow: Complete PR creation and management process - Task Implementation Workflow: Structured implementation approach - Bug Investigation Workflow: Systematic bug analysis and resolution **Documentation Properties** (information capture): - Technical Approach: Architecture and implementation strategy - Requirements Specification: Detailed requirements and acceptance criteria - Context & Background: Project context and background information **Process & Quality** (standards and completion): - Testing Strategy: Comprehensive testing approach and coverage - Definition of Done: Clear completion criteria and quality gates ## Usage Patterns **RECOMMENDED WORKFLOW**: 1. Run `list_templates` with targetEntityType filter (TASK or FEATURE) 2. Identify templates from multiple categories for comprehensive coverage 3. Apply templates during create_task/create_feature using templateIds parameter 4. Use template combinations: Workflow + Documentation + Quality ## Template Selection Strategy **For Implementation Tasks**: - Technical Approach + Task Implementation Workflow + Testing Strategy **For Bug Fixes**: - Bug Investigation Workflow + Technical Approach + Definition of Done **For Complex Features**: - Requirements Specification + Technical Approach + Local Git Branching + Testing Strategy **For Feature Planning**: - Context & Background + Requirements Specification + Testing Strategy ## Filtering Best Practices - Filter by targetEntityType to match your creation needs (TASK vs FEATURE) - Use isEnabled=true to only see available templates - Filter by tags to find domain-specific templates ("authentication", "api", "testing") - Built-in templates (isBuiltIn=true) provide proven workflow patterns ## Context Efficiency Templates are designed for modular composition rather than monolithic coverage: - Small, focused templates (3-4 sections each) reduce cognitive overhead - Composable design allows mixing based on specific needs - Category-based organization helps with systematic selection Example successful response: { "success": true, "message": "Retrieved 8 templates", "data": { "templates": [ { "id": "workflow-uuid-001", "name": "Task Implementation Workflow", "description": "Step-by-step implementation guidance with MCP tool integration", "targetEntityType": "TASK", "isBuiltIn": true, "isProtected": true, "isEnabled": true, "tags": ["workflow", "implementation", "process"] }, { "id": "tech-uuid-002", "name": "Technical Approach", "description": "Architecture and implementation strategy documentation", "targetEntityType": "TASK", "isBuiltIn": true, "isProtected": true, "isEnabled": true, "tags": ["technical", "architecture", "documentation"] }, { "id": "test-uuid-003", "name": "Testing Strategy", "description": "Comprehensive testing approach and coverage requirements", "targetEntityType": "TASK", "isBuiltIn": true, "isProtected": true, "isEnabled": true, "tags": ["testing", "quality", "coverage"] } ], "count": 8, "filters": { "targetEntityType": "TASK", "isBuiltIn": "Any", "isEnabled": "true", "tags": "Any" } } } For template discovery patterns and selection strategies, see: task-orchestrator://guidelines/template-strategy Common error responses: - VALIDATION_ERROR: When targetEntityType is not TASK or FEATURE - DATABASE_ERROR: When there's an issue retrieving templates - INTERNAL_ERROR: For unexpected system errors
Related servers