Skip to main content
Glama
Sign In
wyoloservice2_mcp

wyoloservice2_mcp

by wisrovi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to wyoloservice2_mcp

No user-submitted related servers found.

    Related Servers

    • ml-lab-mcp

      CyrusTao
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to manage and run machine learning training jobs on a remote server, including syncing code, submitting experiments, monitoring progress, reading TensorBoard metrics, and receiving completion notifications.
      -

    • ai-toolkit-mcp

      shhlife
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to set up, launch, monitor, and manage LoRA training runs through the ai-toolkit web UI API, including datasets, captions, job configuration, checkpoints, logs, loss curves, and sample images.
      19
      MIT

    • gpuctl-mcp

      EricYuan2007
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage GPU training end-to-end through natural language, including submitting and scheduling jobs, monitoring logs and metrics, diagnosing failures, comparing runs, and recommending the best checkpoints.
      Apache 2.0

    • clu

      QiandingHuang666
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to run remote commands and manage Slurm cluster jobs over persistent, pooled SSH sessions, with tools for job submission, cancellation, job status/logs, connection state, and querying a cross-session execution ledger.
      17
      132 PyPI
      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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: canceling, checking paths, generating YAML, cluster status, study details, launching, credentials, and dataset validation. No overlapping functionality.

    Naming Consistency5/5

    All tools use snake_case with a consistent verb_noun pattern (e.g., cancel_study, generate_training_yaml). There are no naming convention conflicts.

    Tool Count5/5

    8 tools is appropriate for the server's scope—covering credential setup, dataset validation, YAML generation, training launch, monitoring, and cancellation. No unnecessary tools.

    Completeness4/5

    The toolset covers the core training lifecycle, but lacks a tool to list existing studies or modify credentials after setup. The workflow instructs agents to find study IDs from local YAML files, which is a reasonable workaround.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources