Helios-9 MCP Server

Instructions

Implementation Reference

• src/tools/tasks.ts:866-913 (handler)

  The core handler function for get_task_workflow_status. Parses arguments using the schema, fetches all tasks in the project (filtering by workflow_name is limited due to schema constraints), calculates progress statistics, retrieves dependencies, computes critical path and bottlenecks using helper functions, and returns a comprehensive status report including next actions and completion estimates.
  export const getTaskWorkflowStatus = requireAuth(async (args: any) => { const { project_id, workflow_name } = GetTaskWorkflowStatusSchema.parse(args) logger.info('Getting workflow status', { project_id, workflow_name }) // Get workflow tasks (metadata_filter not available) const tasks = await supabaseService.getTasks({ project_id // metadata_filter not available as metadata doesn't exist in database schema }) if (tasks.length === 0) { throw new Error(`Workflow "${workflow_name}" not found`) } // Calculate progress const totalTasks = tasks.length const completedTasks = tasks.filter(t => t.status === 'done').length const inProgressTasks = tasks.filter(t => t.status === 'in_progress').length const todoTasks = tasks.filter(t => t.status === 'todo').length // Get dependencies for this workflow const dependencies = await supabaseService.getProjectDependencies(project_id) const workflowDependencies = dependencies.filter(d => tasks.some(t => t.id === d.task_id) && tasks.some(t => t.id === d.depends_on_task_id) ) // Calculate critical path const criticalPath = calculateCriticalPath(tasks, workflowDependencies) // Identify bottlenecks const bottlenecks = identifyWorkflowBottlenecks(tasks, workflowDependencies) return { workflow_name, progress: { total_tasks: totalTasks, completed_tasks: completedTasks, in_progress_tasks: inProgressTasks, todo_tasks: todoTasks, completion_percentage: Math.round((completedTasks / totalTasks) * 100) }, critical_path: criticalPath, bottlenecks, next_actions: getNextWorkflowActions(tasks, workflowDependencies), estimated_completion: estimateWorkflowCompletion(tasks, workflowDependencies) } })
• src/tools/tasks.ts:861-864 (schema)

  Zod schema for input validation. Requires project_id (string) and workflow_name (string). Used in the handler to parse and validate arguments.
  const GetTaskWorkflowStatusSchema = z.object({ project_id: z.string().min(1), workflow_name: z.string().min(1) })
• src/tools/tasks.ts:842-859 (registration)

  MCPTool object defining the tool's metadata: name 'get_task_workflow_status', description, and JSON schema for inputs (project_id and workflow_name). This is exported and included in taskTools for registration.
  export const getTaskWorkflowStatusTool: MCPTool = { name: 'get_task_workflow_status', description: 'Get status and progress of a task workflow', inputSchema: { type: 'object', properties: { project_id: { type: 'string', description: 'ID of the project' }, workflow_name: { type: 'string', description: 'Name of the workflow' } }, required: ['project_id', 'workflow_name'] } }
• src/tools/tasks.ts:1157-1167 (registration)

  Central registry mapping tool names to their handler functions. Includes 'get_task_workflow_status' mapped to the getTaskWorkflowStatus handler. This is likely used by the MCP server to dispatch calls.
  export const taskHandlers = { list_tasks: listTasks, create_task: createTask, get_task: getTask, update_task: updateTask, add_task_dependency: addTaskDependency, get_task_dependencies: getTaskDependencies, create_task_workflow: createTaskWorkflow, bulk_update_tasks: bulkUpdateTasks, get_task_workflow_status: getTaskWorkflowStatus }