qkrun-mcp
Related Servers
Alternatives to qkrun-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents to submit and manage persistent, dependency-aware task graphs with immutable artifacts, resource reservations, durable event streaming, and retryable process execution over MCP.12MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to submit and manage long-running Codex Desktop tasks asynchronously, with retry-safe operations, Plan Mode approvals, diagnostics, and restart recovery.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to submit and manage durable, long-running Codex Desktop tasks asynchronously, with polling, approvals, Plan Mode workflows, retry safety, diagnostics, and recovery state.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients and orchestrators to submit long-running Codex Desktop tasks, poll their status, handle approvals and Plan Mode workflows, and retrieve final reports with diagnostics and recovery.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to submit and monitor long-running Codex Desktop tasks asynchronously, with polling, approvals, Plan Mode workflows, diagnostics, and restart recovery.-
- AlicenseNot gradedqualityBmaintenanceExposes device discovery, capabilities, observation, logs, task execution and cancellation, and evidence retrieval as tools so MCP clients can run typed mobile automation tasks and inspect proof of completion.Apache 2.0
TDQS
Scored across 2 tools
The two tools map cleanly to a discover-then-execute workflow with no overlap: list_tasks only reads metadata, run_task only executes. An agent can unambiguously pick the right tool from the description.
Both names follow the same verb_noun snake_case pattern (list_tasks, run_task), using the shared 'task' noun. Fully predictable and consistent.
Two tools is thin but coherent for a narrow task-runner domain; there is no padding. However, with only a discovery and an execution tool, the surface feels minimal rather than well-scoped.
Core flow (discover tasks and their arguments, then run with stdin/stdout/stderr handling) is covered. Gaps remain: no way to cancel or kill a running task, check status of in-flight runs, or inspect a task's schema beyond the listing.