Skip to main content
Glama
jaguarkyng

Jungle Grid MCP Server

by jaguarkyng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Jungle Grid MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      14 npm
      4
      MIT

    • 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

    • LinkedRun

      ShiroganeKaichou
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to submit and manage persistent, dependency-aware task graphs with immutable artifacts, resource reservations, durable event streaming, and retryable process execution over MCP.
      12
      MIT

    • Skills Master MCP Server

      jaisol-inc
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to invoke remote inference tasks from a local MCP client, handling file upload, job submission and polling, result download, cancellation, and account/billing checks.
      17 npm
      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 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: inputs, estimates, jobs, events, logs, and artifacts are clearly separated. get_job, get_job_events, and get_job_logs could overlap, but their descriptions draw clear boundaries around status, platform lifecycle events, and paginated logs respectively.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern, with list_* for collections and get_* for individual resources. Verbs are specific and predictable across upload, estimate, submit, list, get, and cancel.

    Tool Count5/5

    At 11 tools, the surface is well-scoped for a job-submission and artifact-retrieval workflow. Each tool maps to a necessary step in the lifecycle without redundant or filler operations.

    Completeness5/5

    The tool set covers the full workflow: upload inputs, estimate cost, submit jobs, monitor status/events/logs, cancel jobs, and retrieve artifacts. Minor conveniences like deleting old inputs are absent, but no essential operation for the stated purpose appears to be missing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources