MCP Task
Related Servers
Alternatives to MCP Task
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables asynchronous, event-driven orchestration of long-running AI coding agents, allowing a leader session to dispatch jobs that execute in the background, survive disconnects, and provide queryable status and resumability without blocking model turns.01MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that enables asynchronous task submission and execution through a local worker daemon, decoupled from specific providers and models, with tasks continuing even after the client disconnects.-

RunComfy MCPofficial
AlicenseAqualityBmaintenanceOfficial remote MCP server for RunComfy. 31 tools across three products: Serverless API (ComfyUI) deployment management and async inference, Model API hosted-model inference, and Trainer API LoRA training jobs.311MIT- AlicenseNot gradedqualityBmaintenanceMCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.18 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows AI assistants to manage background processes, enabling start, stop, monitoring, and querying of long-running shell commands without blocking the conversation.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Conductor workflow orchestration, enabling AI agents to create, execute, and analyze workflows.Apache 2.0
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no ambiguity: list_tasks enumerates tasks, run_task initiates tasks, check_task_status monitors progress, get_task_result retrieves final outcomes, wait_for_task blocks for completion, and cancel_task stops tasks. The descriptions clearly differentiate these functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with underscores, such as run_task, check_task_status, and cancel_task. This predictable naming convention enhances readability and usability across the tool set.
With 6 tools, the count is well-scoped for a task management server, covering the full lifecycle from creation to completion and cancellation. Each tool earns its place without redundancy or bloat, making the set efficient and focused.
The tool surface provides complete CRUD/lifecycle coverage for task management: run_task for creation, list_tasks for listing, check_task_status and wait_for_task for monitoring, get_task_result for retrieval, and cancel_task for deletion. There are no obvious gaps that would cause agent failures.