task-orchestrator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILE_PATH | No | Path to JSON file for task storage |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createTaskA | Create a new task with optional parent and index positioning. This tool initiates a new workflow for handling user requests. To manage tasks, you MUST always run this tool first. The workflow is as follows:
|
| getTaskB | Get a task by its ID |
| listTasksA | List tasks from hierarchical structure, optionally filtered by parentId. Returns root tasks if no parentId specified, or direct children of specified parent task. |
| updateTaskC | Update an existing task |
| deleteTaskC | Delete a task by its ID |
| startTaskB | Start a task (change status to in_progress)
|
| completeTaskB | Complete a task and get the next task to execute.
To start the next task, execute |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/108yen/task-orchestrator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server