Skip to main content
Glama

Related Servers

Alternatives to Awaitless

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server that launches user-supplied scripts inside disposable Docker containers, returning task IDs for async tracking and bounded output tails.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local stdio MCP server that lets Claude Desktop hand tasks to a Hermes Agent on the same machine and read the raw output and files back, job by job. Long work runs as background jobs that are polled by id, so Claude can plan, verify against the filesystem, and resume earlier sessions without blocking on tool timeouts.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Reference MCP server for the mcp-longjobs library: durable long-running tasks with progress polling, mid-flight input, and cooperative cancellation, plus chunked file transfers with resume cursors and sha256 verification. Works on every MCP client today — no Tasks-extension support required.
      9
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight, cross-platform MCP server for managing background processes. Enables AI coding agents to spawn, monitor, and interact with long-lived processes.
      MIT

    TDQS

    A4.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: run for default single command, submit_job for async/fan-out, run_job for MCP Tasks compatibility, wait_for_job for single job waiting, wait_for_completions for multiple jobs, get_job_status for snapshots, get_job_logs for diagnostics, plus cancel/list/queue tools. Descriptions explicitly cross-reference when not to use each, eliminating ambiguity.

    Naming Consistency5/5

    All 11 tools follow a consistent verb_noun snake_case pattern (run, submit_job, wait_for_job, wait_for_completions, get_job_status, get_job_logs, cancel_job, list_jobs, create_queue, list_queues). No style mixing or vague verbs.

    Tool Count5/5

    11 tools cover the job lifecycle and queue management without excess. Each tool has a clear role, and the count is appropriate for a job orchestration server—neither too thin nor bloated.

    Completeness5/5

    The surface covers the full lifecycle: creation (run, submit_job, run_job), waiting and collection (wait_for_job, wait_for_completions), status (get_job_status), logs (get_job_logs), cancel (cancel_job), listing (list_jobs), and queue management (create_queue, list_queues). No obvious gaps for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues