Skip to main content
Glama

Related Servers

Alternatives to Climate MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI assistant to reliably read and chunk PDF/text documents, validate extracted JSON against a schema with full error paths, and save structured output—all confined to a single allowed directory.
      6
      MIT
    • F
      license
      Not graded
      quality
      C
      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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to query a local SQLite database read-only, search and read files within a sandboxed directory, and get current weather and forecasts via Open-Meteo, all through natural language.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Allows LLMs to explore CSV datasets through statistics without loading raw data, offering tools for dataset inspection, column description, and filtered queries while enforcing safety by restricting file access to a specified directory.
      -

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct role: get_config_schema returns the schema, validate_climate_config checks a config, list_sample_data enumerates inputs, and process_climate_data runs the pipeline. The schema/validate/process trio shares the same config object, which creates mild potential for confusion, but the descriptions clearly delimit each step.

    Naming Consistency5/5

    All four names follow a consistent verb_noun snake_case pattern (get_config_schema, list_sample_data, validate_climate_config, process_climate_data). No mixing of conventions or vague verbs.

    Tool Count4/5

    Four focused tools cover the discover-validate-run workflow cleanly with no redundancy or bloat. It is slightly thin, but each tool earns its place for a scoped climate-processing server.

    Completeness4/5

    The surface covers the full workflow of discovering the schema, finding input data, validating, and executing the pipeline with inline results. There is no way to retrieve or revisit past outputs, but that is a minor gap given the stateless inline-return design.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues