Skip to main content
Glama
musharna

jobd

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jobd

No user-submitted related servers found.

    Related Servers

    • clausius

      tamohannes
      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
      -
    • jungle-grid-mcp-server by Jungle-Grid

      jungle-grid-mcp-serverofficial

      Jungle-Grid
      A
      license
      A
      quality
      B
      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

    • Agent-MQ

      bababoi-bibilabu
      A
      license
      B
      quality
      D
      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

    • gpusmarket

      jyswee
      A
      license
      Not graded
      quality
      B
      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.
      387 npm
      1
      -
    • Awaitless by xpluspro

      Awaitlessofficial

      xpluspro
      A
      license
      A
      quality
      A
      maintenance
      Durable MCP server for managing long-running jobs locally, over SSH, or on Slurm clusters. Jobs survive client disconnects and return exit codes, bounded logs, and JSON artifacts.
      11
      1
      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 9 tools

    Disambiguation4/5

    Each tool has a clearly targeted purpose: submit, list, status, logs, events, cancel, preempt, worker list, and worker delete are all distinct. The only mild ambiguity is between cancel and preempt for running jobs, but descriptions clarify the preemptible requirement and final state.

    Naming Consistency4/5

    All tools share a consistent 'jobd_' prefix, but verb placement varies: some are imperative verbs (jobd_submit, jobd_cancel), some are nouns (jobd_events, jobd_status), and one is noun-verb (jobd_worker_delete). This is mostly readable but not perfectly uniform.

    Tool Count5/5

    Nine tools is a well-scoped set for a job broker: job lifecycle, monitoring, debugging, and worker management are each covered without unnecessary redundancy. The count feels appropriate for the domain.

    Completeness4/5

    The core job lifecycle is covered: submit, list, status, cancel, preempt, logs, events, and worker fleet management. Minor gaps like job deletion/purging or retry/resubmit are absent, but agents can work around those with existing tools.

    Maintenance

    ActivityNo data
    ResponsivenessWithin a week

    Resources