Skip to main content
Glama
CROCODILE-CESM

cesm-runner-mcp

by CROCODILE-CESM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cesm-runner-mcp

No user-submitted related servers found.

    Related Servers

    • presence-mcp

      sara-star-quant
      A
      license
      Not graded
      quality
      C
      maintenance
      PyPI-launched MCP server that exposes a living project model and outcome telemetry as read-only resources for MCP-aware clients.
      21 PyPI
      1
      Apache 2.0

    • spear-mcp-test

      zappalaja
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for accessing SPEAR model output from various sources (AWS, STAC API, local) and integrating with AI assistants like Claude Desktop or a SPEAR Climate Chatbot.
      -

    • openmc-validator-mcp

      zxkjack123
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides pre-flight validation and post-processing tools for OpenMC Monte Carlo transport simulations, catching common authoring mistakes before jobs hit the HPC queue.
      MIT

    • Penny

      kangwa
      A
      license
      A
      quality
      B
      maintenance
      MCP server for orchestrating coding tasks with frontier-model planning and local execution, enabling manifest validation, plan submission, status checks, cancellation, and report retrieval through Claude Code.
      6
      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 17 tools

    Disambiguation5/5

    All 17 tools have clearly distinct purposes, covering different stages of CESM case execution, container management, and configuration queries. No two tools appear to overlap in functionality, reducing the chance of misselection.

    Naming Consistency4/5

    Tool names consistently use lowercase with underscores and combine verbs and nouns. However, there is a minor inconsistency in order: some are verb_noun (e.g., build_sandbox) while others are noun_verb (e.g., case_build). Still, the pattern is predictable and readable.

    Tool Count5/5

    With 17 tools, the server is well-scoped for its purpose of running CESM cases. Each tool serves a distinct function without being excessive, covering setup, build, submit, monitoring, container management, and configuration.

    Completeness4/5

    The tool set covers the primary lifecycle of CESM case execution, including build, setup, submit, status checks, log tails, and XML modifications. Minor gaps like case creation or input data download are absent, but these are outside the stated 'runner' scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources