Climate MCP Server
Related Servers
Alternatives to Climate MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents to validate climate-processing configurations, inspect sample CSV data, and run a deterministic pipeline that aggregates daily records into monthly summaries and plots, with sandboxed paths and isolated outputs.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables 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.6MIT
- FlicenseNot gradedqualityFmaintenanceProvides 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-
- AlicenseBqualityCmaintenanceEnables MCP clients to load CSV, Excel, and other tabular files, profile datasets, and answer questions by executing LLM-written pandas code in a sandboxed subprocess.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to explore and analyse local CSV, Parquet or JSON files through validated read-only SELECT queries, with schema discovery, profiling and query-plan tools. Results are capped, timed, PII-masked and audit-logged inside a locked DuckDB sandbox that cannot write, reach the network or read other files.MIT
TDQS
Scored across 4 tools
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.
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.
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.
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.