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
      9 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
      F
      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.
      76 npm
      1
      -

    • agent-gpu-pool

      AlfredQuan
      A
      license
      B
      quality
      C
      maintenance
      Provides a persistent compute queue for AI agents, enabling them to submit hardware-aware GPU jobs, monitor execution, and retrieve results and artifacts across sessions via MCP tools.
      13
      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.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation: status/logs/cancel/preempt/list/events/workers/worker_delete/submit. There is no overlap between them; even status vs events are clearly differentiated (state snapshot vs why-events).

    Naming Consistency5/5

    All tools follow a consistent jobd_<verb> or jobd_<noun>_<verb> pattern (jobd_status, jobd_logs, jobd_cancel, jobd_preempt, jobd_list, jobd_events, jobd_workers, jobd_worker_delete, jobd_submit). The pattern is uniform and predictable.

    Tool Count5/5

    9 tools is well-scoped for a job scheduling/broker domain: submit, inspect (status/logs/list/events), control (cancel/preempt), and fleet management (workers/worker_delete). Each tool earns its place.

    Completeness4/5

    The surface covers the full job lifecycle: submit, status, logs, cancel, preempt, list, events, and worker management. Minor gaps like resubmit or job deletion are absent, but the core scheduling workflow is complete.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources