Skip to main content
Glama
cpietsch

Amadeus

by cpietsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Amadeus

No user-submitted related servers found.

    Related Servers

    • slurm-mcp

      romelllo
      A
      license
      B
      quality
      C
      maintenance
      Enables users to work on a SLURM HPC cluster over SSH through plain-language requests, covering file browsing and editing, batch job generation and submission, queue monitoring, and log reading to debug failed jobs. It runs with built-in safety guardrails such as fixed commands and configurable path policies for reads and writes.
      27
      MIT

    • mcp-slurm

      tejasvinu
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage SLURM HPC clusters via SSH. Supports job submission, resource monitoring, queue management, and file operations.
      4 npm
      4
      -

    • 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

    • 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.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools are largely separable by resource and stage: job lifecycle (list/details/log/wait/check/draft/submit/update/cancel), execution (run_command vs node_exec), file transfer, diagnostics, and issue reporting. A few boundaries blur—job_details already includes log tails, and run_command/node_exec both execute commands—but the descriptions clarify context.

    Naming Consistency3/5

    All names are snake_case and readable, but the set mixes verb_noun patterns (submit_job, check_job, push_files) with noun-only names (job_details, cluster_load, budget) and noun_verb (node_exec). The convention is not uniform, though the terms remain reasonably predictable.

    Tool Count3/5

    21 tools is heavy for an MCP surface and lands in the borderline 16-25 range. The domain is broad—access, Slurm lifecycle, diagnostics, transfers, billing, issues—and no tool is obviously redundant, but the surface feels sprawling.

    Completeness4/5

    The core HPC workflow is covered thoroughly: login/access, job drafting/checking/submitting/updating/cancelling, monitoring/waiting/logs, cluster load, budget, transfers, and issue reporting. Minor gaps remain, such as no direct issue-detail/update path or general remote file listing beyond run_command, but workarounds exist.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources