Skip to main content
Glama
Konjkov

casino-mcp

by Konjkov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to casino-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      28 PyPI
      1
      MIT

    • qe2mcp

      mitsuaki1987
      A
      license
      Not graded
      quality
      C
      maintenance
      Converts Quantum ESPRESSO output files to structured JSON and serves them via an HTTP API for use with MCP clients.
      MIT

    • saturday-materials

      toki0413
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run materials computation workflows through tools for loading structures, relaxing potentials, screening doped variants, analyzing phonons and elasticity, sampling candidates, and replaying trajectories. It exposes these capabilities over stdio or streamable HTTP, adapting available engines and structure sources to the environment.
      19 npm
      MIT

    • mikezero-mcp

      Ultron-1-7
      A
      license
      A
      quality
      C
      maintenance
      Enables headless control of DHI MIKE Zero, including launching and batch-running simulations, monitoring job progress and logs, and reading/plotting simulation results from DFS and RES1D files.
      15
      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.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool addresses a distinct lifecycle stage: preparing a directory, launching/interrupting a run, listing/checking jobs, and extracting physics results. Status and list_jobs are adjacent, but one is explicitly per-job detail while the other is an overview, so there is no real ambiguity.

    Naming Consistency4/5

    All tools share the casino_ prefix and use snake_case, but the pattern mixes simple verbs (run, prepare, stop), a verb-object phrase (list_jobs), and bare nouns (status, results). This is readable and predictable, though not a uniform verb_noun convention.

    Tool Count5/5

    Six tools is a well-scoped set for a job-management server. Each tool covers a necessary action without redundancy, and the count sits comfortably in the ideal 3-15 range.

    Completeness5/5

    The tool surface covers the full CASINO workflow: prepare a calculation, run or restart it, monitor it, stop it, and retrieve physics results. Missing cleanup or job-forgetting operations are not essential to the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources