A
licenseNot graded
qualityB
maintenanceEnables AI agents to delegate tasks, run adversarial reviews, and manage background jobs across multiple models and providers via anymodel_* tools.
Apache 2.0
Async Hero
by NathanNT
Related Servers
Alternatives to Async Hero
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Codex to delegate bounded code analysis, review, isolated edits, multimodal research, and native image generation to supervised Antigravity workers, with queued execution, retries, and inspectable patches.232MIT
- AlicenseNot gradedqualityDmaintenanceEnables Codex to offload expensive code reading, editing, and checking to a worker agent via Claude Code, supporting async jobs and long-running tasks.MIT
- AlicenseAqualityCmaintenanceEnables an orchestrator like Claude Code to hand coding work off to Cursor SDK agents, run as detached background jobs that survive the session and can be listed, inspected, steered, resumed, or stopped. Agents are asynchronous and reusable across follow-up turns, letting expensive frontier models delegate cheaply without blocking or paying to read the results.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code, Codex, and others to offload bounded background tasks (e.g., repository scans, reviews, batch work) to smaller models configured in OMP, while the parent agent retains context and decision-making.MIT
- FlicenseNot gradedqualityAmaintenanceEnables a primary coding assistant to delegate tasks in parallel to specialized local sub-agents, sharing project context and synthesizing their responses into a single result.-
TDQS
A3.6/5.0
Scored across 10 tools
Disambiguation4/5
The singular/plural pairs (start_job/start_jobs, get_job/get_jobs, get_result/get_results, cancel_job/cancel_jobs) are clearly distinguished by cardinality, and list_jobs/list_worker_profiles target different resources. The only minor ambiguity is between get_job and get_result, but descriptions clarify that get_result is for completed results.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: start, get, list, cancel, and list_worker_profiles is the only compound noun but still fits the pattern. Singular and plural forms are used systematically.
Tool Count5/5
10 tools is well-scoped for a job queueing and management server. Each tool serves a distinct purpose, and the singular/plural pairs cover both single-item and batch operations without unnecessary bloat.
Completeness4/5
The surface covers the full job lifecycle: create, read, list, cancel, and retrieve results. A minor gap is the lack of an explicit retry or delete operation, but the core workflow is complete.
Maintenance
ActivitySlowing
ResponsivenessNo issues