Skip to main content
Glama
ssciwr-courses

climate-mcp-server

by ssciwr-courses
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to climate-mcp-server

No user-submitted related servers found.

    Related Servers

    • climate-example

      ssciwr-courses
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to validate climate processing configs, inspect available sample data, and run a climate data pipeline that aggregates mock daily weather into monthly summaries and plots. Returns validation results and rendered plot output through inline JSON configs.
      MIT

    • Climate MCP Server

      ssciwr-courses
      A
      license
      A
      quality
      B
      maintenance
      Wraps a climate data-processing pipeline so agents can inspect the config schema and available sample CSVs, validate an inline JSON config, and run the pipeline to return a monthly summary table plus a rendered plot, with file access sandboxed to the data and outputs directories.
      4
      MIT

    • tdcv2-mcp

      NickLiapin
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to validate .tdc configs, generate deterministic test data files locally, locate language and country data packs, summarise generated files, and read the TDCv2 docs as MCP tools. Everything runs on the user's machine, producing identical output byte for byte on every run.
      MIT

    • Data Science Agent MCP Server

      frzzzing
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP-compatible tools for data analysis, including file reading, Python/SQL execution, and hypothesis testing. Enables autonomous data analysis agents to interact with a sandboxed environment.
      1
      -
    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.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a clearly distinct purpose: schema retrieval, sample data listing, config validation, and pipeline execution. The only potential overlap is between get_config_schema and validate_climate_config, but their descriptions clearly differentiate them (informational vs. validation). Workflow order is logical and unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: get_config_schema, list_sample_data, validate_climate_config, process_climate_data. The convention is predictable and easy to parse.

    Tool Count5/5

    With only 4 tools, the set is tightly scoped to the climate data processing pipeline. Each tool is essential and serves a distinct purpose, and the count is appropriate for the narrow domain.

    Completeness4/5

    The tool set covers the core lifecycle: schema discovery, data listing, config validation, and execution. It lacks tools for inspecting results or managing stored data, but for a one-shot pipeline server, the surface is mostly complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources