Skip to main content
Glama

Related Servers

Alternatives to Agent Jobs MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to list, create, update, run, pause, resume, and delete scheduled shell-script jobs, pass inputs, and read job outputs and message feed entries.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables host agents to launch and supervise durable, long-horizon AI jobs—starting, running, resuming, checking budgets, and inspecting assembled context—so tasks can survive restarts and outlive the conversation with verified completion.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables orchestrating AI agents by spawning, stopping, and monitoring them, assigning asynchronous tasks, and sharing results via persistent storage.
      14
      MIT

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific resource or action: cancel_job, create_job, get_job, get_jobs_stats, get_job_type, and list_jobs are all well-defined and non-overlapping. An agent can easily distinguish between them based on their names and descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern throughout, using snake_case uniformly. The verbs (cancel, create, get, list) are clear and predictable, making the set easy to navigate and understand without any deviations or mixed conventions.

    Tool Count5/5

    With 6 tools, the server is well-scoped for managing agent jobs. Each tool earns its place by covering essential operations like creation, retrieval, listing, cancellation, statistics, and job type handling, without being too sparse or bloated for the domain.

    Completeness4/5

    The tool surface provides strong coverage for the agent jobs domain, including CRUD-like operations (create, get, list, cancel) and additional utilities (stats, job type). A minor gap exists in update operations (e.g., update_job), but agents can likely work around this by recreating jobs or using other methods.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues