Skip to main content
Glama

Related Servers

Alternatives to jobd

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Your AI agents won't set your GPU on fire. GPU/CPU/RAM scheduler + market maker for AI coding agents (Claude Code, Codex, Gemini, Cursor, Grok, OpenCode, Kimi, Copilot and more) sharing one PC. Any mix of GPUs, MCP server, one-command install, Windows/macOS/Linux.
      5
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for monitoring and managing multi-cluster Slurm GPU jobs, enabling AI agents to execute commands, check allocations, and explore logs across HPC clusters.
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      Jungle Grid MCP Server lets AI agents submit, estimate, monitor, and retrieve logs for GPU workloads through Jungle Grid. It enables agentic execution for inference, training, fine-tuning, and batch jobs without manually choosing GPU providers or infrastructure.
      8
      24 npm
      4
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      agent-mq is a message queue that enables AI coding agents to communicate with each other across sessions and machines. Agents can send messages, delegate tasks, and coordinate work — all through MCP tools. Supports Claude Code, Cursor, Codex, OpenClaw, and any MCP-compatible tool. UUID-based authentication with per-user data isolation. Self-hostable with Docker.
      7
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for renting real GPUs from the terminal. Enables browsing, renting, chatting, managing, and pooling GPU instances with per-second billing, designed for AI agents.
      1
      -

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a clear resource+action target, and the descriptions explicitly route between near-neighbors (jobd_list is a compact summary vs jobd_status for the full record vs jobd_events for 'why'). The remaining overlap is small but real: jobd_status and jobd_events both claim to help debug stalled/failed jobs, and jobd_cancel vs jobd_preempt both stop a job, distinguishable only by the preemptible qualifier.

    Naming Consistency4/5

    All names use a uniform jobd_ prefix with snake_case and short, readable tokens. There is minor inconsistency in that some entries are verbs (submit, cancel, preempt, list) while others are bare nouns (status, logs, events, workers), and jobd_worker_delete uses a compound resource_action form unlike the rest.

    Tool Count5/5

    Nine tools is well within the sweet spot and each maps to a distinct part of the job lifecycle or fleet surface. No obvious filler or redundant wrapper tools.

    Completeness4/5

    Core job lifecycle (submit, inspect, list, logs, cancel, preempt) and worker observability are covered, but there are gaps: no job delete/purge for finished records, no retry/resubmit, no worker registration/drain (only delete), and profiles/requires are referenced in status output yet have no management tools.

    Maintenance

    ActivityActive
    ResponsivenessLimited data