Skip to main content
Glama
xpluspro

Awaitless

Official
by xpluspro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Awaitless

No user-submitted related servers found.

    Related Servers

    • script-runner

      oyren-ai
      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.
      -

    • mcp-longjobs

      ljppanda
      A
      license
      A
      quality
      B
      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
      16 npm
      MIT

    • mcp-sidecar

      lsequeiraa
      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

    • mcp-job-queue

      tommypj
      A
      license
      A
      quality
      D
      maintenance
      Enables MCP clients to submit long-running jobs that are executed safely in isolated child processes with a durable SQLite queue, configurable timeouts, retries with backoff, and backpressure.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources