Skip to main content
Glama
Sign In
task-orchestrator-mcp

task-orchestrator-mcp

by 108yen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

task-orchestrator-mcp

NPM Version codecov MIT License

task-orchestrator-mcp is an MCP (Model Context Protocol) server that provides a set of tools for managing tasks. It enables agents to perform CRUD operations on tasks and manage their progress.

Features

The main tools provided by task-orchestrator-mcp are as follows:

Tool Name

Description

createTask

Create a new task

getTasks

Retrieve all tasks

getTask

Retrieve a task by specified ID

updateTask

Update a task by specified ID

deleteTask

Delete a task by specified ID

startTask

Start a task (change status to 'in_progress')

completeTask

Complete a task and find the next task to execute

Related MCP server: agent-scheduler

Usage

FILE_PATH is optional.

{
  "mcpServers": {
    "task-orchestrator-mcp": {
      "command": "npx",
      "args": ["-y", "task-orchestrator-mcp"],
      "env": {
        "FILE_PATH": "path/to/json_file.json"
      }
    }
  }
}

VS Code Installation Instructions

For quick installation, use one of the one-click installation buttons below:

Install with NPX in VS Code

For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open Settings (JSON).

Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.

{
  "servers": {
    "task-orchestrator-mcp": {
      "command": "npx",
      "args": ["-y", "task-orchestrator-mcp"]
    }
  }
}

Available Tools

7 tools
completeTaskB

Complete a task and get the next task to execute. To start the next task, execute startTask.

Inputs: id (required), resolution (required).

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:

  1. Create tasks with the provided name and optional description. Tasks are organized in a hierarchical structure where subtasks can be created by specifying parentId.

  2. Tasks are ordered by their position in the parent's tasks array. Use insertIndex to specify position (defaults to end).

  3. After task creation, you MUST call the startTask tool to begin processing the task.

  4. When the task is completed, call the completeTask tool with the task ID and resolution details.

  5. If the following task is assigned, execute it by calling the startTask tool again.

  6. Repeat this cycle until all tasks are completed.

Inputs: name (required), completion_criteria, constraints, description, +3 more.

deleteTaskC

Delete a task by its ID

Inputs: id (required).

getTaskB

Get a task by its ID

Inputs: id (required).

listTasksA

List tasks from hierarchical structure, optionally filtered by parentId. Returns root tasks if no parentId specified, or direct children of specified parent task.

Inputs: parentId.

startTaskB

Start a task (change status to in_progress)

  1. Run this tool to start the task.

  2. When the task is complete, call the completeTask tool to complete the task.

Inputs: id (required).

updateTaskC

Update an existing task

Inputs: id (required), description, name, resolution, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: createTask initiates tasks, getTask retrieves a single task, listTasks retrieves multiple tasks, updateTask modifies tasks, deleteTask removes tasks, startTask begins task execution, and completeTask finishes execution and triggers the next step. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with camelCase styling (e.g., createTask, getTask, listTasks, updateTask, deleteTask, startTask, completeTask). This uniformity makes the tool set predictable and easy to understand.

    Tool Count5/5

    With 7 tools, this server is well-scoped for task orchestration, covering the full lifecycle from creation to completion. Each tool serves a necessary function without redundancy, making the count ideal for the domain.

    Completeness5/5

    The tool set provides complete CRUD and lifecycle coverage for task management: create, read (get and list), update, and delete operations, plus start and complete actions for execution flow. There are no gaps that would hinder an agent from managing tasks end-to-end.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches