migrate_subtasks

Convert subtasks into tasks with parentId for unlimited nesting depth, ensuring data compatibility after system upgrades. Specify the working directory to migrate subtask data seamlessly.

Instructions

Migrate existing subtasks to the unified task model. This tool converts all subtasks to tasks with parentId for unlimited nesting depth. Run this once after upgrading to ensure data compatibility.

Input Schema

Name	Required	Description	Default
`workingDirectory`	Yes	The full absolute path to the working directory where data is stored. MUST be an absolute path, never relative. Windows: "C:\Users\username\project" or "D:\projects\my-app". Unix/Linux/macOS: "/home/username/project" or "/Users/username/project". Do NOT use: ".", "..", "~", "./folder", "../folder" or any relative paths. Ensure the path exists and is accessible before calling this tool. NOTE: When server is started with --claude flag, this parameter is ignored and a global user directory is used instead.

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "workingDirectory": {
      "description": "The full absolute path to the working directory where data is stored. MUST be an absolute path, never relative. Windows: \"C:\\Users\\username\\project\" or \"D:\\projects\\my-app\". Unix/Linux/macOS: \"/home/username/project\" or \"/Users/username/project\". Do NOT use: \".\", \"..\", \"~\", \"./folder\", \"../folder\" or any relative paths. Ensure the path exists and is accessible before calling this tool. NOTE: When server is started with --claude flag, this parameter is ignored and a global user directory is used instead.",
      "type": "string"
    }
  },
  "required": [
    "workingDirectory"
  ],
  "type": "object"
}

Agentic Tools MCP Server

migrate_subtasks

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Agentic Tools MCP Server

Related Tools

MCP directory API