AgentTasker
Related Servers
Alternatives to AgentTasker
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables parallel execution of shell commands and AI coding agents (Claude, Gemini, Codex) across lists of items like files or URLs, with batched processing and real-time streaming output for batch operations.8172 npm6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables running a validated DAG of coding tasks across a pool of model workers, with independent tasks executing in parallel and dependent ones receiving upstream results. Only a pinned acceptance command's exit code 0 counts as success, with atomic task claims, leases, takeover of killed runners, and scope- and hash-checked applies that refuse to overwrite files or leak secrets.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides tools for executing shell commands both synchronously and asynchronously with real-time output streaming and process management capabilities. It enables users to start background tasks, monitor progress, and manage long-running processes via Stdio or HTTP transports.525 npmMIT
- AlicenseAqualityCmaintenanceEnables executing commands and transferring files over SSH on multiple hosts concurrently, with auto-discovery from SSH config and support for various authentication methods.36 npmMIT
- FlicenseBqualityDmaintenanceEnables safe execution of system shell commands with real-time streaming output and rich metadata capture. Provides configurable command execution with timeout controls, environment management, and extensible plugin architecture for monitoring command lifecycles.4-
- FlicenseBqualityCmaintenanceEnables parallel agent tasks on disposable Arch Linux drones by providing a local stdio gateway for batch job submission, status monitoring, log retrieval, artifact fetching, and cancellation across SSH-connected runners.13-
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: single execution, batch execution, batch retrieval, and batch cancellation. The boundaries between execute and execute_batch are especially clear, and get_batch/cancel_batch cover separate lifecycle operations.
Names use snake_case consistently and mostly follow an action_resource pattern (cancel_batch, execute_batch, get_batch). The single execute tool is a minor deviation but remains intuitive.
Four tools are well-scoped for a task execution service: run single tasks, run batches, inspect batches, and cancel batches. No tool feels redundant or out of place.
The surface covers the core execution lifecycle, including background batch retrieval and cancellation. A list_batches or batch discovery operation is absent, but returned batch_ids from execute_batch mitigate that gap.